Skip to content

docs: say how credentials reach the sandbox - #1

Open
ananos wants to merge 1 commit into
mainfrom
docs/credentials
Open

docs: say how credentials reach the sandbox#1
ananos wants to merge 1 commit into
mainfrom
docs/credentials

Conversation

@ananos

@ananos ananos commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

The org profile described the boundary and then stopped short of what a reader most wants to know: what happens to their login.

It also said credentials are "forwarded per exec". That is now only half the story -- the Claude profiles deliver a file into a memory-only mount, and the environment is the other channel rather than the only one.

Adds a short Credentials section covering the three things someone landing on the org page needs: a sandbox with no credential still boots, brig secret import carries the host login in once, and every run after that reads only brig's own store -- no other application's keychain item, no approval dialog.

Everything else on the page was checked and is accurate: install.sh resolves, brew trust is a real command, and all four referenced assets return 200.

The profile described the boundary and then skipped the part a reader most
wants: what happens to their login. It also said credentials are "forwarded
per exec", which is now only half true -- the Claude profiles deliver a file
into a memory-only mount, and the environment is the other channel rather than
the only one.

Adds a Credentials section: a sandbox with no credential still boots, `brig
secret import` carries the host login in once, and after that a run reads only
brig's own store.

Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
@ananos
ananos requested a review from asapranidis August 19, 2026 19:47
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