Conversation
A security feature for issue mode: /do:next --issues --self restricts every claim (auto-pick, --swarm batch, and explicit #num) to issues whose author is the running gh account (@me), so on a shared tracker the agent never picks up or acts on the instructions embedded in an issue filed by someone else. Auto-pick filters others out at the API (--author @me); an explicit number for another user's issue is refused, not overridden -- the one skip a deliberate cherry-pick can't cross, because it's a security boundary not a curation preference. Persisted via /do:config --self (global or per-project).
…m workers so a per-run override beats the saved self default
… ownership check so a fresh run doesn't read an empty var
…verview bullet The top-of-file <slug>/#<issue> Parse-Arguments bullet still said an explicit number bypasses 'every auto-pick skip', contradicting the --self security boundary that Phase 1 step 5 and the Notes section correctly exclude. An agent reading the overview in isolation could wrongly claim another user's issue under --self. Carve out the exception to match the authoritative gate.
…${VAR:+...}
zsh does not word-split parameter-expansion results, so
${AUTHOR_FILTER:+--author "$AUTHOR_FILTER"} expanded to a single argv word
'--author @me' and gh aborted with 'unknown flag: --author @me' whenever --self
was on (the sibling --label filter had the same latent trap). Build the optional
flags with a LIST_ARGS array, which appends each flag and value as separate words
in both bash and zsh and expands to nothing when unset.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Highlights
/do:next --selfclaims only issues you filed. A new security gate for issue mode restricts every claim — auto-pick,--swarmbatch, and an explicit#<num>— to issues authored by the running account, so on a shared tracker your agent never picks up (or acts on instructions embedded in) someone else's issue. Save it once with/do:config --self, or pass--no-selfto fall back to claiming any open issue.Changes since v3.18.0
add --self gate to /do:next: claim only issues you filed(458c274)address review (claude): note --self exception in the explicit-#num override summary(a84e8b6)address review (codex): propagate resolved --self/--no-self into swarm workers(95c5216)address review (codex): set ISSUE_NUM before the explicit-#num --self ownership check(141ab50)Full Diff: v3.18.0...v3.19.0