Many agents.
One workspace. Your call.

Meet Siwar, the local workspace that runs your Claude Code and Codex agents
in parallel — each task in its own git worktree, every result in one merge queue you control.

See it in action

siwar12

Projects

Aacme-web⋯

Aacme-mobile⋯

Alinkbox⋯

Add Searchable Notes to LinksMerge

Land #3 into main · let-people-attach-a-short-note-to-a--0u80Merge

Review #3 · let-people-attach-a-short-note-to-a--0u80

Write and test a count-tags script

Add GET /uptime answering with the server's uptime

Land add-get-uptime-answering-with-the

Review add-get-uptime-answering-with-the

Add GET /version answering with the versionAnswer

Land add-get-version-answering-with-the

Review add-get-version-answering-with-the

Find dead code across the codebase

Land find-dead-code-across-the-codebase

Review find-dead-code-across-the-codebase

How many links are in links.json in total?

New worktrees start without node_modules

Land new-worktrees-start-without-node-modules

Review new-worktrees-start-without-node-modules

People want to star their favourite links

Land people-want-to-star-their-favourite

Review people-want-to-star-their-favourite

AMAlex Morgan

Add Searchable Notes to Links⋯

let-people-attach-a-short-note-to-a--0u80Claude Code · Opus 5.53h ago

Tests pass: notes are optional, capped at 500 characters, returned with saved links, and matched by q alongside titles and URLs.

2 stepsBash

Implemented and submitted.

Added optional note field, limited to 500 characters.
?q= searches titles, URLs, and notes.
npm test: 12 passing.
Commit: 19d682a
Submission #3 ready for review.

26k in · 0 out · context 26k

#3Ready to mergeintomaintargetMerge

Review approved — Alex Morgan · 3h ago — approved after reading the review

Add optional 500-character link notes, return them with links, and include them in q search; no feature flags. Tests: npm test

LPlet-people-attach-a-short-note-to-a--0u80submitted 3h ago·19d682a1·1 commit

ReviewReview #3 → main, 1 commitlet-people-attach-a-short-note-to-a--0u80-review3h ago

Approved — approved after reading the reviewAlex Morgan · 3h ago

let-people-attach-a-short-note-to-a--0u80 is told with your next message there — as context, not a task.

LandLand #3 into main, 1 commitlet-people-attach-a-short-note-to-a--0u80-land3h ago

Message the agent · / commands · @ files · $ env · ! shell

LowOpus 5.5

linkboxlet-people-attach-a-short-note-to-a--0u80← maindiverged ↑1 ↓5AMLPLR

ChangesNeeds you3

Branchsince main6 files · what it brings, since 0cd17ce+34−90/6 seen

SeenUndo filesrc/links.js-3+6

1const MAX_TAGS = 10;

2const MAX_NOTE_LENGTH = 500;

