v4.x: interactive invocation by model name — @deepseek / @nova / @gpt5.5 (not just @claude)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 4h 4m
- Merged PRs (30d)
- 1
Description
Feature request
Today interactive mode is triggered by @claude and runs whatever the caller's model_id is. A consumer should be able to invoke a specific model by name in a PR/issue comment — the way @claude works — e.g.:
@deepseek review the IAM changes@nova summarize this PR@gpt5.5 is this migration safe?@claude …(unchanged)
The mention itself selects the model/route for that one interactive run, overriding (or in addition to) the caller's default model_id.
Why
- Lets reviewers pick the right model per question without editing workflow YAML or maintaining one caller job per model.
- Natural fit for the model diversity we already run (Claude writes, a non-Claude reviews) — a human can pull in a second opinion from another family on demand.
- The routing already exists: the orchestrator maps
anthropic.* → claude,openai.* → codex-mantle, everything else →bedrock-generic. This is mostly a mention → model_id mapping layer on top ofenable_mention_detection.
Sketch (for discussion, not a spec)
- A configurable alias map, e.g.
@gpt5.5 → openai.gpt-5.5,@deepseek → deepseek.v3.2,@nova → amazon.nova-pro,@claude → ${default}. - Mention detection resolves the alias, sets
model_idfor that run, routes as usual. - Sensible default + allowlist so a comment can't invoke an un-provisioned/expensive model arbitrarily (cost + IAM scope — mantle
openai.*is already gated by the BEDROCK_ROLE_ARN policy). - Unknown alias → no-op or a one-line "unknown model" reply.
Targeting v4.x since it changes the interactive trigger contract.
Refs: #42, #43 (reviewer output quality — separate track).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with enable_mention_detection and the orchestrator's existing model_id routing, including the anthropic., openai., and bedrock-generic paths described in the issue. Done means configurable model-name aliases can select an allowed model for one interactive run, preserve @claude behavior, and define handling for unknown or unprovisioned aliases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ai, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100