[copilot-cli-research] Copilot CLI Deep Research - 2026-05-16 #32544
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Copilot CLI Deep Research Agent. A newer discussion is available at Discussion #32749. |
Beta Was this translation helpful? Give feedback.
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.
-
Analysis Date: 2026-05-16
Repository: github/gh-aw
Scope: 229 total workflows, 128 using Copilot engine (56%), 99 simple form + 29 extended form
📊 Executive Summary
This is the 6th consecutive deep research run tracking Copilot CLI feature adoption across this repository. The overall Copilot footprint has grown from 121 → 128 workflows (56% of the repo). Strong cache-memory adoption continues (94 workflows), version pinning has rebounded (10 workflows, up from 0 last run), and web-search via MCP has made its first appearance (2 workflows). However, three persistent gaps remain unresolved for 9+ consecutive runs:
engine.args,engine.env, andengine.api-targetare all at zero usage despite being documented and supported features.The most significant finding is that 5 custom agent files go completely unused in production workflows, and
max-runs— the invocation cap feature — is used by only 1 workflow (vs. 128 that could benefit). Model selection is largely ignored (only 6 workflows usemodel: smallout of 128), leaving significant cost-optimization potential on the table.Critical Findings
🔴 High Priority Issues
1.
engine.args,engine.env,engine.api-target— Zero Usage (9+ Consecutive Runs)These three documented features have never been used in any production workflow.
engine.envwould be valuable for BYOK mode and custom debugging.engine.argsenables passing custom CLI arguments for specialized scenarios. These persistent gaps suggest either poor discoverability or unclear use cases.2. 5 Unused Custom Agent Files
.github/agents/contains 10 files, but 5 are never referenced in any workflow:grumpy-reviewer,interactive-agent-designer,w3c-specification-writer,create-safe-output-type,custom-engine-implementation. These represent development investment that is not delivering value.3.
max-runsSeverely UnderusedOnly 1 workflow (
daily-safe-output-optimizer, max-runs: 200) uses this invocation cap. All other 127 Copilot workflows implicitly use the default of 500, meaning runaway workflows could consume 500 invocations before stopping. For daily/weekly scheduled tasks, a lower cap (20–50) is more appropriate.🟡 Medium Priority Opportunities
4. Model Selection Gap (97/128 workflows use default model)
Only 6 workflows explicitly use
model: smalland 3 usemodel: large. With 97 workflows on the default model, there's potential for significant cost reduction by usingmodel: smallfor read-only analysis tasks (architecture-guardian, breaking-change-checker, etc.).5.
engine.harness— Never UsedThe custom harness script feature (
engine.harness) allows replacing the built-in retry/error-handling wrapper. Zero adoption may indicate teams don't know it exists or don't need it yet.6. 20 Copilot Workflows Missing
safe-outputsWorkflows like
copilot-pr-merged-report,dead-code-remover,daily-issues-report,terminal-stylisthave no safe-outputs configuration — they cannot publish results back to GitHub. It's unclear if these are intentionally output-less or if they're missing a required configuration.View Full Analysis
1️⃣ Current State Analysis
View Copilot CLI Capabilities Inventory
Copilot CLI Capabilities Inventory
Runtime Configuration
engine: copilot/engine: { id: copilot }— engine selectionengine.version— pin to specific CLI version (e.g.,"0.0.422")engine.model— override the AI model (e.g.,gpt-5,gpt-5-mini,small,large)engine.command— custom executable pathengine.args— additional CLI arguments passed to Copilot CLIengine.env— environment variables injected at engine runtimeengine.agent— custom agent file from.github/agents/(Copilot-exclusive)engine.api-target— custom API endpoint (GHEC/GHES)engine.bare— disable automatic context loading (AGENTS.md, custom instructions)engine.harness— replace built-in retry/error-handling harness script (Copilot-exclusive)Execution Control
max-continuations— autopilot mode with N consecutive runs (Copilot-exclusive)max-runs— invocation cap per workflow execution (default: 500)timeout-minutes— job timeoutSecurity & Sandboxing
sandbox.agent: awf— AWF (Agentic Workflow Firewall) network sandboxsandbox.agent: srt— SRT sandbox variantnetwork.allowed— allowlist of domains/presetsstrict: true— strict mode validationengine.env:COPILOT_PROVIDER_BASE_URL,COPILOT_PROVIDER_API_KEY,COPILOT_PROVIDER_BEARER_TOKENTools & Integrations
tools.github— GitHub MCP server (toolsets, mode: gh-proxy)tools.bash— shell access with glob patternstools.edit— file editingtools.cli-proxy— CLI proxy tooltools.web-fetch— HTTP fetchtools.web-search— web search via MCPtools.cache-memory— persistent cross-run memorytools.playwright— browser automationView Usage Statistics
Usage Statistics
2️⃣ Feature Usage Matrix
3️⃣ Missed Opportunities
View High Priority Opportunities
🔴 High Priority
Opportunity 1:
max-runsfor All Scheduled Workflowsmax-runsinvocation cap defaults to 500 but is only configured in 1 workflowmax-runs: 30(or appropriate value) to each scheduled workflowOpportunity 2: 5 Unused Custom Agent Files
grumpy-reviewer,interactive-agent-designer,w3c-specification-writer,create-safe-output-type,custom-engine-implementationexist but are never usedgrumpy-reviewer)Opportunity 3:
engine.envfor BYOK and Custom Configurationengine.envallows injecting environment variables to customize Copilot behaviorView Medium Priority Opportunities
🟡 Medium Priority
Opportunity 4: Model Selection for Cost Optimization
model: smallcosts significantly less for analysis/read-only tasks;model: largefor complex reasoningarchitecture-guardian,breaking-change-checker,ci-coach,daily-syntax-error-quality,linter-minerOpportunity 5: Missing
safe-outputson 20 Copilot Workflowssafe-outputsconfigurationcopilot-pr-merged-report,dead-code-remover,daily-issues-report,daily-secrets-analysis,terminal-stylist,daily-testify-uber-super-expert,mcp-inspector, etc.Opportunity 6:
max-continuationsfor Long-Running Workflowsmax-continuationsdespite it being a Copilot-exclusive featuredead-code-remover,repository-quality-improver,daily-workflow-updater, and other refactoring/improvement workflowsOpportunity 7:
engine.barefor Self-Contained WorkflowsView Low Priority Opportunities
🟢 Low Priority
Opportunity 8: Version Pinning for Critical Workflows
daily-issues-report,daily-performance-summaryversion: "0.0.422"in the engine blockOpportunity 9:
engine.harnessfor Custom Retry Logic4️⃣ Specific Workflow Recommendations
View Workflow-Specific Recommendations
Workflow:
dead-code-remover.mdmax-continuations: 5(dead code removal is multi-step), addpush-to-pull-request-branchsafe-output to surface changesWorkflow:
architecture-guardian.mdmodel: small✅, safe-outputs configured ✅, 20-min timeoutmax-runs: 20to cap invocations for this analysis workflowWorkflow:
daily-issues-report.mdWorkflow:
contribution-check.mdmax-continuations: 20✅, usescontribution-checkeragent ✅Workflow:
archie.mdadr-writercustom agent ✅, imports serena-go MCPlargefor better reasoning on architectural decisions.5️⃣ Trends & Insights
View Historical Trends (6 Runs)
Key Trend: Web-search adoption started this run. Version pinning rebounded strongly (0→10). The Copilot CLI ecosystem is growing steadily. Persistent zero-usage features (api-target, harness, args, BYOK) likely indicate these are enterprise/advanced features not needed for this internal repo.
6️⃣ Best Practice Guidelines
Based on this research, here are recommended best practices for Copilot workflows in this repository:
max-runs: Default of 500 is too high for most scheduled workflows. Use 20–50 for analysis, 100–200 for complex refactoring.model: smallfor read-only workflows: Architecture analysis, code review, report generation don't need the default (larger) model.contribution-checkerandadr-writerpatterns show the value — encapsulate domain expertise in agent files.max-continuationsfor multi-phase work: Workflows that improve/refactor code need multiple passes; configure autopilot mode.safe-outputsor document why not: Every workflow should either publish results to GitHub or have a clear comment explaining the output mechanism.strict: true: Already used by ~60% of workflows; should be standard for all new workflows.7️⃣ Action Items
Immediate Actions (this week):
max-runsto the top 10 highest-timeout scheduled Copilot workflowssafe-outputsor a comment to the 20 workflows missing itShort-term (this month):
model: smallto read-only analysis workflows (architecture-guardian, breaking-change-checker, ci-coach)max-continuations: 3-5to refactoring workflows (dead-code-remover, repository-quality-improver)engine.argsandengine.envuse cases with examples from this repoLong-term (this quarter):
shared/copilot-defaults.md) with standardmax-runs,strict, andtimeout-minutesView Supporting Evidence & Methodology
📚 References
docs/src/content/docs/reference/engines.mdpkg/workflow/copilot_engine.go,pkg/workflow/copilot_engine_execution.go.github/agents/(10 files)memory/copilot-cli-researchbranchResearch Methodology
Analysis used
grepand shell scripting to survey all 229 workflow markdown files in.github/workflows/. Features were counted by searching for specific YAML keys in the frontmatter of Copilot-engine workflows. The Go source code (pkg/workflow/copilot_engine*.go) was reviewed to understand available but undocumented features. Historical trends were retrieved from repo-memory (/tmp/gh-aw/repo-memory/default/). Prior research notes spanning 5 runs from 2026-05-10 to 2026-05-14 were used for trend comparison.Generated by Copilot CLI Deep Research (Run: §25953071091)
Beta Was this translation helpful? Give feedback.
All reactions