Skip to content

For small teams and project leads

Write down what your AI assistants keep forgetting

Notes, decisions and proposals stay attached to the project, so the next assistant starts from what your team already learned and agreed. No code needed to use it.

In the product todayPartly covered

Proofs last checked on 7 Oct 2026

  • “We decided that last month, but nobody remembers why.”

    Choices live in chat threads, meetings and heads. They get reopened and decided twice, and the reason is gone.

  • “My assistants make the same mistakes again.”

    You corrected the tone, the supplier or the format in one conversation. The next conversation starts blank and you correct it again.

  • “Everybody knows it, but nobody wrote it down.”

    What the team knows stays in a few heads. A new colleague, or a new assistant, starts from nothing.

  • “Someone suggested a change in a thread and it never got a yes or a no.”

    Without a place for proposals, ideas float around until someone assumes they were accepted.

  • “Where are we on this project? I have to ask three people.”

    Plans live in several documents and the answer depends on whom you ask.

  • Available

    Decisions with their reason

    A decision keeps the choice, the reason, the options you ruled out and a status. Months later, you can see why.

  • Available

    What you replaced stops coming back

    Mark a decision Superseded or a note obsolete, and it is no longer put in front of the assistant. Only what is still current is.

  • Available

    Plans and objectives with their progress

    Break an objective into plans and tasks, and see how many tasks are done. The answer to “where are we” is on one page.

  • Planned

    Roles and rights for a team

    Who may see or change what, and who wrote which note, is not built yet.

A pricing choice that survives the month

A team of four relaunches a client website. The same pricing discussion, a month apart, without and with Project Orchestrator.

Without Project Orchestrator

  1. YouIn a meeting, the team picks monthly billing and drops the annual plan, because of a client’s cash flow.

  2. YouThe reason stays in a chat thread and in two people’s notebooks.

  3. AssistantA month later a new conversation drafts the offer page with the annual plan the team had dropped.

  4. YouYou catch it by luck, explain the whole story again, and wonder what else was reopened.

With Project Orchestrator

  1. YouAfter the meeting you ask your assistant to record the decision with its reason and the option you dropped.

  2. Project OrchestratorThe decision is saved on the project, with its reason and the dropped alternative.

  3. AssistantA month later, a new conversation about the offer page. PO puts the matching decision in front of the assistant before it answers.

  4. YouThe client’s cash flow improves. You mark the old decision Superseded and record the new one.

  5. Project OrchestratorOnly the new decision is put in front of assistants from now on.

No promise that an assistant never gets it wrong: it starts from what your team wrote down, instead of from nothing.

Your words, and ours

You say “what we agreed”, “where we are”. Project Orchestrator uses these words.

  • “what we agreed on”

    Decision

    A choice that was made, with its rationale and alternatives.

  • “what the team knows and nobody wrote down”

    Note

    What was learned: guidelines, gotchas, patterns, tips.

  • “a proposal to validate”

    Proposal

    A change put up for review before it is decided.

  • “a project, a file”

    Project

    A body of work with its own plans, notes and decisions.

  • “the roadmap, the checklist”

    Plan

    How an objective gets done: ordered tasks and steps.

  • “the milestone, the deadline”

    Objective

    What the work is heading toward.

  • “our AI assistants”

    Assistants

    A conversation with an AI that works on your project; Today shows which ones are running.

  • “we changed our mind”

    Superseded

    The status of a decision or a note that a newer one replaced; assistants are no longer shown it.

  • “yes, that is still how we work”

    Confirm

    The button that tells PO a note is still true, so it does not go stale.

