Skip to content

labels.trusted_labelers: let a listed app's bot hand work over by label (0.4.0) - #6

Merged
cycle-five merged 2 commits into
masterfrom
trusted-labelers
Nov 20, 2026
Merged

cycle-five merged 2 commits into
masterfrom
trusted-labelers

Conversation

@cycle-five

Copy link
Copy Markdown
Member

What this is

0.3.0 hands work to an agent by label, and trusts a label only when GitHub reports triage access or more for whoever applied it. GitHub reports no access at all for a GitHub App's bot user, so a label applied by another agent was always untrusted-label. That already happened in practice: an agent's app asked another agent for review by label, and the request could not be routed.

Change

A source's labels block gains an optional list:

"labels": { "org": "your-org", "tag": "claude",
            "trusted_labelers": ["your-other-agent[bot]"] }
  • A labeler whose login is on the list is trusted without a permission lookup, for both labels.
  • Entries are whole logins, name or name[bot], matched in any case. Anything else, or a duplicate, is a config error.
  • Everyone not on the list is judged exactly as before. Without the list nothing changes.
  • A mailbox that lists its own bot follows what that bot labels for itself, without a claim record (skip_self).

Listing a bot means whoever can steer that agent can route work to this mailbox, for both labels, in any repository of the organisation. The README says so.

Design: docs/superpowers/specs/2026-11-20-label-claims-design.md, "Trust". Released as 0.4.0; the door moves with it, with no change in behaviour.

Checked

  • cargo fmt, cargo clippy -D warnings, cargo test --workspace (193 tests), the wasm32 build, the door's typecheck and tests.
  • New tests: a listed bot is trusted with no lookup and followed; an unlisted bot stays untrusted; a person's login that only starts like a listed one is still looked up; the mailbox's own listed bot; config validation. A prefix match, and "any bot once a list exists", each fail a test.

After merge

Add the list to each mailbox in the manifest, npm run mailbox -- deploy --mailroom, deploy the door, verify, tag v0.4.0, release.

🤖 Generated with Claude Code

https://claude.ai/code/session_017zqkE8grD6nh1bNnb2r1X8

…er by label (0.4.0)

GitHub reports no role for an app's bot user, so until now a label applied by
another agent was always untrusted. A source can now list logins whose labels
count whatever GitHub reports.

Co-Authored-By: Claude & Lothrop (cycle.five@proton.me)
… relabel by a listed bot

Co-Authored-By: Claude & Lothrop (cycle.five@proton.me)
@cycle-five
cycle-five merged commit d6593e5 into master Nov 20, 2026
2 checks passed
@cycle-five
cycle-five deleted the trusted-labelers branch November 20, 2026 13:27
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