aws / aws/amazon-q-developer-cli

Improvements for MCP Prompts

Aperta
#2,789 1 commento 3 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

I've been playing around with Q CLI's support for MCP prompts and have some feedback for improvements that I think would make a big difference in the overall experience:

### UX low-hanging fruit

1. `/prompts list` should include the prompt description so it's easy to understand what each prompt does
2. There should be something like `/prompts details ` that shows all properties of the prompt returned by the MCP server. Specifically argument details.
3. `/prompt get` causes Q to go into a Thinking loop before outputting the prompt. Is this necessary? Shouldn't fetching the prompt be purely deterministic? Edit: I didn't realize that `/prompt get` not only fetches the prompt but also sends it to the model for processing. So `/prompt get myprompt` is the same as running `@myprompt`. So the UX should be modified to output the prompt so it's clearer that this is what's happening.
4. If you try to call a prompt without passing a required argument, you get this really ugly error with a raw JSON output from the MCP server.

### Feature Request

You should be able to pin a MCP server prompt as context, both in agent configuration JSON and via `/context add`For the last one, picturing being able to do something like this:

```
> /context add @some-mcp-prompt arg
```

This will expand the prompt and pin it to context. For agent configuration, you could support something like `prompt:///...` in addition to `file://` supported today. Not quite sure how friendly the URL format will be for prompt arguments, but you could do get params encoded in the URL although depending on the prompt, that could get very long...

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Non vengono indicati file, test o punti di ingresso dell’implementazione. Inizia riproducendo in Q CLI i flussi di prompt MCP elencati, quindi separa la richiesta in elenco/dettagli dei prompt, output del recupero e gestione degli argomenti mancanti, nonché contesto del prompt fissato. Il lavoro sarebbe completato quando saranno concordati l’ambito e i controlli di accettazione per i miglioramenti selezionati.

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
Abbastanza chiara
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.