/rubber-duck is offered in the composer but its agent is unavailable

Summary

/rubber-duck is available in the composer, but invoking it produces an “agent unavailable” message. Copilot then uses a General Purpose agent instead. This has happened across multiple GPT-6 Astra sessions.

Steps to reproduce

1. Open a session with GPT-6 Astra selected and Rubber Duck enabled.
2. Ask Copilot to draft something.
3. Run /rubber-duck this draft.
4. Observe the unavailable-agent message and General Purpose fallback.

Actual behavior

Copilot responds:

The named rubber-duck agent isn’t available in this session. I’ll use an independent reviewer to critique the draft’s credibility, point of view, and reason to meet.

The resulting task is labeled General Purpose. The requested Rubber Duck review does not run.

Expected behavior

The command should invoke Rubber Duck. If the session, model, or account is ineligible, the app should explain the restriction before accepting the command.

Environment

• GitHub App: 1.1.19
• Bundled Copilot runtime: 1.0.84-4
• Platform: macOS, Apple Silicon
• Model: GPT-6 Astra
• Reasoning effort: High

Investigation findings

A read-only investigation found:

• The app’s Rubber Duck toggle is enabled.
• Running Copilot processes receive RUBBER_DUCK_AGENT=true.
• rubber-duck is absent from the session’s callable agent list.
• The app’s slash-command handler checks the feature toggle, then injects a request to invoke the agent without checking runtime availability.

The runtime has additional model-eligibility checks, but the exact reason for exclusion was not established. Please investigate both the missing agent and the command’s failure to surface the eligibility restriction.

Inizia dal gestore dei comandi slash dell’app e segui come l’interruttore di Rubber Duck diventa una richiesta di invocazione. Confronta tale richiesta con l’elenco degli agenti richiamabili della sessione e con i controlli di idoneità del modello del runtime, usando i passaggi per riprodurre il problema di GPT-6 Astra. Il lavoro è completato quando il comando invoca Rubber Duck quando è idoneo e mostra la restrizione prima di accettarlo quando non è disponibile.