New Pilos Rooms is in open preview

Two ways to work with Claude Code

Pilos Agents runs the agent on your machine and turns your best conversations into scheduled workflows. Pilos Rooms puts your whole team inside a single live session — watching, steering and approving together.

Free. Open core, MIT licensed. Agents runs entirely on your machine.

Pilos AgentsDesktop app

A native app on top of Claude Code. Build a team of agents, give them a real terminal and 22 tool integrations, then turn any conversation that worked into a workflow that runs on a schedule.

macOS Windows Linux MIT core
Pilos RoomsWeb · open preview

One agent, many people. The runner stays on a developer's machine; everyone else joins a room in the browser to follow the work live, queue messages, approve the risky commands and take the wheel when it is their turn.

Browser Sign in with GitHub Approvals
Pilos Agents

Stop repeating yourself

Build a workflow once from any AI conversation. Run it on a schedule. Never prompt the same thing twice.

Visual workflow builder

A drag-and-drop canvas for AI pipelines. Connect agents, tools, conditions and loops — 13 node types, auto-layout, undo and redo. No code.

13 node types auto-layout

Scheduled automation

Run any workflow every 15 minutes, hourly, daily or weekly. Nightly code reviews and morning reports happen while you sleep.

every 15 min Jira triggers

Multi-agent team mode

Assign a PM, an Architect, a Developer or a Designer to each step. They disagree with each other, and the output is better for it.

31 templates custom agents

Local-first storage

Conversations and runs live in SQLite on your disk. No cloud sync, no telemetry, nothing leaving the machine unless you ask for it.

SQLite full history

22 tool integrations

GitHub, Supabase, Slack, Jira, Figma, Kubernetes, Terraform and 15 more MCP templates. Your agents read, write and act on real data.

22 included bring your own

Integrated terminal

A real shell in the window. Agents run commands, read the output and react — no tab-switching between your terminal and your AI.

real shell live output
Workflow engine

From chat to automation in minutes

  1. 01

    Have a conversation

    Chat with your agents about any task — a report, a code review, a research brief. Use it the way you already do.

  2. 02

    Convert it to a workflow

    Turn a conversation that worked into a reusable graph. Add parameters, conditions and connected tools, visually.

  3. 03

    Set a schedule

    Every 15 minutes, daily at 9am, or weekly on Monday. Pilos runs it and delivers the result where you asked.

  4. 04

    Review and refine

    Every run is in your history. Improve the workflow as you go, share it with the team or keep it to yourself.

Work Day Reporter

Your standup, written from your git history

Everyone uses AI to write the code. Turning that work into a standup, a report or a timesheet is still copy-paste. Pilos reads your commits — including what you have not committed yet — and writes it for you.

No API key needed 4 formats secrets stripped

Daily Standup, Detailed Work Report, Manager Summary or an invoice-ready Timesheet — all from the same git activity. Runs on Pilos Cloud with no setup, or entirely locally with your own key.

$ git log --oneline · git diff --stat
→ 23 files · +1,942 −388
 
What I did today
• Shipped the Cloud reporter end-to-end
• Added secret redaction and a send preview
 
Blockers — none
Tomorrow — wire the hosted quota
Pilos Rooms

Your team, inside the agent session

The agent runs on one machine. Everyone else opens a link. They see every message, every diff and every command as it happens — and when the agent wants to do something irreversible, it stops and asks the room.

payments · refund-flow waiting for approval

Claude — Migrated the refund handler to the new provider and updated the tests. Ready to push the branch.

src/payments/refund.ts+18−6
export async function refund(id: string) {
- return legacy.refund(id)
+ const res = await provider.refunds.create({ id })
+ if (!res.ok) throw new RefundError(res.code)
+ return res.data
}
Needs approval
$ git push origin refund-flow --force
git-push Pushing rewrites history on a shared branch.
Approve Reject Owners or reviewers can approve
Plan
  • Read the provider SDK
  • Rewrite the refund handler
  • Update the tests
  • Push the branch
  • Open the pull request
Terminal
$ pnpm test payments
✓ 34 passed
$ git push origin refund-flow
⌛ waiting for the room…

