Alternatives
Products that do what OpenBBox does
Stop losing prompts. Link AI interactions to Git diffs.
- 1GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 2IR
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com
- 3
- 4
- 5
- 6
- 7SC
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com
- 8
- 9
- 10
- 11
- 12PG
Jun 2026 · github.com
- 13
- 14
- 15LP
A CLI tool for managing and semantically diffing LLM prompts. Goes beyond text diff by detecting meaning-level changes using embeddings (OpenAI or local). Useful for versioning, testing, and CI/CD workflows.
2025 · github.com
- 16
- 17BE
I realised I was working on more parallel tasks with coding agents, but git branches became a huge bottleneck. Tried Git Butler but it just complicated things further. Found git worktrees as a solution but the git API was a bit too complicated for day to day. So thought I'll vibe-code this simple CLI utility to manage the process. It technically works with any setup – claude/codex/gemini + cursor/vim/whatever. Just manages git worktrees inside your repo and sets up your dev environment how you like it. Nothing fancy, just something I built to scratch my own itch. Figured…
2025 · github.com
- 18
- 19HP
Hi HN! I'm building Hopsule. If you use AI coding tools like Cursor, Copilot, or Claude, you’ve probably seen this happen: The AI writes good code - but it ignores your architecture. It doesn’t know: - why you chose a specific pattern - which conventions your team agreed on - which decisions are already locked in So it falls back to generic patterns, outdated examples, or random GitHub training data. Over time this slowly breaks the consistency of the codebase. Most teams try to fix this with: - giant Markdown files - wiki pages - long prompts - Slack threads But those aren't…
Mar 2026
- 20
- 21IC
Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…
2025 · shadowgit.com
- 22SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 23GC
It has been almost 10 years since I started the opencv-python packaging project. Scaling it to more than 100 million downloads as a side project showed me how much ease of installation and proper package distribution matter to users. It gave the computer vision ecosystem a noticeable boost. Now I have a new idea that I hope can help even more people across the broader software engineering world. A while ago, I realized I kept giving the same advice to teammates and friends when they ran into a programming issue they couldn't easily solve: go to GitHub and look at how others solved it. There…
Dec 2025 · githits.com
- 24DE
I wanted a very simple way to dump prompts, links, and todo lists into my claude code and codex agents. And to work outside of the context window. This works particularly well for sharing "Projects" between Claude/ChatGPT etc. It's open source here; https://github.com/Vochsel/dump.page Anything you dump on the board becomes an llms.txt - spatially sorted implicitly and explicity sorted via connection edges. Would love HN's thoughts!
Mar 2026 · dump.page
Ranked by how close each launch is in meaning, then by votes. Refine with a description →