[copilot-session-insights] Daily Copilot Agent Session Analysis — 2026-07-25 #47954
Replies: 1 comment
|
Stone bot watch. Latest talk found. Run 30151690498 stomp here.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🤖 Copilot Agent Session Analysis — 2026-07-25
Executive Summary
Today's 12% completion sits below the 30-day mean of 17.6% and marks a pullback from yesterday's 36%, snapping a 4-day above-mean run (07-20 → 07-24). The important nuance: unlike recent high days that were single-branch artifacts, today's 6 successes are spread across 6 distinct branches (SCC = 0.17, the lowest concentration in the window) — this is genuine, distributed fleet health rather than one branch clearing its full gate suite. Fleet stayed clean: 0 loops, 0.69% tool-failure rate (all recovered), 0 orphaned branches.
Key Metrics
action_required)Success Factors ✅
Agentic (non-CI-gate) provenance: Every one of today's 6 successes came from an agentic workflow — 3× Running Copilot cloud agent and 3× Addressing comment on PR (Add post-update SHA integrity validation for actions-lock entries #47907, fix(lint): resolve 4 targeted golint-custom findings in pkg/cli, cmd/gh-aw, and pkg/linters #47910, refactor(linters): consolidate duplicated import-editing and file-lookup helpers into internal/astutil #47912).
Distributed completion, not a single-branch artifact: The 6 successes landed on 6 different branches.
Zero loops, high tool reliability: Across 6 rich conversation logs, 288 tool calls ran with only 2 recoverable failures and no repetitive/circular patterns.
Failure Signals⚠️
CI-gate approval saturation dominates: 44/50 sessions are
action_required— awaiting approval gates, not agent failures.CGO remains the zero-anchor CI type: CGO completed 0/5 again today, consistent with its multi-week 0-line.
gpt-5.3-codexcarried all recoverable errors (see Experimental Analysis): the lone codex run held 2/2 of the day's tool failures while all sonnet runs were clean.Prompt Quality Analysis 📝
Conversation logs show agentic sessions opened with substantial, well-scoped user prompts (8k–16k chars) and immediately invoked a skill or targeted search — a high-quality pattern correlated with the 100% agentic success rate today.
High-Quality Prompt Characteristics (from today's 6 agentic logs)
skillorsearch_code_subagentcall rather than blind editing.Low-Quality Signal
Orphaned Branch Escalation Alerts 🚨
Summary
Escalation Candidate Details
Escalation Candidates
✅ No orphaned branches exceed the escalation threshold today.
main(no PR branch reached the ≥5-gate footprint required to orphan).fix/code-scanning-651-652-graphql-injection,signed/jsweep/issue-title-dedup) have 0 active gate runs, so neither qualifies for escalation.CI Waste Estimate
Notable Observations — Loop Detection & Diagnostics
Loop Detection
Tool Usage (across 6 agentic conversation logs)
bash(125),read_bash(31),github(29),view(25),edit(16),report_progress(14),rg(13).parallel_validation×1,rg×1 — both recovered.Context Issues
Experimental Analysis
This run included experimental strategy: MEDR — Model Efficiency Divergence Ratio
Today's 6 agentic logs spanned two backend models (
claude-sonnet-4.6×5,gpt-5.3-codex×1), enabling a per-model efficiency comparison. MEDR = mean turns of the higher-turn model ÷ mean turns of the lower-turn model, with tool-failure share attributed by model.Findings:
gpt-5.3-codexrun used 73 turns / 76 tool calls vsclaude-sonnet-4.6's mean 34.4 turns / 42 calls (n=5).Effectiveness: Medium (numerator rests on n=1 codex run — directional only).
Recommendation: Refine. Re-run on the next mixed-model day; if codex consistently exceeds ~1.8× sonnet turns with a failure monopoly, MEDR becomes a per-model efficiency early-warning. Confound: task difficulty and prompt size differ per run and are not controlled.
📈 Session Trends Analysis
Completion Patterns
Completion rate oscillates in a sawtooth between ~2% trough days and ~40–54% peak days; today's 12% is a mid-low point that ends a 4-day above-mean streak. Successful completions (green) and gate-blocked counts (red) remain near-perfect mirror images, confirming that the headline number is driven almost entirely by whether agentic branches clear their gate suites on a given day.
Duration & Efficiency
Average duration stays low (today ~2.0 min) because the median is pinned at 0 by the mass of gate-stub sessions; the visible spikes (07-22 ≈15m, 07-20 ≈9.9m) are days with long agentic runs. Loop counts remain at zero across the entire window (single bar on 07-17), so longer averages reflect genuine work, not looping.
Actionable Recommendations
For Users Writing Task Descriptions
For System Improvements
action_requiredsessions are approval-gate stubs, not agent failures — surfacing them separately would make the true agent success rate legible.For Tool Development
turn=log lines. A first-class per-model turns/tokens/failure summary would make efficiency divergence trackable without log scraping.Historical Trends & Statistical Summary
Trends Over Time
Statistical Summary
Next Steps
Analysis generated automatically on 2026-07-25.
Run ID: 30149242598
Workflow: Copilot Session Insights
References:
All reactions