Approvals, not permissions dialogs

A push, an rm -rf, a deploy, a publish, a write outside the repo — the agent stops and the room decides. Who may approve is set per rule, and the decision is recorded with the name of whoever made it.

One driver at a time

Exactly one person holds the wheel. Everyone else can still type — their messages are queued and visible to the room until the driver releases them. Handing over writes a summary of where things stand.

Replay is the same screen

A room is an append-only log. Someone joining an hour late scrolls back through exactly what the first person saw — the same events, in the same order, not a summary of them.

Start one from the repo you are already in

The runner connects outbound only. Nothing opens a port on your machine, no one gets a shell, and your environment variables never leave it. The room sees the events the runner sends and nothing else.

Read the Rooms docs
# create a room at rooms.pilos.net, then
$ npx pilos-runner room \
--room <token> --cwd .
 
✓ connected · payments/refund-flow
  https://rooms.pilos.net/rooms/8f2c…
  3 people watching

Four roles

RoleCan do
OwnerEverything: invite and remove people, change roles, take the wheel at any time, approve anything the policy allows an owner to approve.
DriverHolds the control lock. Sends messages straight to the agent, releases other people's queued messages, pauses and resumes the run.
ReviewerApproves and rejects the calls the policy assigns to reviewers. Can ask for the wheel. Messages are queued until released.
ViewerSees everything, including every approval card and every decision. Sends nothing.

Driving is a position, not a replacement for a role: a reviewer who takes the wheel still approves what reviewers approve.

Open source

Built in the open

The Agents core is MIT licensed and fully auditable. No black boxes, no telemetry, no vendor lock-in. Run it, fork it, change it.

2.4kGitHub stars
180+Forks
40+Contributors
MITCore licence

Core

MIT
  • The Electron app and solo mode
  • Integrated terminal
  • Agent templates and MCP integrations
  • Conversation history in SQLite
  • Permission modes

Extensions

Included free
  • Multi-agent team mode
  • All 31 agent templates
  • All 22 MCP integrations
  • Jira integration and story sync
  • The workflow builder and Reporter

Source-available under BUSL-1.1. Both halves ship in every download, at no cost.

Free

All of it, for everyone

No plans, no licence key, no card. Every feature is unlocked. An account is optional — the app works the moment it finishes downloading.

FAQ

Questions, answered

What is the difference between Agents and Rooms?

Agents is a desktop app you install: it runs the agent locally and is built around one person automating their own work. Rooms is a web app: the agent still runs on one person's machine, but the session is shared with everyone you invite, with approvals and a control lock so several people can work with it without talking over each other. They are separate products and you can use either on its own.

Do I need Claude Code?

Yes, for both. Install it with npm install -g @anthropic-ai/claude-code and authenticate with your Anthropic account. No separate API key is needed — the CLI handles it. Claude Code is the only agent either product drives today.

Is it really free?

Agents is free in full — no licence key, no trial clock, no card, and no paid tier to upgrade to. Rooms is free while it is in open preview. If we ever introduce pricing we will say so clearly and give plenty of notice rather than switching a paywall on overnight.

What can the people in a room see?

Everything the runner sends: the agent's messages, its plan, the diffs, the commands it runs and their output, and every approval with the name of whoever decided it. They cannot see anything else on the machine. The runner connects outbound only, opens no port, gives nobody a shell, and never transmits environment variables or secrets.

Where is my data?

For Agents, on your disk: conversations and runs are stored in local SQLite, and nothing is synced unless you create an account and ask for it. Rooms is different by design: a room's event log is stored on our server so that someone joining late can replay it, and that log includes the diffs the agent produced and the output of the commands it ran. Credentials are stripped before anything is sent, but the code in a diff is not — see the privacy policy for exactly what is kept.

Can I self-host?

The Agents core is MIT licensed, so yes — fork it and build it yourself. Rooms is a hosted preview today and is not packaged for self-hosting yet.

Stop prompting. Start automating.

Agents is free to download and runs on your machine. Rooms is free while it is in preview.

macOS, Windows and Linux · requires Claude Code · View on GitHub