Your agent threads, as a colony

Every agent thread, a little astronaut.

Threadnauts turns the coding-agent threads on your machine into a 3D colony. Each one walks out of the ship, claims a plot for its repo, and builds something. When one needs you, it stops and holds a question mark over its head.

In development for macOS, Windows, and Linux. Free to use.

A Threadnauts colony on a grassy world: hex zones for each repo, buildings at different stages, bots at work, and the side panel listing every repo.
Meadow Free

How it works

Your threads, laid out as a place you can learn.

Threadnauts reads the session files your harnesses already keep. Every thread becomes someone in the colony, and the map stays put, so after a day you know where everything lives.

A hex zone is a repo
Bigger repos claim more tiles. A zone keeps its ground as it grows and shrinks, and you can pick it up and move it.
A bot and its building are a session
The more the thread has done, the more finished its building looks, on a scale shared across the whole map.
Scaffolding means work
A building wrapped in scaffolding has a thread running there right now, with its bot hammering away.
A bot with no building is a subagent
It's out on an errand for the session that sent it, and shows up only while the errand runs.
Walking out of the ship
A thread that just started. It heads for its repo's zone and gets to work.
Walking back in
A thread you archived. The bot boards the ship, and what it built stays standing.

At a glance

Every bot shows you what it's doing.

A bot is always in exactly one state, and each state has one color, on its eyes, its antenna, and the badge over its head. Only the states that want something from you get a badge, so the one question mark that matters never gets buried.

Click one

The thread is one click away.

Click a bot and a card opens beside it with its title, branch, model, and last activity. The camera follows it while you watch. Everything you can do is a key away, too.

A selected bot with its thread's card beside it, showing the thread's title, branch, model, and the Open, Viewed, and Archive buttons.

Open Enter

Hands the thread back to the harness it came from, and that app comes forward. Without a desktop app, a terminal opens with its CLI resuming the thread.

Next one waiting N

Flies the camera to the next bot holding up a question mark, so nothing waits on you for long.

New conversation C

Starts a fresh thread in that zone's folder. Its bot walks out of the ship to join the others.

Viewed V

Puts a waving hand down once you've seen the thread. It asks again the moment it does something new.

Archive A

Walks the bot back up the ramp into the ship. Nothing is written to your harness; the colony keeps its own list.

Hide

Takes a whole repo off the map. Repos that have been quiet for three days fold away on their own, and come back to the same ground when they wake.

Worlds

80 worlds to build on.

Set up camp on a meadow, a fjord, Mars, or Saturn's rings, with a day and night you can scrub, let run, or set to follow your own clock. 23 of them are free, and Threadnauts Pro opens the rest.

Harnesses

Every harness you run, in one colony.

Every harness that's installed shows up at once, and each bot carries the name of the one it belongs to. A thread opens back in the app it came from, or in a terminal if you'd rather.

Not yet

macOS, Windows, and Linux. Needs Node 22.13 or newer.

Get started

One command, and your colony is up.

Threadnauts runs on your own computer and shows itself in your browser. There's nothing to sign up for.

  1. Install Node.js

    Threadnauts needs Node.js 22.13 or newer, from nodejs.org.

  2. Run Threadnauts

    In a terminal, run:

    npx @threadcrumbs/threadnauts

    It opens in your browser. Run it again any time to bring back the copy that's already running.

  3. Meet your crew

    Every thread from your harnesses walks out of the ship. Click a bot to open its thread, and press ? to see every key.

Threadnauts isn't released yet. This command works from launch day.

Stays local

It watches. It never touches.

Your threads never leave your machine

It reads your harnesses' own files on your own computer. Nothing about your threads is uploaded, and there's no account to make.

Never writes to your agents

The only file it writes anywhere is colony.json, where your map lives. Archiving a thread is the colony's own bookkeeping.

Only answers you

It serves the colony on your own machine's address, and refuses requests from any other site or host.

Want the numbers too?

Threadnauts keeps to the colony. For tokens, context, spend, and the tool each agent is running right now, there's Threadgauge, from the same people.

Visit threadgauge.io

Contact

Questions, or a harness you'd like to see?

A person reads every message.