Run pi threads side by side.
Bridge is a local web UI for the pi coding agent. Each thread runs as its own pi --mode rpcprocess, with the same extensions, skills, models and logins as pi in your terminal.
Landing page for onbridge.dev
Goal: the site is live and renders the wordmark
Build a one-page site for Bridge and deploy it.
Read the README and the feature docs. The hero says what Bridge is in one sentence, then one short paragraph per feature.
Keep it to one line. No hype.
thread_spawn @bridge-sitewriter
What it does
- Threads
- Every thread is its own pi process. Keep many open, grouped by project folder, and switch between them while they work. A message sent mid-run either steers the agent or waits its turn.
- Comments and subthreads
- Select part of a reply and comment on it. Branch a subthread after any reply to try another path. The original stays as it was.
- Threads that start threads
- A thread can spawn child threads, prompt them, wait on them and read their results. A child that writes code gets its own git worktree and branch. The br command does the same from a shell.
- Loadout
- Skills, extensions, agents, prompts, context and MCP servers in one shared set, the same on every machine. Switch items on per project or per thread. Every change keeps a history you can restore.
- Automations
- Schedule a prompt once or on a repeat. Each run starts a new thread, or arrives as a reminder in a thread that already has the context.
- Runs
- Follow multi-step agent workflows: each phase, the files every step made, and the questions waiting on you.
- App panels
- Panels open beside the thread: Mail, a cloud browser you can watch and take over, a support inbox, a command center.
- Goals and context
- Give a thread a goal and the agent works toward it until it is done or blocked. A meter shows how much context is in use.
Where it runs
On your Mac. Bridge serves the UI on 127.0.0.1 and starts each thread from your own pi install.
In private use. More soon.