Skip to content

Document native ACP setup and expose terminal authentication#437

Draft
igorcosta wants to merge 2 commits into
mainfrom
agent/native-acp-auth
Draft

Document native ACP setup and expose terminal authentication#437
igorcosta wants to merge 2 commits into
mainfrom
agent/native-acp-auth

Conversation

@igorcosta

Copy link
Copy Markdown
Contributor

What changed

  • Add a complete native ACP guide for Zed, JetBrains IDEs, JetBrains Air, GitHub Copilot, and future ACP-compatible ADEs.
  • Advertise Autohand setup as an ACP terminal authentication method during initialization.
  • Correct the ACP login guidance to use autohand --login.
  • Explain why manually configured Air agents use a generic icon and how ACP Registry metadata supplies branded icons.
  • Add contract tests for the guide and ACP handshake.

Why

Autohand Code already supports native ACP through autohand --acp, but users had no maintained setup guide. The ACP Registry also validates that agents expose an authentication path, which the native adapter did not previously advertise. Manual Air entries therefore worked but appeared as generic custom agents rather than branded registry agents.

Impact

Users can configure Autohand Code consistently across supported ACP clients. Registry clients can discover the interactive setup flow, and the repository now documents the distinction between manual ACP configuration and branded Registry installation.

Validation

  • Focused ACP and documentation tests: 68 passed
  • Lint: passed
  • Full proof unit gate: 471 test files passed, 2 skipped; 7,109 tests passed, 26 skipped
  • Production ESM, CJS, and type declaration build: passed
  • Tuistory built-terminal gate: 3 files and 33 tests passed

igorcosta and others added 2 commits July 17, 2026 13:13
Add verified setup examples for Zed, JetBrains IDEs, and JetBrains Air, and record the current GitHub Copilot app limitation. Link the guide from the README and configuration reference and guard the launch contract with documentation tests.

Co-authored-by: Autohand Evolve <code-noreply@autohand.ai>
Expose the interactive setup flow in the ACP initialize response so Registry clients can satisfy their authentication contract. Correct the login guidance and document why manually configured Air agents use a generic icon until Registry installation is available.

Co-authored-by: Autohand Evolve <code-noreply@autohand.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant