GitBot turns a job you keep giving Claude Code, Codex or OpenCode into a bot. Write the instructions once, set what it may touch, and run it in any repo. Each run is a thread you can come back to. Install bots other devs made from the Library, or share yours with a code. ShipGuard, for example, reads your branch and says merge or block, with file and line evidence. Runs on your machine with the logins you already have. Open source. No account, no telemetry.
Most of us give our coding agent the same few jobs every week. Review this branch. Write the release notes. Find the tests I missed. Each time we paste the same instructions and pick the same permissions again.
GitBot saves that job as a bot. You write the instructions, pick Claude Code, Codex or OpenCode, and choose what it's allowed to touch. Then you run it in any repo. Every run gets its own thread, so you can close the tab and come back later.
Bots are easy to share. Last week we ran a 90-minute online build night. Two developers who had never used
GitBot built bots and got them into the Library before it ended:
ShipGuard (by Somesh) reviews your branch and ends with merge or block. It cites file and line, and edits nothing.
Sheet Consolidator (by Guru) merges spreadsheet tabs into one table. Nothing to do with code, which we loved.
Try it:
npm install -g @gitbot-hq/gitbot
gitbot start
It runs on your machine with the agent logins you already have. No GitBot account, no hosted database, no telemetry. It's open source.
Coming next: schedules and triggers, so a bot can run without you starting it.
One honest note: GitBot has no network login yet. Keep it on a trusted network and don't expose its port to the internet.
What job do you keep giving your agent that should be a bot?
the one I'd save first is writing changelog entries from a merged PR diff. I do it every release, it's always the same shape (what changed, why, any migration steps), and I always half-ass it because it's the last step before shipping and I just want to be done. a bot that already knows our changelog format and just needs the diff would actually get used, unlike half the automation ideas I have.
Congrats on shipping GitBot! Building on top of the coding agent you already use is a smart angle — no new workflow to learn, and bots that live where the work already happens. Nice execution.
Thanks for shipping GITB-002 so fast! Read through the localhost-default branch: 127.0.0.1 by default, explicit --host 0.0.0.0 opt-in, and a test that checks LAN is refused. Nice bonus dropping the public IP lookup too. Looking forward to it landing in the npm release. A token on the LAN URL/QR would be the cherry on top 🍒
Can each bot remember decisions from previous runs or does every execution start fresh?
About GitBot on Product Hunt
“Build bots on the coding agent you already use”
GitBot launched on Product Hunt on September 30th, 2026 and earned 177 upvotes and 11 comments, placing #4 on the daily leaderboard. GitBot turns a job you keep giving Claude Code, Codex or OpenCode into a bot. Write the instructions once, set what it may touch, and run it in any repo. Each run is a thread you can come back to. Install bots other devs made from the Library, or share yours with a code. ShipGuard, for example, reads your branch and says merge or block, with file and line evidence. Runs on your machine with the logins you already have. Open source. No account, no telemetry.
GitBot was featured in Open Source (68.9k followers), Artificial Intelligence (479.9k followers), GitHub (41.4k followers) and Bots (110.9k followers) on Product Hunt. Together, these topics include over 175.4k products, making this a competitive space to launch in.
Who hunted GitBot?
GitBot was hunted by Sunny ☀️. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how GitBot stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Sunny ☀️
Hey Product Hunt,
Most of us give our coding agent the same few jobs every week. Review this branch. Write the release notes. Find the tests I missed. Each time we paste the same instructions and pick the same permissions again.
GitBot saves that job as a bot. You write the instructions, pick Claude Code, Codex or OpenCode, and choose what it's allowed to touch. Then you run it in any repo. Every run gets its own thread, so you can close the tab and come back later.
Bots are easy to share. Last week we ran a 90-minute online build night. Two developers who had never used
GitBot built bots and got them into the Library before it ended:
ShipGuard (by Somesh) reviews your branch and ends with merge or block. It cites file and line, and edits nothing.
Sheet Consolidator (by Guru) merges spreadsheet tabs into one table. Nothing to do with code, which we loved.
Try it:
It runs on your machine with the agent logins you already have.
No GitBot account, no hosted database, no telemetry. It's open source.
Coming next: schedules and triggers, so a bot can run without you starting it.
One honest note: GitBot has no network login yet. Keep it on a trusted network and don't expose its port to the internet.
What job do you keep giving your agent that should be a bot?