Code Overlord vs coding CLIs: what the client adds

One instruction to Claude: have Codex implement the change, ask another agent to review it, correct the findings, run independent checks and get a final review. Setup, approvals and waits are shortened in this recording.

Watch the sidebar. Codex appears as a new session. The hierarchy shows it beneath the agent that called it. This is the coordinator creating its own worker.

I open Codex inside the same window. The implementation is ready, with thirty tests passing. The coordinator checks its result and moves the workflow forward.

Now a separate Claude reviewer joins the workspace. The coordinator sends it the review task. I switch back to the conversation, where both Claude sessions have their own tabs.

The review finds real issues in the keyboard handling and tests. Those findings go back to the original implementer through the coordinator.

Back in Codex, the requested corrections are complete and forty tests pass. The task stayed with its implementer; I did not copy the review between agents.

The coordinator creates another session for independent checks. Watch its tab appear alongside the reviewer. Each stage has its own agent and its own visible work.

The coordinator also created an independent checker. Here is its own session, confirming the test results and that the work remains uncommitted.

Back at the coordinator, here is Code Overlord’s completion message from the checker. The coordinator reads the result and sends the work into final review.

Final review catches one more keyboard-layout issue. The coordinator sends a precise correction back to Codex and keeps the reviewer ready to verify it.

Codex finishes that correction with forty-two passing tests. The completion returns to the coordinator, which starts a fresh check alongside final verification.

The reviewer confirms that all eight findings are fixed, forty-two tests pass, and the regression checks catch the broken versions. Its review is complete.

The fresh checker independently verifies the updated keyboard behavior and reports all five checks passed. Both the checker and reviewer have now finished.

The original coordinator brings the whole run together: implementation, review, corrections, checks and the final verdict. The changes are left here for my review.

Here is the completed team in its native hierarchy. One workflow instruction; real agents handling the handoffs. Everything stayed inside Code Overlord.

Open the agent switcher on your phone. Claude, Codex and Pi are all running in this workspace. Choose the conversation you want to control.

With Pi selected, type a short file request and press Send. This goes into the actual agent conversation on the desktop.

Pi reads the file and reports the package name. Its live conversation is available here on your phone.

Switch to Claude. Ask a different question, then press Send. The selected agent and its conversation are shown above your message.

Claude reads the project document and replies. Switching agents keeps each request and answer in the right conversation.

Back in Code Overlord on the desktop, select that Claude tab. The phone request and its answer are both here.

Choose Codex from the same phone switcher. Send a request for the page title. There is no need to change mobile apps.

Here Codex asks for permission to read the local file. Open Special and press Enter to approve this request once. The phone sends the key to the selected agent.

Codex continues after approval and reports the title. The request, approval and result stay together in its conversation.

Select Codex on the desktop. The same phone request, one-time approval and completed answer are visible inside Code Overlord.

Switch back to Pi and its phone request is here too. Three different agent types, controlled from one mobile interface, with their work retained on the desktop.

Use the workspace selector to open Ember Council. The header changes to the workspace you selected. Other workspace names have been hidden for privacy.

Open its agent switcher. These are the conversations in Ember Council. The house icon marks agents running locally. Choose your workspace, then your agent, from the same phone interface.

Ask Claude to write a short plan and a linked handoff document. I leave the conversation open. Setup and waits are shortened.

Watch the sidebar as the files are saved. Both documents appear in Peruse, while my conversation keeps its place.

One click opens the plan as a formatted document, with headings, a checklist and a table. It is all inside Code Overlord.

The handoff is linked from the plan. I follow that link and choose Open in Peruse to read the other document.

Raw shows the Markdown behind the document. I can switch back to the formatted view whenever I want.

Back in the same conversation, I ask Claude to tick the first item and update the final status.

The existing preview marks the document as updated. The first item is checked, and the status now says Ready for review.

On my phone, I open Scrolls and choose the same plan. The formatting and updated values are here too. No hunting through folders.