github / github/copilot-cli

Support activation welcome cards for custom Copilot CLI agents

Aperta
#4,798 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

triage
Lingua principale
Shell
Stelle
11.2k
Fork
1.9k
Merge medio
14h 16m
PR unite (30g)
6

Descrizione

Describe the feature or problem you'd like to solve

Problem Custom Copilot CLI agents are selected with /agent <agent-name>, but selection only changes the active profile. The CLI does not show an immediate, agent-defined welcome or onboarding message. This creates a discoverability problem for specialized workflow agents. A new user can successfully select an agent but still not know what it is for, which goals it supports, or how to begin. The user must already know an appropriate first prompt before the agent can help.

Proposed solution

Add a first-class optional welcome declaration to custom-agent metadata and
render it directly in the Copilot CLI UI after a user successfully selects an
agent with /agent.

Illustrative agent profile:


name: analysis-agent
description: "Helps investigate reports, inputs, and execution results."
welcome:
title: "Welcome"
message: >
This agent can help investigate existing results, analyse supplied inputs,
and prepare focused follow-up work.
suggestedPrompts:
- "Investigate an existing report or execution result"
- "Analyse a supplied input"
- "Help me understand an existing failure"

CLI behavior:

  1. The user selects a custom agent with /agent <agent-id>.
  2. Once selection succeeds, the CLI reads the selected agent's optional
    welcome metadata.
  3. If present, the CLI renders a lightweight terminal welcome card immediately.
  4. The card displays the title, message, and optional suggested prompts.
  5. Selecting a suggested prompt deliberately submits that text as a normal user
    prompt. The user may instead dismiss the card and enter any free-form prompt.
  6. The welcome card is UI-only:
    • it does not invoke the model;
    • it does not consume AI credits;
    • it does not create synthetic user or assistant messages;
    • it does not alter conversation history.
  7. Agents without welcome metadata retain today's behavior unchanged.

Suggested terminal rendering:

┌ Welcome ───────────────────────────────────────────────┐
│ This agent can help investigate existing results, │
│ analyse supplied inputs, and prepare focused work. │
│ │
│ What would you like to do? │
│ │
│ 1. Investigate an existing report or execution result │
│ 2. Analyse a supplied input │
│ 3. Help me understand an existing failure │
│ │
│ Press a number, or Esc to enter your own prompt. │
└────────────────────────────────────────────────────────┘

Example prompts or workflows

Consider two custom agents supplied by a plugin:

  • An analysis-oriented agent for investigating existing artifacts, reports,
    execution results, and input data.
  • A developer-oriented agent that includes those capabilities plus source editing,
    validation, review, and delivery workflows.

After selecting the analysis agent with /agent, the CLI could immediately show:

Welcome

This agent can help investigate existing results, analyse supplied inputs, and
prepare focused follow-up work.

What would you like to do?

  • Investigate an existing report or execution result
  • Analyse an input or dataset
  • Prepare focused follow-up work
  • Understand an existing failure

The developer-oriented agent could show the same concise user goals with one short
additional note that it also supports implementation, validation, and delivery.

Requested behavior

Please add an optional custom-agent activation/welcome contract that the CLI renders
immediately after a successful interactive /agent selection.

Suggested shape (illustrative only):

welcome:
title: "Welcome"
message: "This agent can help with..."
suggestedPrompts:
- "Investigate an existing report"
- "Analyse a supplied input"

Additional context

No response

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia individuando il parsing dei metadati di custom-agent e il flusso interattivo di selezione di /agent nella Copilot CLI. Traccia il modo in cui la selezione aggiorna il profilo attivo, quindi determina dove inserire una scheda di benvenuto solo per la UI e l’invio di un prompt suggerito; il lavoro è completato quando i metadati di benvenuto vengono visualizzati dopo una selezione riuscita, senza modificare la cronologia o il comportamento degli agenti che ne sono privi.

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

Valutazione

Stack tecnologico
shell
Ambito
cli
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Attiva
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.