COPILOT CLI ADDS 'RUBBER DUCK' CROSS‑MODEL REVIEWS AND OPENTELEMETRY TRACING YOU CAN ACTUALLY USE
GitHub Copilot CLI now offers an experimental cross-model “Rubber Duck” reviewer and ships meaningful OpenTelemetry hooks to observe agent runs. GitHub introdu...
GitHub Copilot CLI now offers an experimental cross-model “Rubber Duck” reviewer and ships meaningful OpenTelemetry hooks to observe agent runs.
GitHub introduced Rubber Duck in Copilot CLI experimental mode, a second-opinion agent that uses a different model family to critique plans and outputs. When the orchestrator is Claude Sonnet, Rubber Duck runs GPT‑5.4. In GitHub’s evaluation, Sonnet 4.6 + Rubber Duck closed 74.7% of the gap to Claude Opus 4.6 on hard, multi-file, long-running tasks.
Recent releases tighten observability. Copilot CLI 1.0.19 adds OpenTelemetry tweaks like INTERNAL subagent spans and a streaming latency attribute (github.copilot.time_to_first_chunk) 1.0.19. The 1.0.20-0 pre-release adds a copilot help monitoring topic with OTel config examples and makes Azure OpenAI BYOK default to the GA versionless v1 route if no API version is set (1.0.20-0, releases).
A second, different model reduces silent planning mistakes on complex changes and long-running jobs.
Built-in OpenTelemetry gives you traces to monitor agent behavior, latency, and reliability in real workflows.
-
terminal
Run a multi-repo or multi-file refactor with and without Rubber Duck; compare success rate, review comments, and time-to-fix.
-
terminal
Export Copilot CLI traces to your OTel collector; validate subagent span kinds, the time_to_first_chunk attribute, and end-to-end timelines.
Legacy codebase integration strategies...
- 01.
Enable OTel export and map Copilot spans into your existing tracing backend; confirm INTERNAL subagent spans don’t break dashboards.
- 02.
Gate
/experimentaland model choices; if you use Azure OpenAI BYOK, verify the versionlessv1routing matches your compliance requirements.
Fresh architecture paradigms...
- 01.
Adopt Copilot CLI with Rubber Duck as the default flow for planning and execution on new services.
- 02.
Bake OTel config, MCP persistence, and model settings into devcontainers or bootstrap scripts from day one.