Quickstart

Get Bridge running locally and create your first thread in a few minutes. This guide covers setup, first launch, and the fastest path to sending work to pi.

Overview

Bridge is a local web UI for the pi coding agent. You run it on your machine, open a browser, and manage threads without leaving your projects behind.

This quickstart shows you how to install Bridge, launch it locally, create your first thread, and send a message to a running thread.

Bridge is a starter kit template. Adapt the commands, paths, and defaults to match your own installation and environment.

Before you begin

You need a working pi installation, a recent Node.js runtime, and access to your project folder. If you already run pi in your terminal, you are close.

Pi installed

Confirm that pi is available in your shell before you start.

A project folder

Use a real codebase so each thread has a clear place to work.

Node.js runtime

Install the app and launch the local server from your machine.

Browser access

Open Bridge in your browser after the local server starts.

Installation

Install Bridge from your project directory, then start the local UI. The exact package name may vary in your setup, so treat this as the standard local workflow.

Install dependencies

Run the install step from the repository root.

npm install

Start Bridge

Launch the local app server.

npm run dev

Open the UI

Visit the local address printed in your terminal, then keep that tab open while you work.

npm install
npm run dev

Launching Bridge locally

After the server starts, open the local URL in your browser. The home view should load your projects and show the available thread controls.

Open the printed local address in Safari, Chrome, or your preferred browser.

open http://localhost:3000

Create your first thread

A thread is one pi process managed by Bridge. Start with a single thread in a familiar project so you can verify that Bridge connects cleanly.

Choose a project

Select the repository you want pi to work in. Start with a small, active codebase so you can see changes quickly.

Create a thread

Create a new thread from the project view. Bridge should assign it to the selected folder and show it in the thread list.

Set the task

Give the thread a clear instruction, such as a doc update, a test fix, or a small refactor.

Send a message to a running thread

Once the thread is active, you can send a follow-up message while it is still running. Bridge either steers the current work or queues your message until the agent is ready.

Keep messages short and specific. You get the best results when you ask for one outcome at a time.

{
  "thread": "docs-refresh",
  "message": "Update the README with the new setup steps and keep the tone concise."
}

bridge thread message docs-refresh "Add a short troubleshooting note for local startup errors."

Basic project organization

Bridge works best when you group threads by project folder. That makes it easier to find work, review progress, and hand tasks between threads.

Practice	Why it helps
One project per folder	Threads stay focused on a single codebase.
Short task names	You can scan active work quickly.
Separate exploratory threads	You can test ideas without disturbing the main path.
Reuse the same folder grouping	You build a predictable workspace over time.

To do

Install Bridge

Set up the local app and verify that it starts.

Open the project

Pick the repository where your first thread will run.

In progress

Create first thread

Start a thread and assign a small task.

Done

Send a follow-up message

Confirm that Bridge can steer a running thread.

Common next steps

After your first thread works, try a second project, split a larger task into child threads, or keep one pinned thread as your main point of contact.

If the page loads and your thread responds, you are ready to use Bridge as your local control center for pi.

Was this page helpful?