Launching today
GitBot
Build bots on the coding agent you already use
121 followers
Build bots on the coding agent you already use
121 followers
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
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?
Can each bot remember decisions from previous runs or does every execution start fresh?
GitBot
@albertnelson Hey Albert! In the same thread, the bot picks up where you left off, with the previous conversation as context.
A new thread starts fresh but keeps the bot’s saved instructions.
Decisions don’t automatically carry over between threads yet. If there’s something you want the bot to remember for future runs, you can add it to its instructions.
slack ping when a bot run fails would save me checking manually!..
AI2sql
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 🍒
GitBot
@mustafaergisi Thanks for checking the branch, Mustafa! Your request got this moving for Hypership Day 😄
We’ll push it to main in a few hours, then get the npm release out.
I like the LAN token idea too,
For now, LAN access should stay on a trusted network, but we are bumping up this to push it by tomorrow.
P.S. Give the Humanizer skill a spin for the copy
Helps escaping that “Likely AI” badge 😉