← All Posts

gitbot-hq/GitBot — 138 Stars

Create reusable bots powered by Claude Code, Codex, or OpenCode. Run them locally across your repositories with persistent threads and permissions you control.

shorts ID: shorts-gitbot-hq-GitBot #shorts#gitbot-hq#gitbot

Watch Episode

About This Repo#

gitbot-hq/GitBot — 138 ⭐ | TypeScript

GitBot documents reusable bots powered by Claude Code, Codex, or OpenCode, with persistent repository threads and agent-specific permissions. The reel uses author-published UI screenshots and the README, not an independently executed task-quality test.

Narration#

Running the same agent task in three repos? GitBot keeps each job and thread together. Create a reusable bot, choose a repo, and return to its conversation. You control permissions; Codex uses sandbox modes. Setup needs Node eighteen plus and a signed-in coding agent. Keep its unauthenticated server on a trusted network.

Source Scope and Requirements#

Setup requires Node.js 18+ and an installed, signed-in local coding-agent CLI. GitBot’s server has no authentication: keep it on a trusted network and never expose it publicly. GitBot is MIT-licensed; the selected coding agent and model may have separate usage requirements or charges.

Permission semantics differ by agent. The current README describes Codex sandbox modes, not per-tool approval. A legacy form label in the published screenshot differs from those current semantics; the narration follows the current README. The screenshots demonstrate the published UI, not independently verified agent quality. Some peripheral controls are cropped and a thread title is naturally truncated; primary evidence remains readable.

Source snapshot: GitHub commit 34135f2edaf249a44ec9924ba9e4052002e4a3eb. Publication was explicitly authorized for the delivered reel; the agent’s listening and continuous-motion assessments remain pending and are not represented as an automated audiovisual pass.

Watch#