Words this page leaves out : knowledge graph, RFC, MCP, Neo4j, agent

  • A note has a project, a type and an importance

    Available

    The note form offers seven types (Guideline, Gotcha, Pattern, Context, Tip, Observation, Assertion), four importance levels beyond the default, and a project or “Global (cross-project)”.

  • A decision keeps its reason and its alternatives

    Available

    Each decision stores a description, a rationale, the alternatives, the chosen option, who decided and when, and one of four statuses: proposed, accepted, deprecated or superseded.

    src/neo4j/models.rschecked 7 Oct 2026
  • The assistant is shown matching notes and decisions

    Available

    In the chat built into PO, before each message, the project’s notes and decisions that match its words are added: by default up to 5 notes and 3 decisions, in about 3000 characters, with a 200 ms limit per search. It is best effort: a search that is too slow is skipped.

  • Replaced knowledge is left out

    Available

    Archived, obsolete, stale or replaced notes are dropped, and only proposed or accepted decisions are added. A newer answer wins.

  • A proposal has nine possible states

    Available

    Draft, proposed, under review, accepted, planning, in progress and implemented, plus rejected and superseded. PO sets up this procedure for the project the first time a proposal is created.

    src/api/rfc_handlers.rschecked 7 Oct 2026
  • Sign-in exists, roles do not

    Planned

    The sign-in token carries an id, an e-mail and a name, and nothing about a role or a project. Per-project rights are planned.

What it does not do yet

Nothing here is hidden: these are the things you might assume and that are not true yet.

  • No roles and no per-project rights: everyone who signs in to the same server sees everything.

    Planned
  • A note or a decision does not record which person wrote it. Notes are saved as coming from “api”, decisions from “agent”.

  • No team view and no editing together in real time.

  • Sharing between installations, with consent and expiry, is in progress and has not been tried between two real installations.

    In progress
  • The assistant is shown a few matching notes and decisions, chosen by the words of your message and only in the chat built into PO. There is no guarantee that a given note appears.

  • The decisions list has no “new decision” button: decisions come from a task page or from your assistant. Proposals are drafted by assistants, not typed in a form.

  • The Today screen is written in French in the product today; the rest of the app is in English.

  1. Step 1 : Install it on one machine

    You need Docker Desktop and an AI engine. The setup walks you through four steps, and the first launch takes a few minutes while it downloads what it needs.

    Download
  2. Step 2 : Create a project named after the work

    A name is enough: no code folder needed. Group projects that go together in a workspace, your team’s space.

  3. Step 3 : Write the three things your assistants keep forgetting

    Open Notes, choose New note, pick the project and a type such as Guideline or Gotcha. Use the words your team uses.

  4. Step 4 : Record the choice your team keeps reopening

    Ask your assistant in the chat: “record this decision on the project, with the reason and the options we ruled out”.

  5. Step 5 : Keep it current

    Press Confirm on notes that are still true, mark replaced decisions Superseded, and read what is planned for teams.

    See what is planned
Can my whole team use it together?

Not as a shared team space yet. The server can have several accounts, but they all see the same things, nothing records which of you wrote what, and nobody has walked a team through that setup. Roles and per-project rights are planned. Today it fits one person who runs it for the team, or a small group that fully trusts each other.

Can two installations exchange their notes?

Not in a way you can rely on yet. The approval step per note, the expiry and the revocation exist, but an exchange between two real installations has not been tried. We do not call it sharing until it has.

Will the assistant really stop suggesting what we dropped?

It stops being shown it once you mark the decision Superseded or Deprecated, or the note obsolete. What it is shown depends on the words of your message: write notes in the words your team uses, and know that a handful of matches is added, not everything. This happens in the chat built into PO.

Do I have to write all this myself?

No. Ask your assistant: “record this decision, with the reason and what we ruled out”. You can also add a note yourself with New note. Proposals are drafted by assistants; you review and move them forward. On the app, a decision is added from a task page.

Do I need to know how to code?

Not to use it. A project only needs a name: a code folder is optional. The installation needs Docker Desktop and an AI assistant engine; the setup offers to install Claude Code, and walks you through four steps.

Is it free?

The app is free and open source (MIT). The AI engine you connect has its own cost, which Project Orchestrator does not include.

Where do our notes live?

On the machine that runs Project Orchestrator, in its own database and on its disk. The chat goes through the AI engine you chose, so what you type reaches that provider.

Download

Download Project Orchestrator

One-click install

1 click: download, open, connect your AI.

There is no Project Orchestrator account to create.

Free · MIT license · Bring your own AISee what it costs

Version 0.0.19 · 13 Nov 2026

The app installs on a computer. Pick the one you use.

Prefer a terminal?

Homebrew · Mac and Linux. Installs orchestrator, orch and mcp_server.

brew install this-rs/tap/project-orchestrator

