I’m curious… Here’s something I’m trying for my overnight run for my latest work, using GSD v1 in the Claude Code CLI harness: (I’m at 30% usage left for the week, and 2.5 more days before this overnight run… I’m going to run out on a Max20 plan, as usual lately). I’d be curious if you are doing anything that might work better to mitigate such shallow usage windows with Claude MAX20, than this “sidecar” idea I’m trying: All confirmations locked. Pre-flight summary before kickoff: Verified:
- Codex 5.5 HIGH active (runtime metadata + reasoning task confirmed)
- Planning worktree clean (the earlier “modified” was a bare-config artifact)
- Pre-cherry-pick PR #286 squash verification already in RUNNING-LOG (line 3)
- Master’s recent hook hardening will flow into the unified worktree automatically (created off master) AFK execution plan:
- GSD discipline: per-phase plan-check → execute → Codex adversarial review → verify → SUMMARY.md → STATE.md → next phase. RUNNING-LOG updated by every dispatched agent.
- Model dispatch hierarchy enforced at every step: Codex GPT-5.5 high (default) → Sonnet 4.6 (only when Codex can’t do it) → Opus 4.7 (material design-judgment locks only). Per-agent assignments in plan files OVERRIDDEN to push as much work to Codex as possible.
- AFK gate: untracked install in unified worktree from buildout source (no commit, no contamination)
- Phases sequential 01→05; Phase 06 deferred separate PR
- All work local on 05-10-module-recovery-unified — NO PUSH, NO MERGE, NO PR
- Stop-and-ask reserved for hard-scope / destructive / material / policy-ambiguity. Everything else escalates through 5 tiers per ROADMAP and gets logged with [NEEDS_APPROVAL] in RUNNING-LOG One process flag worth knowing: /gsd-autonomous skill dispatches via Claude Agent tool by design — using it as-is would burn Claude quota. To honor your model-preservation directive, I’ll follow GSD discipline (structure, gates, RUNNING-LOG, STATE.md, SUMMARY.md per phase) but drive execution manually with codex exec calls for everything Codex can do, falling back to Claude subagents only when needed (e.g., parallel team coordination Codex CLI can’t do). You’ll see this clearly in the morning report — every Claude-subagent dispatch flagged as a “Claude usage burn” with reason. Kicking off now: creating the unified worktree off master, installing the AFK gate untracked, then dispatching Phase 01 plan-check to Codex 5.5 HIGH. Have a good rest — morning report waiting when you’re back. I prefer the Claude Code CLI harness… don’t know why - I guess it’s just what I’ve seen the best results with, especially autonomous work with all my hooks etc. I have had really poor luck (which is why this AFK run tonight is required at all… last night CODEX desktop environment using Claude sidecar occasionally was a total disaster, with similar gates etc. in place.) I also have another agent via OpenCode with GLM 5.1 doing some overnight work - not as capable, so I don’t trust it with this more complex stuff I’m working on right now. I need to maximize my MAX20 and PRO Codex plans out… I’m way past deadlines. I’m all ears… Help a girl out 😄 submitted by /u/N3TCHICK
Originally posted by u/N3TCHICK on r/ClaudeCode
You must log in or # to comment.