No reviews yetBe the first to leave a review for VibeRaven
Maker
📌
Hey, I'm Ohad. I built VibeRaven.
It's open source: https://github.com/ohad6k/VibeRaven
VibeRaven is mission control for apps you built with AI agents. Agents, providers, versions, releases. One place to see what changed, what broke, and what your coding agent should do next.
I made it because getting to a demo got easy. Running the thing as a real product did not. You ship a new version and something regresses. Stripe needs a dashboard fix. Your agent writes code but does not always know what changed between releases or which provider still needs a human.
That's the problem I wanted to solve. Before launch checks are part of it. The part I use every week is after launch. Production bugs, postmortems, version drift.
MIT. Free to use.
If you try it, I would love feedback. Star the repo if it helps, open an issue if something is off, and PRs are welcome if you want to contribute.
Thanks for checking it out.
The post-launch use case you described is the more compelling angle honestly - the "agent wrote code but doesn't know what changed between releases" problem hits every team running AI-assisted CI. Pre-launch gap detection is useful once, but version drift and postmortem tracking is a recurring pain. Does VibeRaven watch git diffs automatically, or do you trigger the scan manually after each deploy?
Report
Maker
@galdayan Fair point. The recurring pain is post launch, not the one time pre ship scan.
Right now scans are on demand or CI triggered. You run npx -y viberaven --agent-mode or --verify, or wire it into a GitHub Action on PR or deploy. It does not sit in the background watching every commit.
For release to release, Studio compares two git refs when you ask and lets you drag that context into agent chat so the agent actually knows what changed.
Automatic git diff watching across releases is exactly what I want to ship next. Your framing is spot on. Thanks for calling it out.
Report
Maker
If you have any questions or want to just share things, feel free to send me a message on LinkedIn
@ohad6k This is an interesting idea.
The post-launch use case you described is the more compelling angle honestly - the "agent wrote code but doesn't know what changed between releases" problem hits every team running AI-assisted CI. Pre-launch gap detection is useful once, but version drift and postmortem tracking is a recurring pain. Does VibeRaven watch git diffs automatically, or do you trigger the scan manually after each deploy?
@galdayan Fair point. The recurring pain is post launch, not the one time pre ship scan.
Right now scans are on demand or CI triggered. You run npx -y viberaven --agent-mode or --verify, or wire it into a GitHub Action on PR or deploy. It does not sit in the background watching every commit.
For release to release, Studio compares two git refs when you ask and lets you drag that context into agent chat so the agent actually knows what changed.
Automatic git diff watching across releases is exactly what I want to ship next. Your framing is spot on. Thanks for calling it out.
If you have any questions or want to just share things, feel free to send me a message on LinkedIn