Works with your tools
Bring your subscriptions, skills and configuration
Run it anywhere
Use Clisbot locally, from another machine, or with a team
Desktop app
The one click experience, download the app and it just works, no server required
Built for automation
Use MCP, the CLI, or the TypeScript SDK to automate Clisbot
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.
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
UI
Screens, workspace panels, sidebar items, slash commands, and themes
Agent lifecycle
Change configuration, environment, and MCP servers. Answer permissions. Follow up when a turn ends
Providers
Add a coding agent as a provider, used the same way as the built-in ones
Clisbot is Apache 2.0.
Fork the repoFAQ
+Is this free?
+Does my code leave my machine?
+What agents does it support?
+How does Clisbot run providers?
+Do I need the desktop app?
+How does voice work?
+Can I connect from outside my network?
+Do I need git or GitHub?
+Can I get banned for using Clisbot?
+How do worktrees work?
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
Every coding agent, used the same way. Switch providers any time.
Composable
Run agents on your 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.
Sponsor Clisbot
Sponsorship options for Clisbot are being set up. Check back here when they are ready. Sponsorship details