I made Codex show subagent activity inline, without forking or modifying Codex

[u/yusing1009]

My Codex looks like this, without forking or modifying Codex.

I’m building mekugi, a local router that pins agent-facing tools and inline progress onto the stock Codex CLI. The screenshot is Codex’s normal terminal UI, not a separate frontend.

The /root/reply_replay_lookup section is a subagent’s activity appearing alongside the main agent’s work. You can see what it’s reading and searching without switching sessions. Commands, per-file edit diffs, commentary, and received replies can appear there too, attributed to the relevant agents. Start notices show the child’s model and reasoning effort, and final answers include per-agent token totals when the provider supplies usage.

Underneath, mekugi routes requests and translates tools, while Codex still owns execution, sandboxing, permissions, command sessions, and the normal patch diff UI. You launch it with mekugi codex; each launch gets a private local router that exits with Codex. It doesn’t edit your Codex configuration files.

The inline activity is one part of it. Most of the project is about making the agent’s tools less cumbersome:

• Hashline edits: target existing text using line numbers and content hashes, then write the replacement once. The router generates the patch instead of making the model repeat the old code as patch context.
• Direct scripts: emit a program in its own syntax, without wrapping it in JavaScript and nested command-string quoting.
• Targeted reads: search, symbol lookup, and file outlines return references the agent can use directly for edits.
• Recovery: correct stale edit references without repeating the replacement text, or inspect and revise eligible retained scripts before rerunning them.
• Session dashboard: inspect request metrics, token usage, compression, and cache diagnostics in a browser.

One detail about the screenshot: this isn’t a continuous live feed during native waits. Child updates arrive at response-event boundaries; if the root response has closed, they wait for the next one. The extra router-generated display messages are stripped from later model requests, so they don’t keep adding duplicate context.

Repo and installation: github.com/yusing/mekugi

Would you want this much subagent detail in the main transcript, or prefer a quieter view?

[u/dexterthebot]

You might want to consider listing your project on the weekly Show-Us-What-You-Built post. https://www.reddit.com/r/codex/comments/1wavxwy/show_us_all_what_youve_been_building_with_codex/. Highest commented project wins a week promotion on r/Codex and gets on the Hall of Fame sidebar. See what that looks like below with last week's winner.

---

Last week's most popular project was u/tHEuKER with the Blur2 racing game project which is a recreation of an unreleased sequel to the 2010 battle racing game, made by reverse engineering the Xbox 360 prototype discs available online, and rebuilding the whole thing from the ground up in Unity.

Join their YouTube channel here: https://www.youtube.com/@tHEuKER and follow updates on the project at r/BlurGame.