You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[deep-report] Right-size Schema Consistency Checker: add chunking or deterministic pre-steps to cut 8.1M-token/138-turn runs #28750
The Schema Consistency Checker consumed 8.1M tokens in a single run across 138 turns (Apr 20–27 weekly window) — the highest per-run token cost in the entire repository. Its cache efficiency is only ~14.9%, meaning most context is being re-read rather than cached. This represents a compounding cost as the workflow runs.
Evidence: Weekly Workflow Analysis #28687, Agentic Observability Report #28682 — both flag this as the primary cost optimization target.
Recommended approach:
Add a deterministic pre-step that fetches/diffs schema files and writes results to /tmp/gh-aw/agent/schema-diff.json before the agent starts — eliminates bulk data-gathering turns (~40–60 turns)
Split the workflow into smaller batch jobs (e.g., one per schema area) rather than one monolithic run
Add max-turns: 60 cap to prevent runaway (current 138 turns = no guard)
Increase cache hit rate by structuring prompts to reuse static context
Expected Impact
Target: reduce from 8.1M → ≤ 3M tokens/run. With weekly cadence: ~5M tokens/week reduction.
Activity
github-actions commentedon Apr 28, 2026
🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
Caution
Security scanning requires review for Issue Monster
Details
Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.
Review the workflow run logs for details.