Skip to content

MANUAL RUN: rotate the Agent Office password, clear secrets from the office shell, trim gh token scopes #654

Closed as not planned

Description

@QuinnsCode

Found in the security audit (notes/SECURITY_AUDIT.md). One-off hygiene that needs you at the machine:

  1. Rotate the Agent Office password and session secret once the office token fix lands (the current ones sat in a file every agent could read). Delete password, secret, salt and verifier from ~/agent-office/.agent-office/config.json while the office is stopped, start it, and save the new password in 1Password.
  2. Check what the office's shell exports: run env | cut -d= -f1 | grep -iE 'token|secret|key|pass|op_' in the terminal you start the office from. Anything listed reaches every agent today. Remove those exports from your shell profile; deploys get them from varlock.
  3. gh token scope: gh auth status shows its scopes. Agents use it. If it has delete_repo or admin:org, drop them with gh auth refresh --remove-scopes delete_repo,admin:org.
  4. 1Password service accounts (only if you use wheel: "agent"): one per test vault, never with access to the codesplitters vault.

Activity

  1. added
    securityFound in the security audit (#135)
    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it
    on Oct 11, 2026
  2. self-assigned this
    on Oct 11, 2026
  3. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Checked from an agent (2026-10-11):

    • Step 3 is done, nothing to trim. gh scopes are gist, project, read:org, repo, workflow. There's no delete_repo or admin:org.
    • Step 4 doesn't apply. No app config uses wheel: "agent" (it only shows up in REFERENCE.md and a test).
    • Steps 1–2 are left for the owner. Run zsh ~/office-hygiene-654.sh from the terminal that starts the office, with the office stopped. It lists secret-looking export names and removes password/secret/salt/verifier from the config, keeping a backup.
    • Agent Office: any agent can read every worker's hook token, the pty token and the office session secret #642 is still open. After it lands, rotate again, because agents can read the new password until then.
  4. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Tracked in #609, the one hands-on checklist. The steps here still apply; tick them there.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close itsecurityFound in the security audit (#135)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions