Skip to content

docs(harness): Record that the Harness authenticates itself and ai-buddy holds nothing (#371) - #405

Merged
omesser merged 1 commit into
mainfrom
docs/371-harness-auth-boundary
Sep 6, 2026
Merged

omesser merged 1 commit into
mainfrom
docs/371-harness-auth-boundary

Conversation

@omesser

@omesser omesser commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Why

ADR-0010 has ai-buddy spawn a Harness and hold it for as long as the app runs,
and said nothing about how that subprocess is authenticated. #371 spiked it.
The finding is that all five Harnesses keep their credential in a home-relative
file or the OS keychain and read it at process start, so an already-logged-in
CLI hands its login to a subprocess we spawn as the same user. Anthropic's own
legal page permits that shape by name and forbids the alternative, so the
boundary is settled rather than chosen: ai-buddy holds nothing.

That is a decision a future pull request has to be held to, which is why it
lands in the record where spawning was decided rather than staying a comment.

What changed

docs/adr/0010-headless-harness-our-chat-surface.md gains three paragraphs and
a numbered list in Consequences:

  • The Harness authenticates itself, with the reason SecretStore does not
    carry over — ai-buddy is the HTTP client for the Director key and is not the
    HTTP client for a Harness.
  • Eight things a pull request touching attachment may not do.
  • The Chat surface's three states: not attached, attached but not
    authenticated, attached and refused.

Documentation only. No code, per #371.

How to verify

Read the diff against the spike comment,
which carries the per-Harness evidence and source URLs the amendment condenses.

Closes #371.

— Claude Code, on @omesser's behalf.

@omesser omesser added the security Security related - secrets, password, key-chain management, etc label Sep 6, 2026
@omesser
omesser merged commit 2486675 into main Sep 6, 2026
8 checks passed
@omesser
omesser deleted the docs/371-harness-auth-boundary branch September 6, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security Security related - secrets, password, key-chain management, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Spike: how an attached Harness authenticates, and what ai-buddy must never hold

1 participant