aws / aws/amazon-q-developer-cli

Feature request: UX for maintaining list of available tools in cli-agents

Aperta
#2,840 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Rust
Stelle
2k
Fork
439
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

CLI agent configurations include an allowlist of available tools (the `tools` list, not the `allowedTools`list). For an agent that includes large MCP servers (or many MCP servers), where the user wants to control for tool context consumption but still have a large handful of tools available, the `tools` list can include dozens of entries. And, as MCP servers continue to evolve tool names may change or new tools may become available that would benefit a given agent configuration.

Currently `/tools` run within an agent lists only the tools that are available to the agent. I can't find any way to have Q CLI list out all agents that *could possibly* be available from the loaded MCP servers, and therefore can't effectively review and update my `tools` list to account for these changes.

A better UX for maintaining `tools` lists could be as simple as adding a `/tools --all` command which shows all possible tools (leaving it to the user to append `@mcp-server-name/` ahead of tool names before pasting them into the agent config. Or it could be as involved as displaying a scrollable list of all potentially available tools, showing which are included in the current agent and which are not, and letting the user toggle availability on each tool, with Q CLI modifying the agent config as these toggles change.

Does the Q CLI team have any specific plans for agent maintenance workflows including the `tools` list that are already aiming to solve this?

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

La issue non indica file né test. Inizia esaminando il comando `/tools` esistente e l’allowlist `tools` della configurazione dell’agente, quindi determina il workflow di manutenzione desiderato; il lavoro è completato quando è stata definita una UX per elencare e aggiornare tutti gli strumenti MCP potenzialmente disponibili.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
ai, cli
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.