Obeya

Open source · runs on your machine

Direct coding agents like an engineering director.

Every task is a card on a canvas. Agents work in the background, each in its own clone or worktree. When an agent is done, it shows you a narrated demo. You approve it or say what to change, like a director in a launch review.

The video shows a real run on a small app, from a spoken idea to the approved change.

See every feature in action. Each change to Obeya is listed with the demo its agent recorded.

Canvas

A card stays where you put it.

Every task is a card, and you decide where it goes on the canvas. A project keeps its workstreams in one frame, and you put related cards next to each other. You know where things are the way you know where things are in a room. A card shows its state by its colour. It does not move to another column when its agent is done, as it would on a kanban board. Each product you build gets its own canvas, for one repository or several.

  • Agent working
  • Waiting for you
  • Approved
Cards on the canvas in their states
Voice

Talk instead of typing.

Hold the space bar and say what you want: a new task, an answer to an agent's question, feedback on a demo. Obeya sends it to the card you are looking at. You don't keep a terminal tab open for each agent.

An agent's question, answered by holding push-to-talk
Demos

Watch the demo instead of testing it yourself.

Every change comes back with a short report and something to look at: a narrated screen recording with chapters, or a page when the result is a layout or variants side by side. You don't have to click through the app to see whether it works. Approve the change or say what to change. If your feedback is about one moment of the video, pause it there, and the agent gets that frame along with your words.

Obeya is built with Obeya. See the latest demos from its own development.

A card unfolded with the demo video of a tip calculator, its chapters and the approve button
Order

Parallel where it can, in order where it must.

Start ten tasks or a whole project at once. Before a card starts, Obeya looks at what it will change and at what is already running. Independent work starts right away. A card that builds on another, or would collide with it, waits until that one has landed. Hover over a card to see what it is waiting for, or draw an arrow from one card to another to make the second wait for the first.

A queued workstream waiting for the one it builds on, linked by an arrow
Review

Other people's pull requests get a card and a demo too.

Say “Review PR #14”, and a pull request someone else opened gets a card. Its agent reads the diff before any of that code runs on your machine, reviews it, and records a demo of the app before and after the change. For each finding you choose what happens: it goes to the contributor, the agent fixes it, it becomes a follow-up task, or you ignore it. You can edit the text that goes onto the pull request, then click “Push and merge” or “Push and comment only”.

When it is the contributor's turn, the card waits. Once they comment or push, the agent reviews the pull request again.

A contributor's pull request on a card: three findings, one of them still to decide, the demo, and the text that goes onto the pull request
Phone

Watch and approve on your phone.

Away from your desk, your phone lists the cards that are waiting for you on all your canvases and the ones agents are working on. Watch a demo and approve it, answer a question, or hold the microphone button and describe a new task. A notification tells you when a card needs you.

Obeya keeps running on your computer, and your phone connects to it over your own private network, Tailscale or another VPN. Nothing goes through our servers. Turn on “Reachable from other devices” in the configuration and scan the QR code under “Connect a phone”.

Obeya on a phone: the cards that wait for you, and those at work The card Split the bill opened on a phone, with its demo video, chapters and the approve button

Fits your setup

From idea to main

For most tasks you do three things: say what you want, watch the demo, and approve. The agent does the work in between.

A card can take more steps than these three. If a task is not clear yet, start with an idea or with prototypes. If the result is not right, the agent goes another round.

  1. 1Say the task

    Export invoices as CSV
    “One row per invoice, VAT in its own column”
    Agent at work

    Hold the space bar and say what you want. It becomes a card, and an agent builds it in its own clone or worktree. You can do something else in the meantime.

  2. 2Watch the demo

    !
    Export invoices as CSV
    Narrated demo, three chapters, a short report
    Demo ready

    When the agent is done, it shows you a demo of the finished work. You watch it instead of testing the change yourself.

  3. 3Approve

    Export invoices as CSV
    Landed on main
    Approved

    Approve it with a click or a word. Obeya lands the branch on main, or opens a pull request and looks after it until it is merged.

Not clear yet, or not quite right? show ideas, prototypes, another round and what an agent proposes on the way.

If it isn't clear yet
Idea
Invoices for the accountant
Which export would they actually use?
Idea

Start with an idea and talk it through with an agent. It lays out variants, their trade-offs and what each would cost, and it keeps a brief of what you decided.

Prototype
A download button
CSV from the invoice list
Agent at work
Prototype
A monthly e-mail
Agent at work

When talking is not enough, throwaway prototypes show the variants side by side. You build on the one that works.

A clear task starts here
Export invoices as CSV
Writing the export
Agent at work

An agent builds the card in its own clone or worktree. You don't have to watch.

!
Export invoices as CSV
One row per invoice, VAT in its own column
Demo ready
Changes? Another round

It comes back with a demo and a short report, or with a question. Say what to change, and it goes another round.

Export invoices as CSV
One row per invoice, VAT in its own column
Approved

You approve. Obeya lands the branch on main, or opens a pull request and looks after it until it is merged. If the agent noticed something outside its task, it proposes a new card for it.

✦
✦ Proposal
Import invoices from CSV
Noticed while building the export
Proposed by an agent

The big room

Obeya is Japanese for “big room”, the room where a project's plans and status hang on the walls. Nobody has to ask how things stand, because everyone can see it.

One agent in one chat works well. With more than a few, you lose track of which chat is waiting for you, which one is stuck, and which one is changing what another built. Obeya puts every agent's work on one wall instead.

Obeya is built with Obeya.

This page was a card there too.

Get started

Obeya is an app for macOS, Windows and Linux and runs locally. The agents use the official Claude Code or Codex installation on your machine, with your own subscription.

Download

On its first start Obeya checks for Claude Code or Codex, git and gh, installs what it can and opens your first canvas. The Windows installer is not signed yet (applied for at the SignPath Foundation): when SmartScreen warns, choose “More info”, then “Run anyway”. Code signing policy

From source

# needs Bun, Claude Code or Codex (logged in), git and gh
git clone https://github.com/sadilek/obeya && cd obeya
# runs the same setup as the app, then opens your first canvas
bun install && bun start

Obeya prints a link to http://127.0.0.1:4417 that opens the canvas and signs your browser in. The app and the source share their data in ~/.obeya.