feat(coding-agents): widen get_coding_agents to all 4 ingested tools
Your work logs itself. Meridian watches what you build - no prompts, no timers - classifies every session into the right task, and auto-updates Jira, Linear, and GitHub Issues. All data stays on your machine.
Brought to you by:
prateekbhoge320
Originally posted by: coderabbitai[bot]
✨ Finishing Touches
🧪 Generate unit tests (beta)
- [ ] Create PR with unit tests - [ ] Commit unit tests in branch `feat/coding-agents-more-providers`Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)Comment
@coderabbitai helpto get the list of available commands.Originally posted by: Akarsh-Hegde
Review — widen
get_coding_agentsto all 4 ingested toolsSummary: A correct, minimal widening — the two edited constants match the ingest table exactly and stay consistent with each other; the only real gap is missing test coverage for the two newly-included agents.
Blocking / correctness issues
None. Cross-checking the four
app_namevalues against CLAUDE.md's "Ingested agents" table:Claude Code,Codex,GitHub Copilot(CLI + VS Code chat share it),Cursor Agent(Cursor IDE + cursor-agent CLI share it) — all match what the ingest pipeline actually writes. Antigravity correctly excluded (detection-only).IN (...)list (coding_agents.rs:81) and theCODING_AGENTSarray (coding_agents.rs:34) list the identical four names, sototal_sand the per-agent breakdown can't disagree. File header,#[tracing::instrument], span, andinfo!summary all intact.Suggestions / nits
meridian-core/tests/readers.rs:83(coding_agents_unions_overlap_per_agent_and_total) still only seedsClaude Code+Codexand assertsagents.len() == 2. Per the port playbook, add aGitHub Copilotand aCursor Agentrow so the test exercises exactly the behavior this PR adds — it would guard against the regression being fixed (agents silently dropped) and against future SQL/const drift. As written,cargo teststill passes even if one of the two new names were fat-fingered in only one of the two locations.:34const vs:81inline SQL). They agree today, but a future one-sided edit would split total-vs-per-agent silently. sqlx can't bind an array cleanly, so the hardcodedINis defensible — but a comment tying the two together, or building theINplaceholders fromCODING_AGENTS.len()and binding the slice, would remove the trap.:2-9), but the agent set is now a deliberate divergence from the original route's two-element list. A one-line note in theCODING_AGENTSdoc-comment would keep the header honest.Verdict: Approve once a test seeding a
GitHub Copilotand aCursor Agentrow is added — the production change itself is correct and ready.🤖 Automated review via Claude Code
Ticket changed by: adityaharishch