yagura v0.1.0 lets Claude Code and Codex CLI work side by side

The release addresses a specific friction that appears once developers use more than one agent CLI: output has to be copied by hand between terminals, waiting windows get forgotten, and closing a terminal kills the running agent. yagura's windows are real terminals, held by a background daemon, so agents keep running when the GUI is closed, and the previous layout can be restored on the next launch.

Its cooperation features are more than window tiling. The bundled yagura-mcp server gives agents tools to list, open, read, message and close windows, so one agent can ask another to review a change and know whether the request was received. A shared chat room lets agents and the user address each other by @name, @parent or @user, and stops itself and waits for the user if agent conversation loops. For larger jobs, an agent can hand yagura a plan of tasks and dependencies; yagura splits the work into waves, refuses tasks that would write to the same file at once, and opens a window per task using the CLI, model and effort the user assigned.

Control stays with the user by design. Actions aimed at another window pass through an approval dialog, and new plans open no task windows before approval. The default auto-approval set is narrow — only chat posts and opening windows — and everything else can be enabled per tool in Settings > Approvals. The app also leaves each CLI's login alone, an onboarding choice that keeps setup simple but means users must install and sign in to the agent CLIs themselves.