8823ea6fcb
## Summary For a single-select `AskUserQuestion`, a non-empty custom-answer field (`question_<n>_custom`) replaced the selected option. A client that renders that box as a notes step (as in #1050, seen via Devin/Windsurf) therefore returned only the typed text and the selection never reached the model. - The pick now stays in `answers`, and the typed text travels beside it as the tool's own per-question `annotations[question].notes`. That is the slot the CLI itself uses for free text attached to a selection and renders to the model as `"Q"="A" notes: ...`, so no new answer format is invented. - Custom text with no pick is still the answer on its own (the CLI's "Other"). - Multi-select folding from #1031 is unchanged: the text still joins the checked options with CLI-style quoting. - `annotations` is only added to `updatedInput` when non-empty. - The single-select field description now says the box can also add a note to the chosen option. Supersedes #1054, which conflicted with #1031 and glued label and text into one string. The "empty notes field won't submit" part of #1050 is client-side: nothing in the requested schema is marked required. Closes #1050 ## Test plan - `npm run check` - `npm run build` - `npm run test:run` (1325 passed, 27 skipped) - New test: pick + custom text yields `answers: { Q: "A" }` and `annotations: { Q: { notes } }` - New test: custom text alone on a single-select stays the answer 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ACP adapter for the Claude Agent SDK
Use Claude Agent SDK from ACP-compatible clients!
This tool implements an ACP agent by using the official Claude Agent SDK, supporting:
- Context @-mentions
- Images
- Tool calls (with permission requests)
- Following
- Edit review
- TODO lists
- Nested subagent transcripts
- Interactive (and background) terminals
- Custom Slash commands
- Client MCP servers
- Session-scoped long-running goals through the provider-neutral goal extension
- Structured errors, recovery, and warnings through the opt-in session failure extension
- Concrete model and effort defaults through the opt-in recommended config value extension
- Tool permission presentation, editable choices, and durable effects through the permission extension
Learn more about the Agent Client Protocol.
To try changes that have landed on main but are not released yet, install from the
preview channel — every push to main publishes one. See
docs/RELEASES.md.
npm install @agentclientprotocol/claude-agent-acp@preview
Subagent sessions
Subagents are exposed only after bilateral capability negotiation. Until the released ACP SDKs
preserve the draft clientCapabilities.subagents field, a supporting client may advertise
nativeSubagentSessions in _meta.jetbrains.air.capabilities; the adapter mirrors the capability
in its initialize response. The canonical field remains supported and takes precedence once it is
available. Without either client signal, Agent/Task lifecycle keeps its legacy ordinary ACP
tool-call representation and child interactions stay on the root session. Clients that use the
historical _meta["subagent-transcript"] capability or forwardSubagentText session option retain
the flattened child transcript behavior.
Contribution Policy
This project does not require a Contributor License Agreement (CLA). Instead, contributions are accepted under the following terms:
By contributing to this project, you agree that your contributions will be licensed under the Apache License, Version 2.0. You affirm that you have the legal right to submit your work, that you are not including code you do not have rights to, and that you understand contributions are made without requiring a Contributor License Agreement (CLA).