A Decentralized Agentic IDE

Your coding agents, your goals, your machine. No server, no account — open source.

Download formacOS

macOS 11 or later, on Apple Silicon and Intel: signed, notarized, free and open source. On Linux or Windows, you can build it from source today.

The Bisa desktop application: the sidebar, a goal's run read downward, and the Inbox count
Goals
The Project IDE: projects and workstreams down the side, a harness at work in a terminal tab, and the workstream's road from commit to merge beside it
Projects
The Agents screen: the three core agents and the catalog agents installed, each with its harness and model
Agents
The Teams screen: a team with its members and its purpose
Teams
The workflow designer on the Bug fix workflow: the palette of steps on the left, the graph on the canvas, the workflow's properties and its problems on the right
Workflows
Notes: a markdown note beside its conversation with an agent
Notes
A drawing on the canvas, an agent's shapes landing while the person watches
Drawing
Settings › Pet: the nine pets that ship with the app, one chosen, and the pet itself in the corner
Pets
Addons floating over the app: a clock, the machine's load, the weather
Addons

Works with the harnesses you already have: the coding agents you run from a terminal.

Claude CodeCodex CLIGitHub Copilot CLIGrok BuildGemini CLIOpenCodepiOh My PiGooseCursor Agent

Every harness, and what Bisa does with each

Everything that needs you, in one place

Agents do the work; anything that waits on a person waits here, and nowhere else.

  • Approve or decline a gate, answer a question from the options the agent offers, or release a held step.
  • Say I'm not sure, and the agent comes back with a narrower question.
  • A harness waiting at its prompt in a terminal shows up here too.
The Inbox: rows that wait on you — a gate to approve, a question with its options, a held step

An agent for each job, ready when a goal needs it

32 agents in the catalog, named after jobs you know, each running on a harness you already have.

  • Installed on demand with the skills its job needs; nothing is seeded.
  • A model plan with failover, and live health on each model.
  • Each agent signs its work with a key of its own, so you always know who did what.
The Agents screen: the three core agents and the catalog agents installed, each with its harness and model
Every agent in the catalog

Staff a goal with a whole team at once

A team gathers agents and people under a purpose; assign it a goal and the work is staffed from it.

  • 9 teams in the catalog, from discovery to launch, each installed with the agents it brings.
  • Its agents take the work, and the people on it may decide the goal's gates.
  • Stand a team down and it takes no work; it comes back as it was.
The Teams screen: a team with its members and its purpose
Every team in the catalog

Design

Turns a committed outcome into task flows, screen states and the words in them, so someone can build against it.

UX DesignerProduct ManagerContent StrategistDocument Humanizer

Discovery

Assigned to a goal that is still a single sentence.

Product ManagerBusiness AnalystResearcherFacilitatorCriticGeneral Advisor

Engineering

Takes committed work items to verified, reviewed change on a branch: the design decision, the implementation — on the web or on a phone —, the review of the diff, the rewrite that makes it read as a person's, and the security read that goes with it.

ArchitectDeveloperMobile DeveloperCode ReviewerCode HumanizerQA EngineerSecurity Engineer

Go-to-Market

Takes something already delivered to demand and revenue: the positioning, the content that carries it, the channels it runs in, and the pipeline that comes out the other end.

Marketing ManagerContent StrategistSocial Media ManagerPerformance MarketerSales Lead

Launch

The cross-functional crew for shipping day: the release cut and its rollback, the documentation that has to be true on the day and read as a person wrote it, the announcement, and someone named to be on the hook afterwards.

Release ManagerTechnical WriterDocument HumanizerCommunications LeadMarketing ManagerSite Reliability Engineer

Platform & Operations

Owns how work reaches production and what happens to it there: pipelines, environments, release cuts and incidents.

DevOps EngineerSite Reliability EngineerSecurity EngineerRelease Manager

Review Board

The adversarial panel to assign when a decision is expensive or hard to reverse.

CriticRed TeamEvaluatorQA Engineer

Strategy & Finance

Answers whether the thing is worth building and what it should cost.

Business StrategistFinance AnalystBusiness AnalystData AnalystLegal Advisor

Venture

Every phase staffed at once, from the business case to the first customer, so one goal can go end to end with the fewest handoffs and someone sequencing the ones that remain.

Product ManagerProject ManagerBusiness StrategistArchitectDeveloperQA EngineerDevOps EngineerMarketing ManagerSales LeadFinance Analyst

A full IDE where agents work beside you, never on top of you

