BasePlatformAdapter interactive UX methods (clarify, approval, pickers) #662
Notifications
Due Date
No due date set.
Blocks
#663 Platform capability flags for adapters
sam/archie
Reference: sam/archie#662
Reference in new issue
Block a user
Add adapter-facing methods for interactive UX: presenting a clarifying question, an approval prompt, and a picker (multi-choice selection) natively on the platform, rather than as plain text the user has to reply to by hand.
Context for implementers
The approval decision plumbing already exists —
internal/tools/approval.go, re-exported throughinternal/gateway/approval.go(ApprovalRequester,ApprovalDecision,WithApprovalRequester/ApprovalFromContext). What's missing is the adapter-side rendering:BasePlatformAdapter(internal/gateway/adapter.go) has no method for an adapter to display an approval/clarify/picker UI and report back a decision through that existing plumbing. This issue wires a new adapter method (or interface) into the existingApprovalRequesterflow — it should not duplicate or replace the decision model ininternal/tools/approval.go. Sibling ofarchie-core-1786637493329-136-49b39c78(typing/edit/delete/media) — same "optional adapter capability" shape, different capability set.Acceptance Criteria
An adapter can render a clarify/approval/picker prompt and the user's response is delivered back through the existing
ApprovalRequester/ApprovalDecisionflow ininternal/tools/approval.go, not a parallel mechanism. Platforms without native UI (e.g. plain text-only channels) degrade to a text-based fallback rather than failing. Covered by a test double adapter, not a live platform.Close reason
Closed
Imported from beads
archie-core-1786637493357-137-35af7083· GitHub #158 · type task · priority P2 · created 2026-08-08 · closed 2026-10-02