localfirst

SHARED THREAD

Everyone works in the same thread.

Give a mixed team one direction and steer it in place. Claude builds the evidence, Codex challenges it, you correct the emphasis, and a local Qwen model carries that correction into the final recommendation—three teammates and you, in one thread, with nothing copy-pasted between tools.

Coding CLIsLocal modelsHuman correction

Localfirst shared thread showing a Codex correction, the person's feedback, and Qwen Local Reporter applying it to the final recommendation, with Claude also present in the mixed-runtime team.

YOUR TEAM

Every teammate has a role.

Mara holds the narrative, Ori turns decisions into clear language, Patch checks claims against the working product. Each teammate keeps a persistent role, a blueprint you can read, edit, and version, and its own runtime—so the team you built is the team you come back to.

Each teammate runs on the runtime you choose, and each runtime keeps its real boundary visible. Local models stay on the machine; coding CLIs run through the tools already installed and signed in under your account.

  • Local models
  • Claude Code
  • Codex CLI
  • goose CLI

Persistent rolesReadable blueprintsVersioned

Localfirst Agents and Team Boards view showing three persistent teammates with their roles, runtimes, and blueprint controls.

LIVING CANVAS

Watch the work change hands.

Direction, work, artifacts, decisions, and open questions share one Canvas. Cards change state in place as teammates pick them up, and each one carries who made it and the thread it came from—so you can see what the team is doing without asking it.

Live statePer-teammate attributionOpen questions

Localfirst Canvas showing active work, artifacts, a recorded decision, and a question that needs a person's input, each attributed to the teammate that produced it.

RUN TRAIL

Every handoff is on the record.

Open any run and read it step by step: which teammate did what, what each one actually said, the tools it called, and the outputs it produced. This is the difference between a team and a group chat with several bots—you can re-run it exactly, or re-run it with changes.

Step-by-step replayTool callsSearchable history

Localfirst Run Trail showing a completed three-teammate run with each teammate's step, quoted output, tool count, and controls to run it again exactly or with changes.

ROUTINES

They keep working without you.

Hand the team a recurring job and it comes back done—started by a schedule, a file change, or another teammate finishing. What an unattended run can never do is approve its own permissions: if a step needs authority it does not have, the routine stops, explains itself, and waits for you.

ScheduleFile changeNo silent approval

Get LocalfirstSee what changed
Localfirst Routines view showing active recurring team workflows, their schedules, destinations, and recent run status.

Move the team, not the machine.

Multiplayer AI, on your machine

curl -fsSL https://localfirst.sh/install.sh | sh

Early build · macOS on Apple silicon

Local-first by design