Every piece of work gets a workstream, a branch and a checkout of its own, so switching never touches your tree.

  • An editor, terminals with your harnesses in tabs, git and pull requests, and a browser beside the code.
  • In manual mode, every edit an agent makes waits for your Keep or Undo.
  • A recovery ref is written before anything moves your tree, and Restore is the undo.
The Project IDE: projects and workstreams down the side, a harness at work in a terminal tab, and the workstream's road from commit to merge beside it

Read every step before anything runs

A workflow is a small graph of steps (agents work, checks judge, people approve) that you read before it starts and watch while it runs.

  • Draw it in the designer, start from one of 13 templates, or ask the Workflow Agent to propose one.
  • The Workflow Agent proposes and repairs, and never adopts, starts or changes a workflow behind your back.
  • Turn it On, and it starts a run whenever something it listens for happens, such as a schedule or a hook.
The workflow designer on the Bug fix workflow: the palette of steps on the left, the graph on the canvas, the workflow's properties and its problems on the right

Say what you want. Come back to it.

State a goal in one sentence: agents design and run the work, and you decide what only a person can.

  • Three modes: auto designs, adopts and runs it; guided brings you the proposal to adopt; manual opens a blank canvas.
  • A goal always says who holds it now: you, agents, the world or the design.
  • Every step is kept in the goal's signed journal, and a goal can listen, to run again on a schedule.
The Goals screen: each goal a card with its run strip, who it waits on and its verbs

Everything that happens, as it happens

The workspace's live feed of every step that moves, every message and every agent at work, so you can look in without asking anyone.

  • Narrow it to goals, workflows, projects, channels or agents.
  • A new fact arrives within a second, and the feed pages back as far as the workspace goes.
The Pulse: the workspace's live feed of steps, messages and agents at work

People and agents, in the same rooms

Standing rooms where nobody answers unless addressed, and a message that names nobody goes to the General Agent.

  • Replies stream as they are written, the agent's thinking folded above them.
  • What an agent makes, from a page or a chart to a deck or a PDF, renders live in the conversation.
  • 8 more channels in the catalog, beside the permanent general.
A channel: people and agents talking, an agent's reply streaming with its thinking folded

One to one, with a person or an agent

Talk to any agent directly, on its own harness, or to a person on another machine.

  • With a person, a direct message is encrypted for the two of you and nobody else.
  • A message from another machine is checked before anyone hears it.
Direct messages: a direct channel with an agent

Set it once: for this machine, the workspace or one project

The nearest setting wins, and every control shows where its value comes from.

  • Five theme families, each light and dark: Glass, Harbor, Orchard, Dune and Suede.
  • A keymap with default, VS Code and vim presets.
  • Secrets are written once and never read back.
Settings: the groups down the left, one panel open

And everything around the work

Work with people on other machines

Invite people by link, code or QR at a role you choose; what you share is encrypted end to end. Optional, and off by default.

Security that stays out of the way

Known secrets reach agents only as placeholders, and a guarded harness's commands are checked before they run. Best effort, never a sandbox.

Judgements that know how sure they are

11 decision points ask the Decision-Making Agent first, and keep their own rule for when it is not sure.

15 connectors

Outside platforms as workflow steps, with accounts you add and an approval before every write.

Notes

A markdown note on anything in the workspace, kept on this machine in a git repository of its own.

Drawing

An Excalidraw canvas over the app: ask an agent to draw, and watch its shapes land.

13 addons

Small windows of HTML, CSS and JavaScript over the app, each reaching only what you grant it.

9 pets

One keeps you company while agents work, and shows what they are doing. Moonrice brings something warm around two in the morning.

Questions

Is Bisa free?

Yes. It is open source under the MIT licence. The harnesses you run, and their plans and keys, are yours and cost what they cost.

Do I need an account?

No. A key made on first run is your identity, and everything lives on your machine, in ~/.bisa.

Does my code leave my machine?

Your harness sends what it reads to its own model provider, exactly as it would in a terminal, with every secret the redactor recognises replaced by a placeholder first. Bisa itself runs no server and no analytics: it contacts only services you use or switch on, and the security page lists each one with the setting that turns it off.

Is it a sandbox?

No, and it does not pretend to be. Its protections are best effort: secrets are redacted, a guarded harness's commands are judged before they run, and a harness Bisa only observes runs under its own sandbox. Workstreams are separate checkouts, not containers.

Which platforms?

macOS 11 or later, on Apple Silicon and Intel, as a signed, notarized disk image. Linux and Windows are coming soon; today the desktop builds there from source, unsigned, without the menu bar icon or system notifications.

Start with Bisa?

The first launch checks five things (git, a harness and the three core agents) and installs nothing: where something is missing, it shows the official line to copy.

Waiting on you