Pain
During dogfood, invoking bro in an interactive session requires typing something like:
…or worse, whatever the tab-completer produces:
That's 6–18 characters on every code-touching ask. Bro is the single Human entry point by design — the handle has to be frictionless or the whole routing architecture collapses to "just ask main Claude directly."
What's actually required
tmb: namespace prefix is CC-enforced to prevent collisions with local agents. We can't drop it at the plugin level.
(agent) suffix is a CC tab-completion UI label, not part of the actual invocation. @tmb:bro alone works.
- Quotes are added by the tab-completer unnecessarily; plain
@tmb:bro is accepted.
Unknown — needs dogfood verification
Does main Claude persist bro's persona across a session after one @tmb:bro invocation, so subsequent messages in the same session route through bro without re-mentioning? If yes, invoke-once UX is acceptable. If no, the per-message cost is real and a shorter form matters.
Test: fresh scratch project, @tmb:bro hello, wait for response, then send "what should I work on?" with no @-mention. If bro handles it, persona persists. If main Claude answers directly, it doesn't.
Options in order of preference
A. Document @tmb:bro as canonical, ignore tab-completer noise
- Pro: zero code change, just clarity.
- Con: still 8 chars per invocation if persona doesn't persist.
B. Project-level proxy agent
- Add instructions in docs: "to type
@bro instead, create .claude/agents/bro.md in your project containing a one-line See tmb:bro proxy."
- Pro: gives users the short handle without requiring CC changes.
- Con: per-project setup burden; proxy pattern may not be supported by CC (untested — needs verification).
C. Slash command alternative
- Ship
skills/bro/SKILL.md (user-invocable) that spawns tmb:bro.
- Invocation:
/bro <ask>.
- Pro: consistent 5 chars; works across projects without setup.
- Con: slash commands and agent spawns are different mechanisms — needs to confirm skill can spawn subagent cleanly; doesn't help if persona-persistence is what we actually need.
D. CC feature request upstream
- Ask Anthropic for an opt-in short form (e.g.,
@bro when plugin is enabled and no name collision).
- Pro: best long-term answer.
- Con: external dependency; unbounded timeline.
Related
Acceptance criteria
Pain
During dogfood, invoking bro in an interactive session requires typing something like:
…or worse, whatever the tab-completer produces:
That's 6–18 characters on every code-touching ask. Bro is the single Human entry point by design — the handle has to be frictionless or the whole routing architecture collapses to "just ask main Claude directly."
What's actually required
tmb:namespace prefix is CC-enforced to prevent collisions with local agents. We can't drop it at the plugin level.(agent)suffix is a CC tab-completion UI label, not part of the actual invocation.@tmb:broalone works.@tmb:brois accepted.Unknown — needs dogfood verification
Does main Claude persist bro's persona across a session after one
@tmb:broinvocation, so subsequent messages in the same session route through bro without re-mentioning? If yes, invoke-once UX is acceptable. If no, the per-message cost is real and a shorter form matters.Test: fresh scratch project,
@tmb:bro hello, wait for response, then send "what should I work on?" with no @-mention. If bro handles it, persona persists. If main Claude answers directly, it doesn't.Options in order of preference
A. Document
@tmb:broas canonical, ignore tab-completer noiseB. Project-level proxy agent
@broinstead, create.claude/agents/bro.mdin your project containing a one-lineSee tmb:broproxy."C. Slash command alternative
skills/bro/SKILL.md(user-invocable) that spawnstmb:bro./bro <ask>.D. CC feature request upstream
@browhen plugin is enabled and no name collision).Related
gatekeeper → broclosed the rename half; the handle length and the routing-enforcement half are still open. This issue is specifically the handle-length sub-problem. User entry path to gatekeeper: enforce the routing + shorten the mention handle (@bro) #36 can close once both halves resolve.Acceptance criteria
@tmb:browithout quotes or parens).@tmb:bro? Result recorded in SCENARIOS.md.