Skip to content

docs(mcp): start every-turn inbox checks on first gander - #86

Merged
scott merged 1 commit into
mainfrom
docs/85-every-turn-inbox-on-first-gander
Aug 31, 2026
Merged

docs(mcp): start every-turn inbox checks on first gander#86
scott merged 1 commit into
mainfrom
docs/85-every-turn-inbox-on-first-gander

Conversation

@scott

@scott scott commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Other agents (Codex, OpenCode, Cursor, etc.) start the no-path inbox check at the beginning of every subsequent turn only after the user first asks to gander a markdown file (preview, share, or gander watch).
  • They still do not use /loop.
  • Grok Build and Claude Code keep the first-gander /loop 5m trigger.
  • Existing comment rules are unchanged: metadata-only inbox, path-scoped body fetch, untrusted comment text, no auto-resolve, empty inbox is silent.
  • Paired with gandermd/gander-skill#9.

Related Issue

Closes #85

Testing

go test ./...
go vet ./...
go build ./...

Result: all green. TestMCPInstructionsOtherAgentsInbox asserts the first-gander-file trigger and every-turn checks after it, and forbids /loop in the Other-agents block. TestMCPInstructionsGrokClaudeLoop still asserts Grok/Claude must not poll every turn.

Notes

MCP initialize still ships one instruction string with both branches — no client detection. List / remove / manage / signup / upgrade are not triggers.

@scott
scott merged commit 435fb3d into main Aug 31, 2026
1 check passed
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.

docs(mcp): start every-turn inbox checks on first gander of a markdown file

1 participant