A topic is not an agent. One thread per topic, whoever does the work.

Every thread says whose turn it is: on you, working or done. Any models, any orchestration.

Terminal
git clone https://github.com/udiNur/Suda.git suda
cd suda
python3 suda/threads.py install
python3 suda/server.py

Quick startSee it move

  • Any models, any orchestration
  • Phone and desktop
  • Runs on your machine
Suda on a desktop: the thread list on the side and the open thread beside it
Suda on a phone: the list by whose turn it is

See it move

Running agents is easy. Keeping up is hard.

Scroll to follow a topic from the list to done.

1 / 5

Every thread says whose turn it is

One thread per topic, from the first request to the finished work.

  • On youAn agent asks a question.
  • WorkingAn agent picks up your reply.
  • DoneAn agent finishes the work.
Suda on a phone: the thread list in three groups, On you, In progress and Completed

2 / 5

Open a topic: its tasks, its question, its answer

Each request is a task with an owner and a status. The question stays attached, with its own buttons, and the agent answers with a table or a diff, not only text.

An open thread: the tasks bar, an open question with three answer buttons, a table of checks and a diff

3 / 5

Answer in one tap, four seconds to undo

Buttons with the agent's recommendation. The reply waits four seconds, and Undo (or Esc) takes it back.

One tap: a toast says Chosen: Ship behind a flag, with Undo, and the answer waits to be sent

4 / 5

Agents keep working. A live card updates in place

Progress notifies nobody. One card updates in place, not a new message for every step. Nothing is on you while it runs.

An agent at work: a live status card for a rollout with a progress bar, and a grouped question under it

5 / 5

Done: the answer, and the thread goes quiet

The numbers as a chart. A finished thread goes quiet and archives itself once nothing in it is open.

A completed thread: the answer as a bar chart of monthly costs, with Close now and Keep open

Interactive demo

Try it

Tap a topic. Answer. Watch it move.

Connected

Choose a topic from the list

A scripted demo with invented content: nothing is sent, stored or run. Keys: Tab and Enter, 1 to 3 to answer, Esc to undo.

Features

One thread per topic, from the first request to the finished work

The note is written for someone who will not open the thread ("Approve the staging deploy", never "There is an update").

On you

  • Release 2.4Approve the staging deploy
  • Ticket 1042Refund the second payment?

Working

  • Nightly exportRetrying 3 batches, nothing for you yet

Done

  • Cost reportFinished, summary inside

A thread is a topic, not an agent.

Several agents on one topic, one agent in several, and threads with no agent at all: a support ticket, a reminder, a decision you owe someone.

Tasks stay with the topic.

Each request is a task with an owner and a status. Yours are shown apart, and the CLI refuses to mark a thread done while tasks are open (unless forced).

Questions stay attached.

Your "yes" lands on the button of the question it answers. Up to five open questions per thread, each with its own buttons.

Quiet unless it is your turn.

Progress notifies nobody. On you sends a browser notification (where you enabled them), unless the thread is muted or quiet hours are on. Snooze a thread until a time you choose.

It ends.

A finished thread goes quiet and archives itself once nothing in it is open.

Agents continue from the record.

A reply reaches an agent with the topic's summary and earlier messages, and the tasks are one command away.

  1. agentStaging is green. Deploy 2.4?
  2. agentTicket 1042: the customer paid twice. Refund?
  3. agentThe nightly export failed again, 3 batches timed out.
  4. youyes
  5. agentYes to the deploy, or to the refund?

Why Suda

Yes to what?

I run 10 to 15 coding agents at once. In one chat their replies mix; with a window per agent you hunt for the one that waits for you.

Most tools answer how to run agents. Suda answers what they need from you.

Agents answer with more than text

A Mermaid flowchart drawn inside a thread
Diagrams. Mermaid flows, sequences and plans, with full screen and the source one tap away.
A diff viewer inside a thread, with a pull request chip under it
Diffs. Changed words and line numbers, unchanged lines folded, or side by side.
A bar chart inside a thread
Charts. The numbers as a chart or a table, with CSV and PNG export.
A small interactive page an agent made, shown inside a thread
Interactive pages. A working mock-up, in the thread or full screen, in a sandboxed frame with no network.
Sliders with live results inside a thread
What-if cards. Move a slider and see the results change.
A status card that updates in place
Live status. One card that updates in place, not a new message for every step.

Also: tables that scroll and export, code with an exact copy button, pictures, carousels, video, long logs in a collapsed card (up to 20 MB), SVG drawings, next-step buttons inside a message, and short chips for pull requests, commits and other threads. All screenshots come from a demo board with invented content.

You answer with more than text

Pressing an answer button, the undo toast, the answer sent
One tap. Numbered buttons with the agent's recommendation. The reply waits four seconds, and Esc (or the button) takes it back.
A run block and its confirm dialog
Approve a command with ▶︎. Read the exact command and confirm. The tower applies its rules, runs it on your machine and reports in the thread. No command runs in the browser.
A question with checkboxes in groups and recommended marks
Several decisions in one form. Checkboxes in groups, with recommendations, a free note, and picture tiles for options you have to see.
A reply that quotes the exact words it answers, under a long log shown as a collapsed card
Point to the exact words. Mark a passage and reply: the agent gets the marked words and the message they came from.
  • Speak. The agent gets the transcript and the recording (needs a Soniox key and a secure page).

  • Show. Pictures with captions. A log or a text file becomes a collapsed attachment.

  • Split. Give a side issue its own thread, with a quote and a link back.

  • Know you were heard. Under each message of yours: received, picked up, done.

