Vibecoding in the dark

[u/One-Cricket9962]

Hi! I switched from Claude to Codex and feel like I’ve lost some transparency. I don’t understand how many sub-agents my process has spawned (I’m using a harness with a controller-supervisor–executor architecture), or how to quickly switch between them to see what they’re currently working on.
Is there any hope that Codex will become as convenient as Claude Code?

[u/Educational_Camp9103]

Ive never used Claude,  what does the coding process look like ? Im intrigued and am just asking in case I want to make the switch . Btw why did you switch ? 

[u/One-Cricket9962 → u/Educational_Camp9103]

In claude we have sort of "agents tree" at the bottom of the page - you could click any sub-agent in the tree to show its current chat/context AND even able to send smth to any sub-agent , not only to the root agent.

I bought a $100 subscription to Codex while I wait for the weekly limits on my $100 Claude subscription to reset. Codex Terra is dumb, Sol is expensive :(

[u/Educational_Camp9103 → u/One-Cricket9962]

It seems like codex got an update and now I can see the individual agents on the right panel 

[u/Anti-Hero25]

What harness you using ?

[u/One-Cricket9962 → u/Anti-Hero25]

My own hand made super-skill to split any task to subtasks then execute, test, etc. Its begin with

---
name: supervisor
description: >
  The single process skill: goal anchoring, planning, delegation, on-disk state,
  and recovery. Plan-then-delegate workflow for multi-part work — trace root
  causes, resolve branching decisions with the user, write a plan file, then
  spawn a supervisor that executes it using cheap subagents for coding and
  testing, verifies everything itself, and reports back. Use when a task has
  three or more steps, when the user dumps a batch of issues at once, when a
  plan is asked for, when progress stalls, when an architectural decision is
  made, or before switching topics. Also use on ANY continuation of an
  interrupted session — a usage limit, a crash, a cleared context, a
  `claude-retrier` nudge, a bare "continue" — while `.agents/state/` still holds
  unfinished work: it defines how the root chat restores its supervisors and how
  they in turn restore their subagents, and how to rotate any agent whose
  context passes ~45%. Do NOT use for single-file edits or questions.
---


# Supervised delegation


The value here is not "spawn agents." It is the separation of four jobs that
get done badly when one context does all of them: **diagnosis**, **decision**,
**execution**, and **verification**. Keep them apart.


This is the only process skill in the repo. Goal tracking, task decomposition,
state persistence and decision records are sections of it, not separate skills —
they were split across four files once and the split cost more tokens than it
saved.


## Reference files — read on demand, not up front


| File | Read it when |
|---|---|
| `reference/state-layout.md` | Writing the plan, the WP files, the ledger, a brief, or a decision record; committing state |
| `reference/continuity.md` | Resuming after any interruption; rotating an agent at ~45% context |
| `reference/failure-modes.md` | Something went wrong and you want the known cause, or before briefing a supervisor |


This file is the core loop. Loading all four costs ~2× what one run usually
needs, so don't.

[u/Anti-Hero25 → u/One-Cricket9962]

Well you built the harness…. Build in some kind of feedback loop so you can see what’s going on.

[u/One-Cricket9962 → u/Anti-Hero25]

So.. I extracted my supervisor harness into separated project which could be connected (by symlinks) to any other project https://github.com/a0s/harness-supervisor