What you need

  • Docker Desktop

    Runs the database and the search engine the app relies on. The app starts them for you. Get Docker Desktop

  • Claude Code

    The default engine for chat. The AI itself is not included: with Claude Code, you use your own Claude account, and the app can install it for you. Other engines (Codex, an OpenAI-compatible model, an ACP agent) are available from Settings — newer, in alpha. Get Claude Code

  • At first launch

    A setup wizard in four short parts checks Docker, installs Claude Code if it is missing and downloads the search model.

Install Docker and Claude Code from this page

Docker Desktop

Runs the two services that hold the project memory (Neo4j and Meilisearch).

Open the downloaded .dmg, drag Docker into Applications, then open Docker once and wait for the whale icon to stop moving.

Or in a terminal

brew install --cask docker

Check that it works

Each line should print a version number. If you see « command not found », open a new terminal window and try again.

docker --versiondocker compose version

Docker must be running (open it once) before you start Project Orchestrator. Installation page of the publisher

Claude Code

The assistant Project Orchestrator works with. It uses your own Claude account.

Paste the command in a terminal. It installs everything it needs and asks for your password only if required.

Command

curl -fsSL https://claude.ai/install.sh | bash

Check that it works

Each line should print a version number. If you see « command not found », open a new terminal window and try again.

claude --version

Run claude once to sign in. Installation page of the publisher

Free · MIT license · Bring your own AI See what it costs

Try it: start a task in any window

  • My day7

    • Confirm the venue deposit
    • Send the save-the-date to guests
    • Pick the menu for the welcome dinner
    • Book the train tickets
    • Print the name badges
    • Brief the photographer
    • Prepare the closing speech

    macOS

    Version 0.0.19 · 87.1 MB

    .dmg

    Download .dmg
  • My day7

    • Confirm the venue deposit
    • Send the save-the-date to guests
    • Pick the menu for the welcome dinner
    • Book the train tickets
    • Print the name badges
    • Brief the photographer
    • Prepare the closing speech

    Windows

    Version 0.0.19 · 88.7 MB

    .exe.msi

    Download .exe
  • My day7

    • Confirm the venue deposit
    • Send the save-the-date to guests
    • Pick the menu for the welcome dinner
    • Book the train tickets
    • Print the name badges
    • Brief the photographer
    • Prepare the closing speech

    Linux

    Version 0.0.19 · 163 MB

    .AppImage.deb.rpm

    Download .AppImage

Three steps, and you are in

  1. 1

    Download

    Pick the file for your system above. There is no account to create.

  2. 2

    Open

    Open the file. A setup wizard checks Docker, installs Claude Code if it is missing and downloads the search model.

  3. 3

    Connect your AI

    Chat runs on Claude Code by default; other engines are available from Settings (alpha). If it asks you to sign in, type this once in a terminal.

    claude
Desktop platforms
macOS, Windows, Linux
License
MIT, with Enterprise Edition modules under BUSL-1.1
Other systemsEvery file for Mac, Windows and Linux, with its size.

macOS

  • macOS, Apple Silicon

    The app for Macs with an M1 chip or later.

    Project.Orchestrator_0.0.19_aarch64.dmg · 87.1 MB

    .dmg
  • macOS, Intel

    The app for Macs with an Intel chip.

    Project.Orchestrator_0.0.19_x64.dmg · 89.8 MB

    .dmg
  • macOS, Intel (macOS 10.15 to 13.3)

    For Intel Macs on macOS 10.15 to 13.3. Without local embeddings: use an HTTP provider such as Ollama.

    Project.Orchestrator_0.0.19_x64-legacy.dmg · 47.7 MB

    .dmg

Windows

  • Windows, installer

    The usual installer for 64-bit Windows. It opens a setup wizard.

    Project.Orchestrator_0.0.19_x64-setup.exe · 88.7 MB

    .exe
  • Windows, MSI

    The same app as an MSI package, for managed deployments on 64-bit Windows.

    Project.Orchestrator_0.0.19_x64_en-US.msi · 120 MB

    .msi

