One Agora per project
Every project gets its own Agora: talk the design through with your own coding agent on the project's architecture diagram, then pick up the very same session in the terminal.
uv tool install git+https://github.com/arvakme/agoraThen, inside any project: cd my-service && agora
Film · 40 s
An agent draws the architecture station by station, its little figure walking from node to node. Zoom into a node and you are inside its sub-diagram.
How it works
You talk to your agent in the panel or in the terminal, and it keeps writing its own native session log. This project’s agora server follows that log and pushes every turn to the canvas in your browser.
In the panel or in the terminal. It keeps writing its own native session log, exactly as it would without Agora.
Every 0.4 s, this project’s agora server picks up the turns from both sides — the panel’s and the terminal’s.
Changes reach the page over HTTP + SSE. When the agent edits the diagram with agora canvas apply, the page checks schema, references and freshness, writes the result to .agora/, and every batch can be undone.
127.0.0.1, one port per project. Only when you share does a read-only guest entrance open through Cloudflare Tunnel.Each one gets the figure, the progress pointer, station-by-station drawing, panel messages and the same session in the terminal. Two differences come from the CLIs themselves: in -p mode Grok, Cursor and Devin take no input once a turn has started, and Pi and Devin have no native sub-agents.
What you get
Screenshots and recordings show Agora’s interface in Chinese.
01 · Per project
Run agora in a project and it sets up .agora/ right there, with its own local server. Canvases are plain .excalidraw files and comments are JSON with sorted keys, so they commit, clone and branch with your code — and the diffs stay readable.
Session records, runtime state and share records stay out of git by default. Deleted canvases and sessions sit in a trash for 30 days.
02 · Station by station
When an agent changes the diagram, its little figure walks to each spot and the new elements fade in as it arrives — the diagram doesn’t pop into existence all at once, and you can follow what it is building.
03 · Sub-diagrams
Any node can hold a sub-diagram: overview › backend › order service. ⌘/Ctrl + scroll into a node and you land inside it; zoom out to climb back. Breadcrumbs and ⌘↑ work too.
04 · Progress pointers
Attach code paths (globs) to nodes — by hand, or let the agent map them from the directory layout. When the agent edits a file, its figure walks to the node that file belongs to: gliding along an arrow when the two nodes are connected, hopping across when they aren’t. Files that belong to no node are listed under the “off the diagram” chip, and edits made in the terminal move it too.
Replay a turn and the diagram shows the avatar’s route, numbered stops and +N files changed on each node.
Several sessions get one pointer each, and Agora flags a possible conflict when two agents touch the same file.
05 · Trajectory & replay
Switch a session between Conversation and Trajectory. Each turn shows model, effort, input / output / cache tokens, time and cost on a timeline; every tool call expands to its full input, output, the files it touched and when it ran.
And the diagram itself can be replayed: from the first stroke to now, the figures walking to where they drew, with play, pause, speed and a scrubber.
Pick the agent, model and effort when a session starts; they stay fixed. Hand a canvas comment to the agent and its reply is posted back into the thread. The agora skill is installed for that agent automatically.
“Open in terminal” resumes the very same native session (claude --resume, codex resume, pi --session-id) in a project-scoped tmux, in Ghostty, Kitty or Terminal.app. What happens in the terminal shows up in the panel, and panel messages queue until the terminal is free.
Get started
No need to keep the repository around. The install builds the web UI, so it needs Node and npm.
uv tool install git+https://github.com/arvakme/agoracd ~/code/my-serviceagora# set up .agora/, start this project's server, open the browseragora status# address, port and pid if it's runningagora down# stop the server and this project's tmuxagora share create --for 1d# a read-only link for a daypi, claude, codex, grok, cursor-agent or devincf and your own Cloudflare domainagora canvas apply exits with code 3.tmux attach command instead.agora-canvas; the command is agora.