Who it is forA developer joining a project who wants answers about how it works without risking changes to the files.
The problemReading an unfamiliar codebase is slow, and an agent with edit access could change files while you are only asking questions.
The outcomeAnswers about the code from a Codex thread that runs in Plan only mode inside the chosen repo folder.
What you need first
- Node.js 18 or newer
- At least one installed, signed-in coding agent: Claude Code, Codex, or OpenCode
- A local folder that holds the repos you want the bot to work in
Steps
- Install the
codexCLI and runcodex login. - Run
npm install -g @gitbot-hq/gitbot. - Run
gitbot startfrom the folder that holds your projects, then open http://localhost:3000. - Create a bot, choose Codex as the agent, and set Permissions to Plan only.
- Open a new thread, choose the repo folder, and ask how one feature works.
Prompt for your agent
Using the gitbot-hq/GitBot package, start it with gitbot start and create a Codex bot with Plan only permissions. Ask it to explain how <feature name> works in <repo folder>. Expected output: a written explanation that names the files it read, with no edits made. Verify that the working files are unchanged after the reply.
Caveat. Codex cannot enforce an Allowed tools list, so Plan only mode is the control to rely on for read-only work.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page