Your AI agents,
connected to your work.

Build, research, and work with specialist Bots on your machines.
Desktop, mobile, and your team’s chat channels.
Open source. Your agents run where you choose.

Download for Mac
Supports
+33 more

When you want to step away from your desk, you can.

The native mobile app has full feature parity with desktop.

Works with your tools

Bring your subscriptions, skills and configuration

Claude Code
Codex
OpenCode
Pi
OMP
Cursor
Muse Code
Antigravity
+33 more

Run it anywhere

Use Clisbot locally, from another machine, or with a team

Desktop app

The app includes the local daemon. Install and sign in to an agent provider to start working.

Mobile

Full client and native, not a WebView

Download

Remote machines

Run Clisbot on a home lab, or a cloud machine

Docs

Teams and triggers

Share access or start work from GitHub, Slack, and Discord

Clisbot Hub

From your workspace to your team's conversations

Connect channels through Hub, share Projects with Managed access, and work with specialist Bots in one Chat.

Hub connects 8+ channels

Eight integrations in the current catalog. You or your team operate the Hub; your agents keep running on your machines. Transports, threads, media, and approvals vary by channel. Check its guide before connecting.

  • Slack
  • Telegram
  • Discord
  • Google Chat
  • Feishu/Lark
  • Zalo Official Bot
  • Zalo Personal
  • WhatsApp

Continue work where your team talks

Use a Hub Route to start an agent or continue a Bot from a channel conversation. Ask for a change in Slack, or review a task in Telegram, with replies in that conversation.

Connect a channel

Share a Host or selected Projects

A Host connects to the daemon that runs your agents. Grant Members or Teams access to its Projects through Managed access. Choose who can chat, create Workspaces, or manage the Host, with provider and model limits for managed sessions.

Set up team access

Bring several Bots into one Chat

Give each Bot a role, instructions, and a home Workspace. Create a Group chat with Bots on the same Host: ask a research Bot to gather options and a writing Bot to draft from the shared conversation. Each keeps its own session and memory.

Create Bots and Group chats

Managed access limits Clisbot operations; it does not isolate an OS account or cap provider spending. Available providers depend on the Host's setup and sign-in. Owners and Host Administrators bypass provider/model limits, and shell or Terminal profile access can run outside them. A Clisbot Group chat is a conversation with Bots on one Host; external channel groups use Hub Routes.

Choose a Project or Workspace with slash commands

Built for automation

Use MCP, the CLI, or the TypeScript SDK to automate Clisbot

MCP docsCLI docsSDK docs

Take the open GitHub issues labeled ready and fan them out to separate worktree agents.

I found two ready issues. I will run each in its own worktree.

create_agent#412claude/opus-4.6worktree
create_agent#417codex/gpt-5.6-solworktree

Done, two agents are running. I will let you know when they finish.

Extend it with plugins

Add new panels and functionality that work in desktop, web and mobile

Plugins

Browse pluginsPlugin docs

UI

Screens, workspace panels, sidebar items, slash commands, and themes

Agent lifecycle

Change config and MCP servers, answer permissions, and follow up

Providers

Add a coding agent as a provider, used like the built-in ones

Clisbot is Apache 2.0.

Fork the repo

Philosophy

What Clisbot stands for, and what every feature is built on

Private

Code stays on your machine. Usage analytics never includes code or chats and can be turned off in Privacy settings. No forced login.

Independent

Clisbot doesn't answer to investors. Its users guide what gets built.

Polished

Install the app and start working. No need to know what a daemon is.

Unified

Work with supported agent providers and specialist Bots through one app.

Composable

Run agents on a laptop or a server, and connect from any device.

Extensible

If Clisbot doesn't fit how you work, change it with a plugin or fork.

FAQ

+Is this free?
Yes. Clisbot is free and open source. You need agent providers installed with your own credentials. Voice is local-first by default and can optionally use cloud speech providers if you configure them.
+Where do my agents and files run?
Agents and working files live on your chosen Host. Agents send requests to their own providers; channel replies and files you send through Hub also leave that Host. Review your provider and channel settings. For remote app access, you can use the optional end-to-end encrypted relay, connect directly over your local network, or use your own tunnel.
+What agents does it support?
Clisbot supports many providers. It has custom implementations for Claude, Codex, OpenCode, Pi, OMP, Antigravity, and Muse Code, and supports many more via ACP. See the full list here: all supported providers. See Muse Code setup and limitations.
+How does Clisbot run providers?
Clisbot runs the providers installed on your machine as you'd normally run them. Clisbot doesn't modify or change their behavior.
+Do I need the desktop app?
No. You can run the daemon headless and use any client to connect. The desktop app just bundles the daemon with a UI.
+How does voice work?
Voice runs locally on your device by default. You talk, the app transcribes and sends it to your agent as text. Optionally, you can configure OpenAI speech providers for higher-quality transcription and text-to-speech. See the voice docs.
+Can I connect from outside my network?
Yes. You can use the hosted relay (end-to-end encrypted, Clisbot can't read your traffic), set up your own tunnel (Tailscale, Cloudflare Tunnel, etc.), or expose the daemon port directly. See configuration.
+Do I need git or GitHub?
No. Clisbot works in any directory. Worktrees are optional and only relevant if you use git. You can run agents anywhere you'd normally work.
+Can I get banned for using Clisbot?
Clisbot is designed to use each provider's officially supported integration and does not attempt to bypass its terms of service. It doesn't extract tokens or call inference APIs directly.
+How do worktrees work?
When you launch an agent with the worktree option (from the app, desktop, or CLI), Clisbot creates a git worktree and runs the agent inside it. The agent works on an isolated branch without touching your main working directory. See the worktrees docs.