See handoffs as they happen.
Each card shows who is active and the latest conversation. Select a workspace to continue with its Main agent.
Local-first, open source, sandboxed. One team per workspace — each with its own provider, files, tools, and permissions, working in parallel, on a schedule, and reporting to you from one Fleet cockpit.
Fleet brings live work, recent results, and requests for your attention into one board.
Fleet keeps every team’s latest activity together. Open a workspace when you want the whole conversation, its tasks, and its files.
Each card shows who is active and the latest conversation. Select a workspace to continue with its Main agent.
When an agent needs a decision, its question appears on the workspace’s card with answer choices, so you can reply from Fleet.
Chat with the Main agent, follow the tasks it hands to helpers, and read their reports. Files the team writes open in the artifacts drawer beside the chat.
Move between workspaces, answer an agent, review artifacts and a chart, follow a helper’s task, and approve a git push.
Each agent has its own instructions, model, skills, tools, and local access. Define it once, then add it to the workspaces that need it.
Instructions set what the agent does and how. Each agent picks its own provider and model, so a Claude Code main agent can hand work to a reviewer on an OpenAI-compatible API.
Grant the paths an agent may read or write, choose which hosts it can reach, and set its shell to Off, Ask first, or Don’t ask. On Linux and macOS, its commands run in an OS sandbox.
Settings → Agents keeps your reusable agents. Add one to any workspace; when you edit it, every workspace using it picks up the change from its next turn. Each workspace still decides whether the agent is enabled there, the context it works under, and the paths it may touch.
CLAI brings the practical pieces together: models, MCP tools, skills, permissions, schedules, transcripts, and files.
Local (Ollama, LM Studio, vLLM, LiteLLM) and hosted providers — OpenAI-compatible and Anthropic-compatible.
Run Claude Code, Codex CLI, and OpenCode from a workspace and keep their outputs in the Fleet cockpit.
Connect MCP servers with static credentials or OAuth, then choose which workspaces and agents can use them.
Run a workspace on a schedule — every N minutes, or cron with presets like Hourly and Daily 9am. Preview cron runs before saving.
Reuse instructions from the default clairun/clai-skills repository, local folders, or Git-backed skill sources and attach them where they help.
Keep generated files, task transcripts, and durable memories next to the workspace that produced them.
Create a workspace for a project or recurring task, give agents the right context, and come back to a clear record of what happened.
Add API providers, local CLI agents, and MCP servers from Settings.
Attach the right model, tools, skills, files, and helper agents to a workspace.
Start work immediately, schedule it on a cadence, and review transcripts, memories, and artifacts when it finishes.
Short answers about what CLAI is, where it runs, and how it handles models, data, and local commands.
CLAI is a free, open-source desktop app for controlling teams of AI agents. You create workspaces; each has a main agent you chat with and optional helper agents it can delegate to. Every agent has its own model provider, files, tools, and permissions, and the Fleet view shows what every workspace is doing.
Yes. CLAI Desktop is free and MIT licensed, and it is developed in the open at github.com/clairun/clai.
macOS 11 or later (Apple Silicon and Intel), Windows 10 or later (64-bit), and Linux x86_64 as .deb, .rpm, Flatpak, or the AUR package clai-desktop-bin. Android and iOS companions are planned but not available yet.
Any OpenAI-compatible or Anthropic-compatible API, including OpenAI, Anthropic, together.ai, Groq, and local endpoints such as Ollama, LM Studio, vLLM, and llama.cpp. CLAI can also drive locally installed CLI agents: Claude Code, OpenAI Codex, and OpenCode. Each agent picks its own provider.
CLAI is a local-first desktop app. Workspaces, memories, and artifacts are stored in workspace directories on your machine. Prompts are sent to the model provider you configure for each agent; with a local model they stay on your machine, unless an agent uses the built-in web search/fetch tools or remote MCP servers, which send their requests to those services.
A workspace is an ongoing conversation with a main agent that owns its provider, tools, skills, and permissions, plus any helper agents on its team. The Fleet view supervises all workspaces: scheduled ones float to the top, and failed or blocked tasks and input prompts are flagged.
Yes. Toggle Schedule in a workspace's settings to run its main agent at a fixed interval (1 to 1440 minutes) or on a cron expression, with presets such as Hourly and Daily 9am. Cron schedules are evaluated in the workspace's timezone and preview the next run times. Outputs, transcripts, and artifacts stay attached to the workspace.
Each agent has filesystem grants and one of three shell modes: Off (no generic local file access), Ask first (commands on the agent's ask-first list, such as git push, wait for your approval; everything else runs), or Don't ask (every command runs without asking). Commands run through bubblewrap on Linux and Seatbelt on macOS. Windows has no sandbox backend: CLAI checks the working directory and the allow/block lists, but the command itself is not contained.
Download the installer for your platform from the download page. On Linux you can also use the apt repository (Debian/Ubuntu), the dnf repository (Fedora/RHEL), zypper (openSUSE), or the AUR (Arch). macOS builds are not yet notarized, so if macOS says the app is damaged, run xattr -cr /Applications/clai.app once in Terminal.
Reach the CLAI team directly for product feedback, MCP integrations, packaging questions, or collaboration.
Prefer the open channel? Ask or share feedback in GitHub Discussions.