Skip to content

docs(acp): correct Codex quick-start, idle timeout, and author gate - #5187

Open
Diego-F-Aguirre wants to merge 1 commit into
block:mainfrom
Diego-F-Aguirre:docs/acp-readme-corrections
Open

docs(acp): correct Codex quick-start, idle timeout, and author gate#5187
Diego-F-Aguirre wants to merge 1 commit into
block:mainfrom
Diego-F-Aguirre:docs/acp-readme-corrections

Conversation

@Diego-F-Aguirre

Copy link
Copy Markdown

Summary

Three statements in crates/buzz-acp/README.md disagree with the code they describe. Docs only, no behavior change.

1. The Codex quick-start silently spawns goose. The "Running with Codex" block never sets BUZZ_ACP_AGENT_COMMAND, which defaults to "goose" (config.rs). Following it verbatim installs codex-acp and then runs goose. The Claude Code section already sets the variable, so this also removes an inconsistency between the two runtime sections.

2. BUZZ_ACP_IDLE_TIMEOUT is documented as 620. DEFAULT_IDLE_TIMEOUT_SECS is 900 (config.rs), asserted by a unit test in the same file.

3. The author-gate section omits two behaviors that change who can prompt an agent. The table documents four modes and notes the owner is implicitly included, but does not mention that:

  • owner-only and allowlist also accept same-owner siblings, verified from the author's NIP-OA auth tag (is_owner_or_sibling);
  • inside a DM, anyone and allowlist do not apply at all — only the owner and verified siblings may fire a turn, and unknown channel type is treated as a DM.

Both are already documented in the author_allowed doc comment; this surfaces them where operators configure the gate. The DM behavior in particular is a deliberate hardening against transitive access grants, and an operator reading only the README could reasonably conclude --respond-to allowlist is authoritative in DMs.

Related issue

None found. Searched open issues and PRs for these specifics. The closest related PR is #5168, which also touches DM handling in this crate, but changes the mention subscription filter rather than the author gate — no overlap with these lines.

Testing

Documentation only; no code paths changed and no tests affected. Each correction was checked against the source at the commit this branch is based on rather than inferred from the docs.

Three README statements disagree with the code they describe.

The Codex quick-start never sets BUZZ_ACP_AGENT_COMMAND, so following it
verbatim spawns goose rather than codex-acp: the flag defaults to "goose"
(config.rs). The Claude Code section already sets it, so this also removes an
internal inconsistency between the two runtime sections.

BUZZ_ACP_IDLE_TIMEOUT is documented as 620, but DEFAULT_IDLE_TIMEOUT_SECS is
900 (config.rs), asserted by a unit test in the same file.

The author-gate section documents four modes and notes the owner is implicitly
included, but omits two behaviors that materially change who can prompt an
agent. owner-only and allowlist also accept same-owner siblings, verified from
the author's NIP-OA auth tag (is_owner_or_sibling in lib.rs). Inside a DM,
anyone and allowlist do not apply at all — only the owner and verified siblings
may fire a turn, and unknown channel type is treated as a DM. Both are already
described in the author_allowed doc comment; this surfaces them in the README.

Docs only; no behavior change.

Signed-off-by: Diego-F-Aguirre <diego3884@gmail.com>
@Diego-F-Aguirre
Diego-F-Aguirre requested a review from a team as a code owner August 7, 2026 14:42
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