Skip to content

gate: a tracker write needs no lease - #32

Merged
tannevaled merged 1 commit into
mainfrom
gate-tracker-writes
Nov 18, 2026
Merged

tannevaled merged 1 commit into
mainfrom
gate-tracker-writes

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

What

agentsync gate --hook no longer refuses a TRACKER write into a repository another session holds: ghissue with --new, a comment, --close or --reopen (and --dry-run plus the text-carrying flags). It prints a one-line notice naming the holder (stderr, and additionalContext with no permission decision).

Why

The lease protects the holder's code. On 2026-11-18 21:55 ghissue go-fleettools/fleettools --new ... was refused for 30+ minutes although opening an issue cannot collide with their branch, PR, merge or release.

Boundary, tested on both sides

  • allowed: --new, comment, --close --reason, --reopen, --repo, --flag=value, quoted values, and with no claim at all.
  • still refused: gitpush, ghmerge, ghrelease, ghpr, ghrun, ghrel, ghissue --edit, --delete, an unknown flag, and a tracker write chained with a code write.

Not touched: Refs #30 (--help/--dry-run of a publishing program needs no claim) is a separate boundary and stays open.

🤖 Generated with Claude Code

The lease protects the holder's code. ghissue --new, a comment, --close and
--reopen touch no file of theirs, yet a hook refused `ghissue --new` for 30+
minutes on 2026-11-18 because another session held the repository.

Those ghissue forms are now allowed with or without a claim, and when another
session holds one the gate prints a one-line notice naming the holder (stderr and
additionalContext, no permission decision). Everything else stays refused:
gitpush, ghmerge, ghrelease, ghpr, ghrun, ghrel, and ghissue --edit/--delete/
--comment or any flag the classifier does not know (fail closed).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit c92fbcf into main Nov 18, 2026
2 checks passed
@tannevaled
tannevaled deleted the gate-tracker-writes branch November 18, 2026 21:09
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