Skip to content

feat: add agent routing sections - #74

Merged
bespoyasov merged 3 commits into
mainfrom
feat/agent-routing
Sep 15, 2026
Merged

bespoyasov merged 3 commits into
mainfrom
feat/agent-routing

Conversation

@bespoyasov

Copy link
Copy Markdown
Collaborator

Summary

  • Add agent routing instructions to CLAUDE.md and GEMINI.md so the agent prefers Confidence MCP tools and skills over browser automation, computer actions, or generic web searches when handling Confidence-related queries
  • Includes graceful fallback: agents fall back to web search or general knowledge when MCP servers are unavailable or don't return useful results

Rationale

Users reported that Codex would use browser automation or general knowledge to answer Confidence questions instead of the plugin's MCP tools — even though the tools have more accurate, up-to-date information. Without explicit routing guidance, the agent might treat MCP tools as one option among many rather than the preferred source.

@krisskross

Copy link
Copy Markdown

This looks great! I have a suggestion to help keep all agent instructions in sync and ensure they work perfectly for both Claude Code and Gemini (Antigravity).

1. Using one file (AGENTS.md) is a great idea
Yes, replacing GEMINI.md with AGENTS.md and symlinking CLAUDE.md to it is a very smart way to avoid maintaining two separate files!

  • Note: Just remember to update gemini-extension.json to say "contextFileName": "AGENTS.md" instead of "GEMINI.md".

2. Make the "Skills" instruction general
Right now, the text says to "invoke it via the Skill tool". However, Claude Code does not actually have a tool named "Skill", so it might get confused or show an error. Gemini also prefers to just read the file.

To make it work for all agents, we can use general wording. I suggest changing step 2 to this:

"2. Check if a skill matches the user's intent and read its SKILL.md file using your file reading tools (like ViewFile or view_file) before attempting manual approaches."

3. Small warning about Windows symlinks
Just a heads-up: Git on Windows sometimes has trouble with symlinks. It might save CLAUDE.md as a plain text file that just contains the word "AGENTS.md". If Windows users report issues with Claude Code later, we might have to use a simple script to copy the file instead of using a symlink. But for now, the symlink is a great start!

@bespoyasov

Copy link
Copy Markdown
Collaborator Author

Using one file (AGENTS.md) is a great idea

I thought about it, but it will require symlink support on Windows, so I thought the decision of whether to symlink the files would be out of the scope of this PR 🙃

@vahidlazio, wdyt? Should I link them right away?

Make the "Skills" instruction general

Fair; updated it to be more general!

@bespoyasov
bespoyasov merged commit f416826 into main Sep 15, 2026
1 check passed
@bespoyasov
bespoyasov deleted the feat/agent-routing branch September 15, 2026 10:48
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