← All workflow demos

Tell one agent. Watch the team appear.

Workflow film · 2:45

Tell one agent. Watch the team appear.

Full instructions →

Real app recording · Original AI voice and presenter portrait · Captions included · Cuts and playback speed shown in the film. Narration uses Code Overlord’s theatrical English.

Read the transcript

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.

Implementation, independent Claude review and checks. Watch the agents appear and return their results to the coordinator.

Try this workflow yourself

Launch the coordinator inside Code Overlord. Install and authenticate the agents you want to use, and choose a separate agent for the review session.

Implement the saved-view change in this workspace. Use Code Overlord’s session tools to have a separate Claude agent review the diff and test coverage without editing. Send its confirmed findings back to the implementer. Have a test agent run the relevant checks, then a final reviewer verify the result. Coordinate every handoff and report the evidence and any unresolved issues. Leave the changes ready for my review.

Choose agents and tools available in your setup. Ask the coordinator to report each result and anything that needs your attention before the next stage can proceed.