Linux

  • Linux, AppImage

    One file that runs on most Linux distributions (x86_64).

    Project.Orchestrator_0.0.19_amd64.AppImage · 163 MB

    .AppImage
  • Debian and Ubuntu, x86_64

    Package to install with dpkg or apt.

    Project.Orchestrator_0.0.19_amd64.deb · 98.1 MB

    .deb
  • Debian and Ubuntu, arm64

    Package to install with dpkg or apt, for ARM64 machines.

    Project.Orchestrator_0.0.19_arm64.deb · 94.4 MB

    .deb
  • Fedora and RHEL, x86_64

    Package to install with dnf or rpm.

    project-orchestrator-0.0.19-1.x86_64.rpm · 61.5 MB

    .rpm
  • Fedora and RHEL, arm64

    Package to install with dnf or rpm, for ARM64 machines.

    project-orchestrator-0.0.19-1.aarch64.rpm · 56.7 MB

    .rpm
For developersHomebrew, install script, Docker image and the orchestrator command line.

Command line

Homebrew

Mac and Linux. Installs orchestrator, orch and mcp_server.

brew install this-rs/tap/project-orchestrator

Install script

Mac and Linux. Latest release into ~/.local/bin. Add --no-frontend for the light variant.

curl -fsSL https://raw.githubusercontent.com/this-rs/project-orchestrator/main/install.sh | sh

PowerShell

Windows. Installs into %LOCALAPPDATA%\orchestrator\bin.

irm https://raw.githubusercontent.com/this-rs/project-orchestrator/main/install.ps1 | iex

Docker

Image for amd64 and arm64, with the web interface.

docker pull ghcr.io/this-rs/project-orchestrator:latest# API only, no dashboard: a version tag with the -api suffix# docker pull ghcr.io/this-rs/project-orchestrator:0.0.19-api

Server programs

orchestrator, orch and mcp_server, with the web interface included. Lighter versions without it are on the release page.

  • macOS, Apple Silicon

    Programs without the app window: orchestrator, orch, mcp_server

    orchestrator-full-0.0.19-macos-arm64.tar.gz · 81.9 MB

    .tar.gz
  • macOS, Intel

    Programs without the app window: orchestrator, orch, mcp_server

    orchestrator-full-0.0.19-macos-x86_64.tar.gz · 82.8 MB

    .tar.gz
  • Linux, x86_64

    Programs without the app window: orchestrator, orch, mcp_server

    orchestrator-full-0.0.19-linux-x86_64.tar.gz · 91.1 MB

    .tar.gz
  • Linux, arm64

    Programs without the app window: orchestrator, orch, mcp_server

    orchestrator-full-0.0.19-linux-arm64.tar.gz · 85.6 MB

    .tar.gz
  • Windows, x86_64

    Programs without the app window: orchestrator.exe, orch.exe, mcp_server.exe

    orchestrator-full-0.0.19-windows-x86_64.zip · 92.8 MB

    .zip

The desktop app starts Neo4j and Meilisearch in Docker for you. With the command line, one compose command does it: follow the quickstart.

More for developers
From download to first launchNo terminal needed. You install two helpers first, then the app does the rest and shows each step as it goes.

The screens you will see

  1. Step 1: The start screen

    What you should see. A list of checks. On the very first launch the Docker lines say “Setup pending”.

    What to do. Wait for the setup to open: the start screen only checks what is installed.

  2. Step 2: Setup 1 of 4: Infrastructure

    What you should see. A green line says “Docker Desktop is running” under two cards, “Docker (recommended)” selected.

    What to do. Keep “Docker (recommended)”. The app looks for Docker Desktop. When it says “Docker Desktop is running”, press Next. If it says Docker is missing or not running, use the button next to the message, then wait: the app checks again by itself. The services use the local ports 7474, 7687, 7700 and 4222, and the app itself uses 6600.

  3. Step 3: Setup 2 of 4: Authentication

    What you should see. Three choices (No authentication, Password, OIDC / OAuth), the first one selected.

    What to do. On a computer only you use, keep “No authentication” and press Next. On a shared or public network, choose “Password” and set an email and a password: without sign-in, the app’s server accepts connections from your whole network.

  4. Step 4: Setup 3 of 4: Chat AI

    What you should see. Claude Code CLI shows a green check once installed (until then: “Claude Code CLI is required” and an install button), and the search model is marked ready.

    What to do. If “Claude Code CLI is required” is shown, press “Install Claude Code CLI”. Then let the app download the search model when it offers to; the size is shown on screen. Next unlocks when both are ready. If you have not signed in to Claude yet, see “If it does not work” below.

  5. Step 5: Setup 4 of 4: Launch

    What you should see. A green “Configuration saved!” message and a “Restart Application” button.

    What to do. Press “Generate Config & Save”. When “Configuration saved!” appears, press “Restart Application”. A switch on this screen controls whether the app checks for updates at start-up.

  6. Step 6: Wait for the first start

    What you should see. A checklist (Docker Desktop, Neo4j, Meilisearch, NATS, Backend server) turning green one line at a time.

    What to do. On this second start the app downloads the three images it runs on, then starts them. Later starts reuse the images and are quicker. When every line is green, the main window opens. If a line says “Taking longer than expected”, wait. If a “Continue anyway” button appears, see “If it does not work”.

