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
Which files still parse the old front matter?
Two of them. I read the history directory to check.
OKFParser.swift and HistoryStore.swift. The rest go through the shared decoder already.
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.
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.
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"
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.
~/.acai.~/.acai/tools. Remote A2A agents go in ~/.acai/agents. Nothing is offered to a model until you enable it for that chat.make app.