feat(acp): connect registry providers to shared sign-in flows - #12967
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
6bc8dbc to
c3a1c5d
Compare
107da3d to
ea880e0
Compare
ea880e0 to
9d52328
Compare
9d52328 to
647baac
Compare
3800e34 to
729b58a
Compare
fef3572 to
df9d598
Compare
df9d598 to
f78a3f8
Compare
f78a3f8 to
20e903c
Compare
20e903c to
394c71e
Compare
|
Effect Service Conventions found one issue in Posted via Macroscope — Effect Service Conventions |
This comment has been minimized.
This comment has been minimized.
- Chat sessions again run agent-managed sign-in when the agent reports auth_required; only discovery and probes surface it without authenticating. - Registry versions must look like versions, so "." or ".." cannot become an install directory segment. - Path-overridden agents without a version rediscover sign-in methods on refresh instead of reusing the first result forever. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tool and plan progress for calls that started before the retry can arrive mid-retry, so it no longer marks the retry as recovered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iver Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
08353f9 to
c4ba935
Compare
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Registry-installed ACP providers need a consistent account setup path instead of requiring users to discover the correct CLI login command themselves.
Discover advertised authentication methods and connect them to the shared sign-in flow, including browser consent and interactive terminal login. Verify authentication with a fresh ACP session and refresh methods after runtime updates. Credentials remain in each agent's native store; credential changes coordinate all instances sharing that agent's binding.
Managed runtimes use
tools/<agent-id>/<version>/inside T3 home, including isolated npm and Python installs. Launch the registry version by default; existing PATH binaries require an explicit executable override. Mistral retry notifications update the existing retry UI, and structured ACP errors retain the provider's error message.Depends on #12966.
Validation: 131 focused catalog, driver, authentication, adapter, and terminal tests passed for managed installs. Scoped server typecheck and targeted lint passed (one existing lint warning). A real managed Mistral binary returned version 2.25.5 through ACP initialize. Earlier integrated stack validation passed 231 focused tests.
Latest restacked validation: 219 focused ACP/Cursor backend tests and 63 provider-settings web tests pass. Scoped server and web typechecks pass.
Live ACP sign-in and before/after UI evidence are pending. The V2 selection-restart CI failure is tracked by #13113. This PR remains a draft.
Implemented with GPT-6 in the Codex harness.