Your system

macOS

macOS 11 or later on Apple Silicon (M1 and later). On Intel: macOS 13.4 or later, or macOS 10.15 to 13.3 with the older-macOS file, which has no local embeddings.

Install and start Docker Desktop

Download Docker Desktop from Docker’s page, open the file, drag Docker to Applications, then open it and wait until it says it is running.

Get Docker Desktop

Docker Desktop is open and reports that it is running. It is Docker’s own screen, so it is not reproduced here.

Open the app

Open the .dmg, drag Project Orchestrator to Applications, then open it from there. If macOS says it cannot check the app, we could not verify how the build is signed: allow it in System Settings, Privacy & Security, with “Open Anyway”.

If it does not work

The three problems you are most likely to meet, with what the app shows.

Docker is not running

What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.

What to do.

  • Open Docker from your Applications folder (the app’s own Open button does the same). Wait until Docker says it is running.
  • Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, quit and reopen the app.
A port is already in use

What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.

What to do.

  • Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
  • Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.

Only if you are comfortable with a terminal, this shows which program uses the port:

lsof -i :7687
The chat cannot reach Claude

What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.

What to do.

  • On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
  • If the chat then asks for a login, open the Terminal app, type the command below, press Enter and sign in to Claude.

Type this and press Enter:

claude
Windows

Windows, 64-bit.

Install and start Docker Desktop

Download Docker Desktop from Docker’s page, run the installer, then start Docker Desktop from the Start menu and wait until it says it is running.

Get Docker Desktop

Docker Desktop is open and reports that it is running. It is Docker’s own screen, so it is not reproduced here.

Open the app

Run the installer and follow the wizard, then start Project Orchestrator from the Start menu. Windows may show “Windows protected your PC” because no signing certificate is set in the build configuration: choose “More info”, then “Run anyway” if you trust the download.

If it does not work

The three problems you are most likely to meet, with what the app shows.

Docker is not running

What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.

What to do.

  • Start Docker Desktop from the Start menu (the app’s own Open button does the same). Wait until Docker says it is running.
  • Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, close and reopen the app.
A port is already in use

What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.

What to do.

  • Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
  • Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.

Only if you are comfortable with a terminal, this shows which program uses the port:

netstat -ano | findstr :7687
The chat cannot reach Claude

What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.

What to do.

  • On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
  • If the chat then asks for a login, open PowerShell, type the command below, press Enter and sign in to Claude.

Type this and press Enter:

claude
Linux

AppImage for Intel/AMD; .deb and .rpm packages for Intel/AMD and ARM64.

Install and start Docker Desktop

Follow Docker’s page for your distribution, then start Docker and wait until it says it is running. The app also recognises Docker installed without the Desktop application.

Get Docker Desktop

Docker is running. It is Docker’s own screen, so it is not reproduced here.

Open the app

For the AppImage: in your file manager, open the file’s properties and allow it to run as a program, then double-click it. For a .deb or .rpm: open it with your software installer, then start Project Orchestrator from your applications menu.

If it does not work

The three problems you are most likely to meet, with what the app shows.

Docker is not running

What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.

What to do.

  • Start Docker Desktop, or your Docker service if you use Docker without the Desktop application. The app’s Open button only tries to start Docker Desktop.
  • Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, close and reopen the app.
A port is already in use

What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.

What to do.

  • Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
  • Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.

Only if you are comfortable with a terminal, this shows which program uses the port:

lsof -i :7687
The chat cannot reach Claude

What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.

What to do.

  • On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
  • If the chat then asks for a login, open a terminal, type the command below, press Enter and sign in to Claude.

Type this and press Enter:

claude