Open sourceBaileyIn development
Assistant In development Apache-2.0

Bailey

An open-source AI assistant that runs ready-made solutions on your own machine, with your own AI key.

Getting AI to do one real job reliably is still a project: someone writes the instructions, connects the tools, supplies the documents and the keys, and keeps it all working when something changes. Bailey is being built to run solutions instead: complete, versioned packages for one job, installed in one step, that ask only for the keys they need.

Status
In development
License
Requires
Python 3.11+
Package
bailey · PyPI

The assistant is not out yet.

Bailey's first release installs one command, bailey doctor, which checks that your computer has what the assistant will need. The assistant itself arrives in 0.1. Until then there is nothing to install and chat with, and this page will say when there is. To follow it, watch the repository or read its changelog.

Today

Check your machine

The first release's one command. It checks what the assistant will need, says how to fix what is missing, and reads your machine only: no network call, and no file written.

README ↗
bailey doctor Available

Run it with uvx and there is nothing to keep installed. It exits with an error when a required check fails.

uvx bailey doctor
The design

What it is being built to do

What its README commits it to. None of it ships before the app does.

Solutions, not projects

A solution is a complete, versioned package for one job, such as answering customer emails or writing a weekly report: its instructions, skills, tools and knowledge, installed in one step.

Your machine, your key

It runs locally and opens in your browser, with the AI provider you choose: Anthropic, OpenAI, or any OpenAI-compatible endpoint, local models included.

It asks before it acts

Every tool is either read or write, and a write tool asks before it runs.

Your documents stay yours

Files you add are indexed on your computer, and answers cite the passage they came from.

Open formats

Skills are Agent Skills, tools are MCP servers, apps speak Postern, and a solution is an Agent Plugins folder, so its parts also load in other clients.

No telemetry

It reports nothing about how you use it. What leaves your machine is your calls to the AI provider you chose, what your own tools talk to, and, once you sign in to the store, its calls to Sigrix.

What comes next

The next two releases

As its README names them.

Changelog ↗
0.1 · The app

Chat, assistants, skills loaded when needed, tools with approval, knowledge from your own documents with citations, apps, and installing a solution from a file.

0.2 · The store

Sign in, browse, install and update solutions, and publish your own.

Bailey and Sigrix

Solutions are sold here

Builders sell solutions on Sigrix, and every assistant listed here already downloads as one: an Agent Plugins plugin whose assistant.json is written in Bailey's format, the schema this site serves. You need not wait for the app to use one: an assistant's download installs in Claude Code today, and its README says how.