/agent <name> - Allow direct invocation of agents by name
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
### Describe the feature or problem you'd like to solve
Currently, `/agent` only opens an interactive browser/picker with no way to pass an agent name as an argument. Users who know the agent name they want must scroll through the full list every time. This adds friction, especially with many agents installed.
### Proposed solution
Support /agent to directly invoke a named agent (e.g., `/agent my-agent`). If the name doesn't match, fall back to the interactive picker filtered by the input string. This mirrors how /model and other commands accept optional arguments.
### Example prompts or workflows
1. Quick invoke by name: `/agent my-test-agent` - immediately starts the agent without navigating the picker. Saves time when you know what you want.
2. Fuzzy match with fallback: `/agent test` - filters the agent list to matches containing "test", showing only relevant options. Falls back to filtered picker when no exact match.
3. Chained with context: `/agent my-test-agent generate tests for src/auth/handler.ts` - invoke agent and pass initial prompt in one command, skipping the extra round-trip.
4. Scripting/repeatability: User frequently runs the same agent on different files. `/agent my-agent` lets them hit up-arrow, change the file path, and re-run - not possible with an interactive picker.
5. Discoverability without friction: `/agent --list` to quickly print available agent names (one-line each) without entering the interactive picker, so users can learn names then invoke directly.
### Additional context
_No response_
贡献指南
调研方向
从 /agent 命令入口开始,将其参数处理与 /model 及其他命令进行比较。测试精确名称调用、过滤后的 fallback、串联的 prompt 文本和 --list;完成标准是这些工作流能够正常运行,且不会破坏现有的交互式 picker。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- shell
- 领域
- cli
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100