Version 0.7.0

An AI agent for the people

Acai is a personal assistant that happens to be a Mac app. It uses the model you choose, the tools you give it and the files on your own disk — and it answers to you, not to a platform.

macOS 14 or later · bring your own API key

Refactor the parser claude-opus-5

Which files still parse the old front matter?

Two of them. I read the history directory to check.

fs__read_dir  ~/.acai/history  → 41 files

OKFParser.swift and HistoryStore.swift. The rest go through the shared decoder already.

Ask anything…

One app, three jobs

A personal assistant
Ask it things, hand it a folder of notes, let it draft and summarise. It remembers each conversation as a file you can open yourself.
An agent that does the work
Give it tools and it stops just talking — your files, your APIs, the agents your team already runs. You choose what it may touch, chat by chat.
A test bench for builders
Building an MCP server or an A2A agent? Point Acai at it and watch every call and reply go past, against any model, before you ship it.

Everything you need

No account. No runtime. No lock-in.

You don’t sign up for Acai, you just open it. Nothing sits between you and the model you picked, nothing is sent anywhere you didn’t point it, and if you ever walk away you keep every conversation you had.

Whichever model you like.
Claude, GPT, Gemini and Bedrock come built in — and anything running on your own machine, which costs nothing at all.
Nobody in the middle.
Your key goes to your provider and nowhere else. No account, no telemetry, no analytics, and no server of ours to be down.
Change your mind mid-chat.
Start on something cheap, switch to something clever when it gets hard. The transcript remembers which model said what.
It can actually do things.
Hook up your files, your APIs and whole agents that already know a job. A switch per chat decides what today’s conversation may reach.
Yours to tinker with.
One small settings file you can read in a minute. Change something, press ⌘R, and it’s live — no restart, no preferences maze.
Your chats are just files.
Plain Markdown in a folder on your Mac. Search them, back them up, edit them, take them with you. Nothing is locked in a database.

Point it at a model and go

A provider is a few lines of TOML. Keep several and switch between them from the toolbar — a frontier model for hard work, something local for the rest.

anthropic
Messages API, SSE streaming, native tool use, prompt caching on by default.
openai
Also the shape every local gateway speaks.
gemini
Streaming, with tool schemas reduced to the subset Gemini accepts.
bedrock
Converse API with a bearer key.
~/.acai/config.toml
default_provider = "claude"
system_prompt = "You are Acai, a concise and helpful assistant."
max_tool_rounds = 8

[providers.claude]
kind = "anthropic"
model = "claude-opus-5"
api_key_env = "ANTHROPIC_API_KEY"
max_tokens = 8192

[providers.local]
kind = "openai"
model = "llama3.3"
base_url = "http://localhost:11434"

Give it hands, colleagues and know-how

Three folders under ~/.acai. Drop a file in, press ⌘R, and it is there — nothing to install, nothing to publish, nothing to ask permission for.

Frequently asked questions

Can’t find what you’re after? The README goes further, or open an issue.

Do I need a subscription?
No. Acai has no account and no server of its own. You bring an API key — or a local gateway, which costs nothing — and pay whoever serves the model, if anyone.
Where does my data go?
To the provider you configured, and nowhere else. No telemetry, no analytics, no crash reporting. Chats, logs and settings stay in ~/.acai.
What does it cost to run?
Whatever your provider charges for the tokens. Acai caps the replayed history at a token budget you set and places prompt-cache breakpoints where the provider supports them, so a long chat doesn’t quietly become an expensive one.
Can it use my own tools?
Yes — any MCP server, over stdio or HTTP, described by a JSON file in ~/.acai/tools. Remote A2A agents go in ~/.acai/agents. Nothing is offered to a model until you enable it for that chat.
What do I need to run it?
macOS 14 or later. The release build is signed and notarized, so it opens without a Gatekeeper detour. To build it yourself you need a Swift 6 toolchain and make app.
Why not Electron?
Because a chat window doesn’t need a browser inside it. Acai is one ~1.3 MB binary with zero third-party packages — even the TOML parser and the AWS event-stream decoder are in-tree.

Download Acai

Drag it to Applications, add a key, start a chat.