Clisbot CLI
An AI-agent workspace with parallel worktrees, cross-provider orchestration, and bots across chat channels.
- 130 ★ on the repository
- Last commit
Broad access
Why this level
- Plugins from the registry, Git or a local folder get access to the daemon's machine and every connected client.
- The daemon runs CLI agents with rights to your file system and dev environment without a per-action confirmation step.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/clisbotDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Plugins from the registry, Git or a local folder get access to the daemon's machine and every connected client.
- The daemon runs CLI agents with rights to your file system and dev environment without a per-action confirmation step.
This is third-party code. Review the repository files before installing.
What it does
Clisbot runs a local daemon that drives existing CLI agents (Claude Code, Codex, GitHub Copilot, OpenCode, Pi, Antigravity, Muse Code and 39 ACP presets like Grok), each in its own git worktree, in parallel. Desktop, web, mobile apps and the CLI all connect to the same daemon, so a session can start at a desk and get checked from a phone. On top of the agents, Clisbot adds its own bots: role, memory, tools and model are set per bot, and several bots can join one group chat to work together. Plugins extend the UI, agent lifecycle and provider list, and a TypeScript SDK (`@clisbot/client`) plus a CLI (`clisbot run`, `clisbot attach`, `clisbot send`) give programmatic access to the same daemon.
Who it is for. Teams and solo developers running several parallel agent tasks in separate worktrees who want to switch providers without being locked to one CLI.
Good fit when
- Several tasks run in parallel, and each needs its own git worktree without branch conflicts.
- A task started on a desk machine needs checking and replying to from a phone.
- One task needs a plan from one model and implementation from another, without switching between separate apps.
- Agents need to reach Slack, Telegram or Zalo as part of a real workflow, not just the terminal.
Not a fit when
- No CLI agent is installed and configured yet: Clisbot orchestrates existing CLIs rather than replacing them with its own model.
- Control over the machine or device running the daemon isn't guaranteed: plugins run on that same machine and in connected clients with its access.
- A minimal single-user tool with no group chat, plugins or cross-platform sync is all that's needed.
Example request
Start a Codex agent in a separate worktree on task X while I keep working with Claude Code on task Y in parallel, and show me both diffs once they're ready.Limitations
Clisbot orchestrates third-party CLIs — at least one (Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, Muse Code) needs to be installed and authorized with its own credentials separately. Plugins install from the shared registry, Git or a local folder and get access to the daemon's machine and connected clients, so the README explicitly recommends installing only trusted code. The relay transport for device pairing is end-to-end encrypted, but can be turned off in favor of direct TCP, Tailscale or another VPN. Sponsorship and contribution terms are not finalized yet; links will follow.
How to disable. Stop the daemon (quit the desktop app or kill the `clisbot` process) and uninstall it the way it was installed. For an npm server install, run `npm uninstall -g clisbot` and remove the `~/.clisbot` folder if a Docker volume was used.
FAQ
How do I install Clisbot on a server with no desktop app?
`npm install -g clisbot`, then just `clisbot` — the daemon starts and asks about the end-to-end encrypted relay for paired devices.
Do I need a separate Clisbot account?
No account for Clisbot itself, but at least one CLI agent with its own credentials is required: Claude Code, Codex, Copilot or another from the supported provider list.
How do I connect from my phone to a session started on my computer?
In the desktop app, open Settings, pick your host, and select Pair Device. The mobile apps are still in beta via TestFlight (iOS) or a Google Play tester group (Android).
What's the difference between the clisbot-handoff and clisbot-advisor skills?
`clisbot-handoff` fully hands off a task to another agent with context and decisions included. `clisbot-advisor` spins up an agent only as a second opinion, without delegating the work itself.
How do I install a Clisbot plugin?
`clisbot plugin add owner/slug` installs from the shared registry, or a Git repository or local folder path works too.
Discussion
No questions or reviews yet.
Related
CLI toolsThe MetaBot CLI connects local coding agents to messaging and a web console while retaining tasks and sessions
botmux connects Lark and Feishu to Claude Code, Codex, Gemini CLI and OpenCode: each message starts its own agent session with live cards
GitBot runs Claude Code, Codex or OpenCode locally as reusable bots with persistent threads and permissions you control.
One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
Self-hosted system for a team of AI agents: org chart, tasks, budgets and oversight of Claude Code, Codex and OpenClaw
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Clisbot (this card) | no | 130 | |
| Paseo | no | 23,208 | Paseo is the foundation Clisbot is built on; Clisbot adds its own bots, group chat and OpenClaw channel integrations on top |
| CCManager | no | 1,278 | ccmanager manages only Claude Code sessions across worktrees; Clisbot orchestrates several providers with a shared daemon and mobile access |
| OpenClaw | no | 394,046 | provides the channel integrations Clisbot adapts as part of its stack; on its own it isn't tied to git worktrees and multiple CLI providers the same way |
README in short
The README, in English, Chinese, Japanese and Korean, frames Clisbot as building on the Paseo project with OpenClaw's channel integrations and its own bots added, with a separate monorepo package map for contributors.