Agent-required framing in MCP section + AGENTS.md#22
Merged
Conversation
README: - The MCP section now states explicitly that cli-bridge is the recommended path for agentic use, with the underlying reason (CLAUDE.md mentions decay under context pressure; MCP tools don't). Links to cli-bridge's "The problem" section for the full background instead of restating it. - Disambiguates the install.sh path (auto-generates spec, skip step 3) from the manual path. - Mentions cli-bridge's auto-refresh so users understand spec stays in sync after binary upgrades without re-registering. AGENTS.md (new): factual description of what gosymdb is, how the database is found, the freshness loop, the MCP integration via cli-bridge, known limitations, and related tools in the family (cli-bridge, cairn). Descriptive register — describes capabilities rather than directing agent behavior. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
walkindude
force-pushed
the
agent-required-framing-and-agents-md
branch
from
fc33caa to
13e49bd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Use with Claude Code (MCP)section now states explicitly that cli-bridge is the recommended path for agentic use, with the underlying reason — and links to cli-bridge's "The problem" section instead of restating it.install.shpath (auto-generates the cli-bridge spec when Claude Code is detected — skip step 3) from the manual path.gosymdbbinary upgrades — no re-registration needed.AGENTS.mdwith a factual description of what gosymdb is, how the database is found, the freshness loop, MCP integration via cli-bridge, known limitations, and related tools in the family. Descriptive register throughout (no imperatives directed at agents).Why
The previous README presented cli-bridge as one of several options. In practice it is the path for agentic use — agents that only see gosymdb mentioned in
CLAUDE.mdquietly fall back togreponce the conversation gets long. Saying so explicitly (with the reason) helps both human readers picking a setup and agents reading the file later.Test plan
go test ./...— greengosymdb cli-bridge-manifeststill emits valid spec JSON (unchanged)gosymdb_*MCP tools appear in the registryRelated
AGENTS.mdtreatment locally🤖 Generated with Claude Code