4export function validateLink(input) {

5 const errors = [];

6 if (!input || typeof input !== 'object') return { ok: false, errors: ['body must be an object'] };

6 const { url, title, tags } = input;

7 const { url, title, tags, note } = input;

8 if (typeof url !== 'string' || !isHttpUrl(url)) errors.push('url must be an http(s) URL');

9 if (title !== undefined && typeof title !== 'string') errors.push('title must be a string');

10 if (note !== undefined && typeof note !== 'string') errors.push('note must be a string');

11 else if (note !== undefined && note.length > MAX_NOTE_LENGTH) errors.push(`note must be at most ${MAX_NOTE_LENGTH} characters`);

12 if (tags !== undefined) {

13 if (!Array.isArray(tags) || tags.some((t) => typeof t !== 'string' || !t.trim())) errors.push('tags must be strings');

14 else if (tags.length > MAX_TAGS) errors.push(`at most ${MAX_TAGS} tags`);

Undo this change

10 unmodified lines

25 return links.filter((l) => l.tags.includes(tag));

26}

25/** Links whose title or url has the text. */

28/** Links whose title, url, or note has the text. */

29export function search(links, text) {

30 const q = text.toLowerCase();

28 return links.filter((l) => (l.title ?? '').toLowerCase().includes(q) || l.url.toLowerCase().includes(q));

31 return links.filter((l) => (l.note ?? '').toLowerCase().includes(q) || (l.title ?? '').toLowerCase().includes(q) || l.url.toLowerCase().includes(q));

32}

Undo this change

More unchanged context may be available

SeenUndo filesrc/server.js-1+1

1// The HTTP API.

2// GET /links paginated links (?tag=x, ?q=text, ?limit=50)

3// POST /links save one: { url, title?, tags? }

3// POST /links save one: { url, title?, tags?, note? }

4// GET /links/:id one link

5// DELETE /links/:id remove it

6import http from 'node:http';

Undo this change

More unchanged context may be available

#3 · ready to mergeintomaintargetMerge

A little less coordination. A lot more building.THE SIWAR DASHBOARD

YOUR CODE. YOUR TOOLS. A LITTLE MORE IN SYNC.

Claude CodeGitHubgitVS CodeTerminal

THE MERGE QUEUE

Agents submit.
You decide what lands.

Finished work waits as ready. Nothing runs on its own, and nothing is ever pushed for you.

01
Submit
The agent commits everything and hands it in. Its part ends here.
siwar submit --branch feat
02
Ready
It waits in Ready to merge, across every project you register.
siwar status
03
Review
Read what it brings: the message, the files, the diff, the checks.
siwar show 14
04
Your call
Merge locally, send it back with a reason, or close it.
siwar merge 14

ChangesNeeds you7Terminal

Waiting for your answer2

Land #12 into main · rate-limit-logins-4kq2, 2 commitsWas not allowed to use Bash · acme-claudeAnswer

Land #15 into main · resize-avatars-x9fa, 1 commitWas not allowed to use Bash · acme-claudeAnswer

Ready to merge5

Add Dark Mode to Settings#9 is ready to merge · acme-codexMerge

Fix Checkout Total Rounding#11 is ready to merge · acme-codexMerge

Paginate the Orders Table#14 is ready to merge · acme-claudeMerge

Land #16 into main · cache-search-p3ze, 2 commits#17 needs approval before it can merge · acme-claudeMerge

Send Weekly Digest Emails#18 is ready to merge · acme-codexMerge

❯ siwar merge 14 --into release

#14 feat/github-auth → release (no-ff)

✓ merged locally · 3 files · +184 −12

Nothing was pushed. Publishing is up to you.

Merged Into the local branch you pick. The target from .siwar.yml is the default.

One idea or a whole backlog.
Make room for the work.

Start with the idea.

Pick a repository and describe the work. Your agent gets the project context and a worktree of its own, ready to get going.

A focused place to start

Give every agent room.

Run independent tasks side by side. Each agent builds in its own branch, so one experiment never gets in another’s way.

Built for parallel work

Projects

acme-web

Add GitHub authentication

Write the OAuth callback tests

Build the billing settingsAnswer

Cover the checkout flowMerge

Fix the flaky login test

Stay in the conversation.

Follow the work, answer a question, or change direction. Messages, tool calls, and decisions stay together in one thread.

Keep the context close

Can you handle the edge cases, too?

edge-casesClaude Code · Opus 5.5just now

On it. I’ll cover empty states and retries in the same worktree.

Updatesrc/board/EmptyState.tsx

Added 18 lines, removed 2 lines

Bashnpm test -- retry

Running… (8s)

edge-cases is working — a message now waits for it

HighOpus 5.5

platformedge-cases← main

Ship on your terms.

Finished work lands in your review queue. Inspect the changes and merge into the local branch you choose. Publishing stays in your hands.

You decide what ships

LIVE SESSIONS

Your agent asks.
You answer, right there.

Every conversation runs in a session host that keeps the agent, Claude Code or Codex, open. Permissions, questions and plans arrive as cards, and your answer goes straight back to the running turn.

Messages queue. Send while it works; edit or cancel until it is taken.
Rewind and edit. Put the files back, or try a message again as a new agent.
Stop, switch, steer. Change the model and permission mode live.
Spend and context. Set a budget; a runaway turn stops too.

CHANNELS

Away from your desk.
Still in the conversation.

Talk to your siwar threads from your phone or your team chat, in Slack or Telegram. Start a thread, follow its work live in one updating message, and get its answer when the turn is done.

Slack in one click. Add to Slack in Settings › Channels; the bot token stays on your Mac. DM the bot, or mention @siwar in a channel.
Telegram with your own bot. Make one with @BotFather, paste its token, and pair your chat with a code.
Answer with a button. Permissions, choices and plans come with buttons. Send photos, files and voice messages; pictures in the answer arrive as pictures.
Told when it matters. /notify on and you hear when an agent waits for you or work is ready to merge.

Only people you pair can talk to siwar. Messages are kept on disk until handled, so nothing is lost if siwar restarts.

our-uptime-monitor-needs-a-health-ch-1hosClaude Code · Opus 5.55h ago

1 stepBash

Clean tree, tests pass 63/63. Submitting.

4 stepsBash1 failed

Bashsiwar submit --branch our-uptime-monitor-needs-a-health-ch-1hos -m "GET /health"

Submitted #42 (2 commits)

Bashsiwar merge 42 --into main

Merged #42 into main: eef0d71

Bashgit push origin main

Error: siwar guard: This repo takes changes to main through siwar, not git push. Commit your work and run `siwar submit --branch <your-branch> -m "<what and why>"`; the user merges it from the dashboard.

Bashgit rev-parse --short origin/main main

1873ae1
eef0d71

#42 is merged into main in this repository, but only locally. It is not on origin yet.

Checks: npm test passed 63/63 on the branch's newest commit, 5d54ea4.
Submitted: as #42 (2 commits: GET /health returning { ok: true, links, version }, plus the README API table update).
Merged: siwar merge 42 --into main made merge commit eef0d71. It's in the local main checkout.
Push blocked: git push origin main was stopped before it ran by the siwar guard hook. Its message was "This repo takes changes to main through siwar, not git push." That contradicts this project's push_on_land: true land rule. I did not try to get around the hook.
Remote: origin's main is still at 1873ae1; local main is at eef0d71.

To publish it, run git push origin main yourself from the main checkout, or allow it in the siwar guard for Land subthreads and have me push again.

THE GUARD

Built-in boundaries.
Not just good intentions.

The siwar plugin loads into every session. If it does not load, the agent does not run.

Never pushes

Merges stay local. Publishing is yours.

Never edits code

Conflicts go back to the author with the reason.

Never merges itself

Merging and pushing the target are blocked for agents.

Never leaks a secret

A submission that carries one is refused.

AUTOMATIONS

Agents that start
by themselves.

Give an agent instructions and a project, then choose what starts it. Every run is a conversation you can open, and its work lands in the same queue.

On a schedule. Daily reviews, weekly maintenance, whenever your workflow needs it.
On GitHub events. A failed check run, a labeled issue, a review comment, a merged pull request.
From a webhook. Let your error tracker hand a production error straight to an agent.

Automations

Start agents by themselves: on a schedule, on GitHub events, or from a webhook.

Create automation

All5Active4Paused1

Search automationsTriggerAny

NameStarted byLast 30 daysLast triggered

fix-ciclaude-code · acme-webCheck run failure · acme/acme-web68h ago⋯

fix-issuesrunningcodex · acme-webIssue labeled · acme/acme-web114m ago⋯

answer-reviewclaude-code · acme-webPR review comment · acme/acme-web95h ago⋯

fix-on-requestclaude-code · acme-apiIssue comment · acme/acme-api42d ago⋯

triage-issuespausedcodex · acme-webIssue opened · acme/acme-web423d ago⋯

fix-issue

fix-issue needs you

acme-web · wf-fix-issue-20261013-0914 · started 14m ago by automation · fix-issues

Open threadStop

step 4 of 5 · approve

issue412

Land it? Checkout total now skips removed cart items (#412)

A note for the next steps (with Reject: what to change)ApproveReject

Steps

implementAgentdone · try 2 · 7 min
Fix issue #{{inputs.issue}} (gh issue view {{inputs.issue}}).
testCommanddone · try 2 · exit 0 · 52 s
npm test
reviewReviewdone · 4 min
siwar review — you give the verdict · Check the empty-cart case too.
approveApprovalwaits for you
Land it? {{steps.implement.output.summary}}
landLandwaiting its turn
siwar Land — as the project's land skill says

Log · 16

WORKFLOWS

Steps that run
in the order you wrote.

A workflow is a YAML file in your repo. Siwar keeps the order, not the agent: every step runs in the run's own worktree, and it stops where you asked to look.

Agents and commands. Each agent step is a fresh session. A command passes when it exits 0; a failure can send the work back for another try.
Your OK where it matters. An approval waits for you. Approve with a note, or reject with what to change.
Review, then land. You give the review's verdict; a land step hands the branch in the way your project lands work.
Started by you or an automation. Run it from the dashboard, from siwar workflows run, or let a trigger start it.

ENVIRONMENTS

Secrets stay out
of the conversation.

A server address or a password goes into Settings, not into a message. Values are encrypted, the key lives in your Keychain, and siwar blanks them in everything it keeps and shows.

Guards against accidents, not a determined agent. What is in its environment, it can read.

Environments

The agents get these as environment variables. Shared ones go to every conversation; an environment's (prod, staging…) only to a conversation that chooses it by the message box, over a shared one of the same name.

Secrets

PROD_SSH_PASSWORD

All projects · deploy@ on the prod server

Last updated 2d ago

STRIPE_API_TOKEN

acme-web · Live key, for the billing checks

Last updated 5d ago

NPM_TOKENprepare only

All projects · The private registry

Last updated 3w ago

Variables

PROD_SSH_HOST

All projects · The prod server

203.0.113.24

Last updated 2d ago

PROD_SSH_USER

All projects

Last updated 2d ago

CONFIG & CLI

One file in your repo.
One command for every step.

Read from the target branch, so a submission can never change the rules it is judged by.

.siwar.ymltarget: main     # default branch to merge into
merge: no-ff      # or squash
agent:
  model: sonnet
  effort: high
  allow: [Read, Grep, "Bash(npm test)"]
  budget: 5
  mcp:
    playwright:
      command: npx
      args: ["@playwright/mcp@latest"]
  agents:
    reviewer:
      description: Reviews a diff
      tools: [Read, Grep]

siwar task "<what to do>"Start an agent in a new worktree

siwar submit --branch b -m "…"Hand finished work in

siwar statusWhat is ready to merge

siwar show 14What a submission brings

siwar merge 14 --into releaseMerge locally, never push

siwar return 14 --reason "…"Send it back to its author

siwar uiThe terminal dashboard

siwar serveThe browser dashboard

Inside
Siwar

LATEST RELEASESiwar 0.3.24Apple silicon · 144 MB · Oct 30, 2026Download for macOS

01Threads, with or without a branchModel

Ask a question with no project, read a repo from its main checkout, or give the work its own branch and worktree. Start a branch later and the same conversation moves there.

02Terminal, browser or desktopApps

siwar ui in the terminal, siwar serve in the browser, or the desktop app with both in one window. All three read the same queue.

03A Claude Code pluginPlugin

siwar:submit hands work in, /siwar:status shows the queue, and a guard hook blocks merging and pushing the target.

04Agents in your terminal, tooSessions

A session open in your own terminal is reached by relay, never by a second writer. Its turns show live and read-only in the dashboard.

05One event log, SQLite or PostgresStorage

Every change is appended and never edited. SQLite by default on your machine, or a shared PostgreSQL server for a team.

06Queue projects and watch projectsProjects

QUESTIONS

Frequently
asked.

How Siwar runs coding agents in parallel, and what stays in your hands.

What is Siwar?

Siwar is a local workspace that orchestrates AI coding agents. You describe a task, an agent such as Claude Code or Codex works on it in its own git worktree, and the finished branch lands in a merge queue where you review it and decide what merges.

How does Siwar run several agents in parallel without conflicts?

Every task gets its own git worktree and branch, created from the target branch you choose. Agents never share a working directory, so one experiment cannot overwrite another. You follow each conversation from one dashboard and merge the results one by one.

Does Siwar push, merge or edit code on its own?

No. Agents hand their work in with siwar submit; the submission waits as ready until you merge it locally, send it back with a reason, or close it. A guard blocks pushes and merges into the target from inside a task, and Siwar never edits code itself.

Which coding agents does Siwar work with?

Claude Code and Codex, signed in with your own Claude or Codex account. Claude Code comes with Siwar, built into the desktop app and installed by npm install; for Codex, install the Codex CLI. Siwar also ships as a Claude Code plugin: siwar:submit hands work in, /siwar:status shows the queue and a guard hook protects the target branch. Sessions you start in your own terminal show up live and read-only in the dashboard.

Does my code or conversation leave my machine?

Siwar itself runs locally next to your repositories. Its event log is a SQLite file on your machine by default, or a PostgreSQL server you host when a team shares one queue. The agents still talk to their own model provider, exactly as they do without Siwar.

Can agents start by themselves?

Yes. Automations start an agent on a schedule, on a GitHub event such as a failed check run or a labeled issue, or from a webhook. Every run is a normal conversation you can open, and its work lands in the same merge queue.

What do I need to install Siwar?

On a Mac with Apple silicon, download the Siwar 0.3.24 desktop app from this page; it has the terminal and browser views in one window and Claude Code built in. You need git and a Claude or Codex account; for Codex, also install the Codex CLI and Node.js. To run it from source on macOS or Linux, you need Node.js 22.18 or newer, git, and a Claude or Codex account: install Siwar from your team's source checkout (Claude Code comes with npm install; for Codex, install the Codex CLI), link the CLI, then run siwar serve in a project to open the dashboard in your browser, or siwar ui for the terminal.

Built for your code.
Designed for
your control.

Local by design

Your workspace runs on your machine.

Isolated by default

Each task gets its own Git worktree.

Human at the helm

You approve merges. You handle pushes.

Less juggling.
More shipping.

Bring your agents together. Build what’s next.

Explore the demo

Many agents.One workspace. Your call.

Agents submit.You decide what lands.

Submit

Ready

Review

Your call

One idea or a whole backlog.Make room for the work.

Start with the idea.

Give every agent room.

Stay in the conversation.

Ship on your terms.

Your agent asks.You answer, right there.

Away from your desk.Still in the conversation.

Built-in boundaries.Not just good intentions.

Never pushes

Never edits code

Never merges itself

Never leaks a secret

Agents that startby themselves.

Steps that runin the order you wrote.

Secrets stay outof the conversation.

One file in your repo.One command for every step.

Inside Siwar

Frequentlyasked.

What is Siwar?

How does Siwar run several agents in parallel without conflicts?

Does Siwar push, merge or edit code on its own?

Which coding agents does Siwar work with?

Does my code or conversation leave my machine?

Can agents start by themselves?

What do I need to install Siwar?

Built for your code.Designed foryour control.

Local by design

Isolated by default

Human at the helm

Less juggling.More shipping.

Many agents.
One workspace. Your call.

Agents submit.
You decide what lands.

One idea or a whole backlog.
Make room for the work.

Your agent asks.
You answer, right there.

Away from your desk.
Still in the conversation.

Built-in boundaries.
Not just good intentions.

Agents that start
by themselves.

Steps that run
in the order you wrote.

Secrets stay out
of the conversation.

One file in your repo.
One command for every step.

Inside
Siwar

Frequently
asked.

Built for your code.
Designed for
your control.

Less juggling.
More shipping.