OYAKATA puts 5 coding agents in one browser view

The project grew out of a specific frustration rather than a product plan: with four terminal tabs open, there was no way to tell which session was idle and which was waiting on a permission prompt, and long answers scrolled past in a wall of Read and Bash logs. The developer tried existing options — Orca, the official Agent View, Remote Control, and tmux-based and worktree-management tools — but each missed on at least one front, whether because it only showed sessions started inside it, because it still displayed plain terminal text, or because it assumed tmux and therefore did not fit a Windows machine.

OYAKATA's approach is to read the record files each agent already writes to disk, rather than wrapping or replacing the agents themselves. That is why sessions begun in a terminal or from a VS Code extension show up alongside ones started in the browser, and why worktrees were later added so parallel sessions in the same repository do not overwrite each other's files. The tool also ships a skill that tells the agent its output will be rendered in the browser, nudging it toward tables and diagrams instead of ASCII art — a small loop that the developer says made them actually read Claude's answers to the end.