Skip to content

feat(mira): first responses post without approval (decision 78) - #54

Merged
mttrbrts merged 3 commits into
mainfrom
feat/mira-auto-first-response
Nov 13, 2026
Merged

mttrbrts merged 3 commits into
mainfrom
feat/mira-auto-first-response

Conversation

@mttrbrts

Copy link
Copy Markdown
Member

Mira's first responses to new PRs and issues now post without a card, once the gateway's checks pass. A redraft of an open comment replaces it, so a comment can no longer be approved and posted twice.

In the first two weeks there were 105 comment cards. Most rejections came in the first week, and most were about closing rather than welcoming. Closures still need approval. In the second week, review caught one unfinished draft and let through three pairs of duplicate comments (template-playground#1105, template-playground#1106, concerto-codegen#315).

Changes

  • New action kind github.first_response, set to auto. The gateway posts it at once if:

    • the PR or issue is open, and the network has no earlier approved or posted comment there;
    • the text is at least 80 characters, has no draft markers and doesn't end mid-sentence;
    • it @mentions no one but the author, and says nothing about the network.

    Otherwise it refuses, and Mira redrafts. It still comes as a card when Mira rates it high risk or a member set the work going.

  • The gateway signs these comments as posted automatically, and strips the draft's "reviewed by a maintainer" label.

  • A new github.comment or github.first_response from the same agent on the same target lapses the older open one.

  • issueState now also returns the author, so the mention check knows who it may allow.

  • Updated: Mira's spec (triage step 1), the public-voice rule in _protocol.md, rule 3 in CLAUDE.md, and decision 78.

Safety

Adds an auto action kind (rule 3), as the owner decided. Comments that close or reply to an issue stay github.comment, which needs approval. Setting auto: false on github.first_response makes every first response a card again.

Deploy

npm run gateway:deploy and npm run deploy:agents (the deploy workflow does both).

Decision

78

Checks

  • npm test passes (429 tests)
  • Tests cover the behaviour change (gateway/test/github.test.ts, "first responses (decision 78)")
  • network.json regenerated if config/ changed
  • No secrets or Discord/Telegram ids added

🤖 Generated with Claude Code

mttrbrts-agent and others added 3 commits November 13, 2026 18:55
A new auto action kind, github.first_response, posts Mira's first response
to a new PR or issue once the gateway's checks pass: the target is open and
the network hasn't already commented there; the text is finished, at least
80 characters, mentions no one but the author and says nothing about the
network. Failures are refused so Mira redrafts. A high-risk request, or work
a member set going, still goes to Matt as a card. The gateway signs the
comment as posted automatically and strips the "reviewed by a maintainer"
label from the draft.

A redraft of an open github.comment or github.first_response from the same
agent on the same target now lapses the older one, so approving both can no
longer post the comment twice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Matt Roberts (Agent) <code+agent@rbrts.uk>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Matt Roberts (Agent) <code+agent@rbrts.uk>
Mira's drafts have carried her note to avoid mentions into the text three times ("@-free", "@Name-Free"). Treat it as an unfinished draft. An email address or code is not matched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Matt Roberts (Agent) <code+agent@rbrts.uk>
@mttrbrts
mttrbrts merged commit 8476ea0 into main Nov 13, 2026
5 checks passed
@mttrbrts
mttrbrts deleted the feat/mira-auto-first-response branch November 13, 2026 19:56
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.

2 participants