Reusable coding bots
Create a reusable bot with standing instructions, an agent selection, a model where supported, permission settings, optional allowed-tool lists, and optional one-time setup steps.
GitBot
GitBot is a local browser workspace for reusable coding bots powered by Claude Code, Codex, or OpenCode, with persistent threads and configurable permissions.
Local orchestration for coding agents
GitBot is a locally run web interface for creating and reusing coding-agent bots across repository folders. It connects a browser to Claude Code, Codex, or OpenCode installed on the same machine, giving each bot a defined job, an agent configuration, and permission settings.
A bot can be reused across threads, while each thread connects the bot to a chosen folder and retains the underlying agent session for later work. GitBot stores bot and thread records locally rather than operating a hosted service; the selected coding agent remains responsible for communicating with its configured provider.
Features
Local agent execution
Run Claude Code, Codex, or OpenCode locally in the selected repository folder, using the agent installation and provider configuration already on the machine.
Persistent threads
Organize work as threads tied to a bot and a folder. GitBot resumes the agent's own session, allowing a conversation to continue after returning to it.
Resumable browser workspace
Stream agent output to the browser and keep a turn running when the browser disconnects. On return, GitBot can reattach and replay buffered events.
Permission controls
Use approval prompts with Claude Code and OpenCode, or choose Codex modes such as read-only, plan, or editing in the working directory. Permission settings can be changed from a thread's chat bar.
Bot sharing and Marketplace workflow
Copy a bot's settings and instructions for another person to import, or prepare a Marketplace listing and pull request for review without automatically publishing it.
Use cases
Repository review and maintenance
Define a standing review job, such as checking whether documentation matches the current code, then start a thread in a repository and ask the bot to inspect a specific issue before making changes.
Repeatable development tasks
Use separate bots for recurring coding tasks and return to their threads later, keeping the work associated with the same repository folder and agent session.
Controlled codebase exploration
Give an agent a read-only or approval-based workflow while exploring an unfamiliar codebase, using broader permissions only when the task and repository are understood.
Sharing team workflows
Copy a bot's instructions and settings for another person to import, or prepare a public Marketplace contribution that can be inspected and submitted through a pull request.
Pros and Cons
Pros
- Runs locally with no GitBot account, hosted database, or separate cloud component.
- Supports reusable instructions, persistent agent sessions, repository-scoped threads, and optional setup steps.
- Offers approval forwarding for Claude Code and OpenCode and selectable sandbox or permission modes for Codex.
- Can be accessed from a browser on the local machine or another device on a trusted network.
- Bot settings and instructions can be copied for import or prepared for a reviewed Marketplace submission.
Cons
- GitBot has no authentication, so anyone who can reach its listening port may be able to run agents with the machine's access.
- The selected coding agents and Node.js 18 or newer must be installed and configured separately.
- Codex does not provide GitBot's per-action approval channel or enforce an allowed-tools list, so its selected sandbox mode is the main permission boundary.
FAQ
How do I install and start GitBot?
Install Node.js 18 or newer, install and sign in to at least one supported coding-agent CLI, then install GitBot with npm install -g @gitbot-hq/gitbot. Start it from a folder that contains your projects and open the local web interface at http://localhost:3000, or use the displayed network address on a trusted local network.
Which coding agents does GitBot support?
GitBot supports Claude Code, Codex, and OpenCode. You use the agent's existing installation and login; GitBot does not require a separate GitBot account.
What is the difference between a bot and a thread?
A bot stores reusable instructions, an agent choice, a model where applicable, a permission mode, optional tool restrictions, and optional setup instructions. A thread pairs that bot with a repository folder and preserves the agent session for later work.
What are the main security considerations?
GitBot has no authentication and listens on all network interfaces. Anyone who can reach its port may be able to use the agents running on the machine, so it should remain on a trusted network and should not be exposed to the public internet.
Where are GitBot's data and conversations stored?
Bots and thread records are stored locally under ~/.gitbot by default, with the data directory configurable through GITBOT_DATA_DIR. GitBot itself does not host the agents, conversations, or a cloud database; the selected agent may send prompts and code to its configured provider.
Quick Facts
- Category
- Developer Tool
- Deployment
- Local Node.js server with browser interface
- Supported agents
- Claude Code, Codex, and OpenCode
- Required runtime
- Node.js 18 or newer
- Local data location
- ~/.gitbot by default; configurable with GITBOT_DATA_DIR
- Primary workflow
- Run reusable coding bots in selected repository folders
GitBot Alternatives
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
Ghost
Ghost is a terminal-based AI assistant for chatting, code generation, and CLI tasks. Includes free models, supports Linux, macOS, Windows, and is open source.
Vi3ecode
Vi3ecode is a maintained development environment for AI coding agents, keeping project context, terminal, Git, memory, flows and review connected.
hob
hob is an independent workspace for coding agents, with local control over sessions, terminals, history, routing, and follow-up work.
Grok 4.7
Grok 4.7 is an xAI model for coding and knowledge work, available via Grok Build, Cursor, the Grok API and more, from $2 per million input tokens.