You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fe50a3e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/agent-activity-overlay.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,22 @@ Provider mapping — only structured, provider-issued questions reach this card:
78
78
| Codex | app-server `item/tool/requestUserInput` (legacy `tool/requestUserInput` alias), one card per question | when the question sets `isOther` or has no options |
CrewCode advertises `_meta["crewcoder/questions"].version: 1` on ACP initialize.
84
+
Updated CrewCoder forwards nested Codex `requestUserInput` and Claude
85
+
`AskUserQuestion` through `_crewcoder/request_question`, retaining original
86
+
option values, descriptions, free-text availability, multi-select toggles, and
87
+
secret input flags.
88
+
Questions use `select`/`prompt` cards and remain interactive in Ask/Plan/Full;
89
+
they never pass through permission-option filtering or Full Access auto-approval.
90
+
Actual provider approval requests carry `kind: permission`, show the requested
91
+
command or filesystem/network scope, and retain read-only mode restrictions.
92
+
CrewCode returns only once/turn permission choices, never session-wide grants.
93
+
Stop, process exit, turn completion, and the exact
94
+
`_crewcoder/question_cancelled` notification abort the pending card. Empty or
95
+
cancelled responses never become answers. Older ACP clients without the
96
+
capability retain option-only permission transport; they cannot collect free text.
82
97
83
98
Codex answers are returned as `{ answers: { [questionId]: { answers: string[] } } }`. A cancelled, empty, or out-of-contract answer (typed text where Codex offered no "Other") fails the whole request with an explicit JSON-RPC error; Codex never receives a fabricated or empty answer. When Codex settles a request itself (`serverRequest/resolved`, e.g. non-blocking questions) or the app-server exits, the bridge aborts the pending `RequestUserFn` signal: the promise settles as `cancel` and the card is retracted with `user_request_resolved`.
0 commit comments