GitBot CLI
GitBot runs Claude Code, Codex or OpenCode locally as reusable bots with persistent threads and permissions you control.
- 242 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- No authentication and the port listens on all interfaces: a network client runs agents with your account's rights
- Bots act with the user's file and shell access; auto-approval removes per-call review
- An imported bot may run setup steps on import
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/gitbotDetects 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.
- No authentication and the port listens on all interfaces: a network client runs agents with your account's rights
- Bots act with the user's file and shell access; auto-approval removes per-call review
- An imported bot may run setup steps on import
This is third-party code. Review the repository files before installing.
What it does
GitBot is a local server with a web interface on top of the Claude Code, Codex and OpenCode CLIs you already have. A bot stores standing instructions, an agent choice, a permission mode and optional setup steps. For a task you open a thread in a chosen repository folder: the agent works there and the conversation streams to the browser. Threads persist, so you can return after closing the tab. Bots are shared as import codes or published to the GitBot Library through a pull request. No separate GitBot login is needed: the agent's own sign-in is used.
Who it is for. Developers working across several repositories who want to hand recurring tasks to coding agents from one window.
Good fit when
- A reviewer bot checks documentation against code across several repositories every week.
- A task conversation with an agent is kept so you can return to it days later.
- One set of instructions runs in turn on Claude Code and Codex.
- A bot with configured permissions is handed to a colleague as an import code.
Not a fit when
- The GitBot port would be exposed on a shared or public network.
- Codex needs a strict allowed-tool list.
- A third-party bot would be imported without reading its instructions and setup steps.
Example request
Create a bot that checks repository documentation against code and start a thread in the project folder with approval for every tool.Limitations
There is no authentication and the server listens on all network interfaces: anyone who can reach the port runs agents with your account's access. Use a trusted network and stop GitBot after a session. Codex has no approval requests: its permission mode selects a sandbox and the allowed-tool list is not enforced. An imported bot may contain setup steps that run on import. At startup GitBot looks up your public IP to print a network address. Node.js 18 or newer and at least one signed-in agent are required. The interface works best on desktop.
How to disable. Stop the `gitbot start` process and remove the package with `npm uninstall -g @gitbot-hq/gitbot`. Bots and thread records live in `~/.gitbot`; delete that directory separately.
FAQ
Do I need a separate GitBot account?
No. GitBot reuses the sign-in already done in Claude Code, Codex or OpenCode. It has no accounts, telemetry or hosted database.
Where are bots and threads stored?
In `~/.gitbot` by default. Project files stay on the machine, while prompts and code go to the selected agent's provider according to its configuration.
How does Codex differ from Claude Code and OpenCode?
Codex has no approval cards: the selected permission mode chooses a sandbox and the allowed-tool list is not enforced. Claude Code and OpenCode ask permission per tool.
Can GitBot be opened from a phone?
Yes, on one trusted network: GitBot prints a network address and a QR code. There is no authentication, so the port must not be exposed to the internet.
Which Node.js version is needed?
Node.js 18 or newer and at least one installed, signed-in agent. For `opencode` also configure a provider with `opencode auth login`.
Discussion
No questions or reviews yet.
Related
CLI toolsAn AI-agent workspace with parallel worktrees, cross-provider orchestration, and bots across chat channels.
The 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
Codync turns Claude Code, Codex, Cursor and other agents on your computer into bots you message from an iPhone or a terminal
DevChain runs a team of AI coding agents on your own machine with a shared board, chat, code review and live terminals.
One config for Claude Code and Codex in every repo: shared rules, skill packs, second-model review and a destructive-command guard
README in short
A bot is instructions, an agent choice and permissions; a thread is a conversation in a chosen folder. Sharing uses import codes or the GitBot Library, where the bot drafts a listing and the owner approves the final diff.