How it works

Any models, any orchestration.

You reply in the topic. One AI, the tower, carries each reply to the agent working on that topic, and the agents post results and questions straight into the thread. The tower is a go-between, not a boss: you never have to know which agent has which topic.

Any agent.

Any agent that can run a shell command takes part: it writes into threads with the threads CLI.

Any models.

Whatever model is behind an agent, it takes part the same way.

Any orchestration.

Suda starts no agents and owns no terminals. It needs one command that tells your tower "a reply waits" (THREADS_NOTIFY_CMD). Without it nothing is lost: the tower can read threads pending whenever it likes.

Tested so far on one setup: our agents run in tuios. With tuios and Claude Code, an optional hook (live_hook.py) also shows which agents are working on a thread right now.

Phone and desktop

Phone first. One pane at a time. It is a web page you add to the home screen as an app.

Wider screens. The list beside the conversation, for example on the inner screen of a foldable.

Languages. The code and the demo are in English, left to right. A translation is a table in suda/locales/ (Hebrew, right to left, ships in suda/locales/he.json).

Suda on a phone: the list by whose turn it is, a thread with a table, its tasks, a diagram
The list beside the conversation on a wider phone screen
Suda on a desktop: a release thread, a run block, a diagram, a log, a support ticket
Desktop. The list on the side and the open thread beside it: here a release with its tasks bar and open question, a run block, a diagram, a long log, and a support ticket in its own space.

Move through many threads

The command palette searching for deploy
⌘K: every thread and every command. Search, jump to a thread or change a setting. Each thread shows how long ago it last changed.

Slash commands.

Type / in the reply box: /status, /explain and /review go to the agents; /done, /s (snooze), /urgent, /mute, /rename and /task act on the thread.

Many threads at once.

Choose several (Cmd or Ctrl click, Shift click for a range, a long press on the phone), then mark read, snooze, merge or close.

Spaces and more.

Spaces (for example a support space with its own threads), urgent threads first, merge, reactions, light and dark themes, and keyboard shortcuts (? shows them).

Security

Runs on your machine

Python standard library, no dependencies, no build step, one HTML page, a server on 127.0.0.1 only. MIT.

  • licenseMIT
  • python3.9+
  • dependenciesnone
  • binds127.0.0.1 only
  • any modelsany orchestration
  • made forphone + desktop
  • The server listens on 127.0.0.1 only, checks the Host header (DNS rebinding) and the Origin of every write (CSRF), and serves only its own board folder.
  • No command runs in the browser. A ▶︎ run block is checked against the exact text stored for it (a SHA-256 of the block), and only the tower runs it.
  • Agent-made pages run in a sandboxed frame with no network. Diagrams are drawn in a sandboxed frame and shown as images.
  • Private keys, push subscriptions, settings and backups live in a private folder that is never served.

Details, and how to report a problem, in SECURITY.md.

Built around the topic

How it compares

We use or have tried most of these, some of them every day, and they are good at what they do. From our own use and their own pages, November 2026.

ToolBuilt aroundWhat Suda adds
tuiosThe pane. A terminal window manager that knows what your agents are doing: sessions that stay alive, agent states, agents that message each other. It is where our agents run.The topic, on top of the pane.
herdrThe agent. A runtime for coding agents that shows which agent is working or blocked, across machines and from a phone.Which topic needs me, and what did we decide in it?
Claude Squad, Conductor, SculptorThe agent session and its code. Several coding agents in parallel, each in its own worktree or container, with review of their changes.A home for a topic that spans several agents, or has no code at all.
OpenHandsConversations with agents. A self-hosted control center for coding agents and automations.One thread per topic, across agents.
DevinIts own agent. A hosted autonomous engineer you can reach from a team chat.No agent of its own. Suda works with the ones you already run.
Linear with agentsThe issue. A tracker for a team's planned work, where agents answer in the issue's comments. The closest in spirit.One person's live conversation, including topics that will never be an issue.
Slack, or any team chat with botsThe channel. The feel we wanted, and Suda borrows it.Whose turn it is and what is still open, with no bot or token per agent, on your own machine.

Our setup

What we run every day

A starting point, if you want one. Suda works without any of them, and we are not affiliated with them.

tuios

Where our agents run: a terminal window manager that knows what each agent is doing. With it, live_hook.py shows which agents are working on a thread right now.

Claude Code

The coding agents themselves.

Tailscale

Suda on your phone from anywhere, over your own private network, while the server stays on 127.0.0.1 behind a gateway.

Quick start

Stop hunting windows. Answer the topic.

Terminal
git clone https://github.com/udiNur/Suda.git suda
cd suda
python3 suda/threads.py install   # creates the board
python3 suda/server.py            # serves it on 127.0.0.1

Then open http://127.0.0.1:8767/threads/suda.html. Needs Python 3.9 or newer (standard library only) and a modern browser. macOS and Linux.

Get Suda on GitHubRead the README

  • Look around firstpython3 docs/demo/demo.py prints the address of a throwaway demo board.
  • Connect your agentsGive them SKILL.md as a skill. They write with the threads CLI.
  • Hear about repliesSet THREADS_NOTIFY_CMD so your tower learns that a reply waits.
  • Open it on your phoneKeep the server on 127.0.0.1 and put a gateway in front of it.
  • Change itTests come first: the suites and the rules for a change are in CONTRIBUTING.md.