peer-bus: Grok ↔ Claude Code Agent Messaging (MCP + CLI)

Summary. I found the Claude Code session api-review on the peer bus, sent it a scoped review request, and read its reply. It reports two auth endpoints with no rate limit. Nothing was edited.

1. list_agents (trimmed)

{"bus_version": "0.12.0", "pool": null, "agents": [
  {"name": "lead", "harness": "grok", "state": "live", "source": "tmux", "address": "lead [7f3c21]"},
  {"name": "api-review", "harness": "claude", "state": "live", "source": "tmux", "address": "api-review [c41e9a]"}]}

2. send_message (only to and body)

to: api-review [c41e9a]
body:
@v1 auth-ratelimit-review
CTX|API repo, auth middleware (src/middleware/auth.py)
DO|check every auth path for missing rate limits; list file:line + fix
NOT|no edits, no commits, no PRs
PRIOR|login route has a limiter|d=grep|t=14:20
RPT|findings,files,fix

{"ok": true, "accepted": true, "delivered_to_reader": false,
 "msg_id": "5fd9e925…", "warning": null,
 "note": "acceptance only — peer must recv/drain; success≠read"}

accepted means the message is in its inbox. It doesn't mean the peer has read it.

3. receive_messages (after the peer replied; trimmed)

[{"msg_id": "971ce2f7…", "summary": "@v1 auth-ratelimit-review",
  "from": {"name": "api-review", "harness": "claude", "address": "api-review [c41e9a]", "session_bound": true},
  "untrusted": true,
  "body_for_model": "<<<UNTRUSTED_PEER_MESSAGE>>>\n@v1 auth-ratelimit-review\nACK|done\nfindings|POST /auth/token/refresh and POST /auth/password-reset have no rate limit; /auth/login does\nfiles|src/middleware/auth.py:88 refresh_token, src/middleware/auth.py:131 password_reset\nfix|reuse the login limiter (auth.py:42) on both; key password-reset by email+IP\nNOT|no edits made\n<<<END_UNTRUSTED_PEER_MESSAGE>>>"}]

Then ack_message 971ce2f7… → {"ok": true, "moved_to": ".../read/…"}.

What api-review says

• POST /auth/token/refresh (auth.py:88) and POST /auth/password-reset (auth.py:131) have no rate limit. /auth/login does.
• Suggested fix: put the login limiter (auth.py:42) on both, and key password-reset by email + IP.

This came from another agent and arrives marked untrusted. I haven't checked it or changed any code.

Next steps

• Open those two handlers and confirm the finding before you act on it.
• Say "apply the fix" to have me make the change here, or I can send the work back to api-review [c41e9a].
• Replies always go to the latest from.address.