Memory for AI coding agents that lives in your git history, not your vendor's. Why code is the way it is. Open source, code-aware, local-first. Building in public - spelunk.cloudhttps://bsky.app/profile/spelunk.cloudhttps://bsky.app/profile/spelunk.cloud/post/3mr3t6fejj22wspelunk search weighs two things at once: what your query means, and how the code connects. So a definition can rise into your results sharing not one word with what you typed, pulled up by the code that did match pointing straight at it.20 Jul 2026 17:32 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mr3t6fejj22whttps://bsky.app/profile/spelunk.cloud/post/3mqvmdlfh5s24Spelunk v0.9.4 is released. We went back to onboarding, the first time you use Spelunk, and hit more rough edges than we expected this late. 0.9.4 files them down. Example: The index now skips generated, vendored, and minified files, so it reflects the source you wrote. https://github.com/spelunk-cloud/spelunk/releases/tag/v0.9.418 Jul 2026 06:13 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mqvmdlfh5s24https://bsky.app/profile/spelunk.cloud/post/3mqquqhyu6s2tYou told them the new way on day one. Then a month of bug fixes in old code, and nothing said it again. It faded. An agent cannot be told once at all: the version you told is gone by the next session. https://www.spelunk.cloud/blog/common-is-not-correct16 Jul 2026 09:00 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mqquqhyu6s2thttps://bsky.app/profile/spelunk.cloud/post/3mqluoyiio224Mid-migration, most of the tree still does it the old way. The pattern that looks like precedent is the one you decided to leave. A newcomer copies it in good faith. So does an agent, every session. Common is not correct. Only the decision tells them apart.14 Jul 2026 09:16 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mqluoyiio224https://bsky.app/profile/spelunk.cloud/post/3mpqxkirzqs2egrep answers where is Y. It cannot answer why is Y this way, because the why is not a string in the current code. It lives in the decision that set it, the change that revised it, the convention it superseded. That is the layer we index, so an agent can read it back.03 Jul 2026 16:25 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mpqxkirzqs2ehttps://bsky.app/profile/spelunk.cloud/post/3mpqll7vrjc2mSpelunk 0.9.2 is out. First run just works: nothing extra to install, no separate ast-grep to fetch, and the server comes up ready right away. Five more languages indexed: PHP, Ruby, C#, Kotlin, Swift, plus a security pass. https://github.com/spelunk-cloud/spelunk/releases/tag/v0.9.203 Jul 2026 12:51 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mpqll7vrjc2mhttps://bsky.app/profile/spelunk.cloud/post/3mpo3steqxk2dChunking code by line count splits a function down the middle and retrieval gets worse. We chunk on the syntax tree instead, at function and class boundaries, across about twenty languages. The unit of a codebase is not the line, it is the definition.02 Jul 2026 13:04 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mpo3steqxk2dhttps://bsky.app/profile/spelunk.cloud/post/3mpkwblbrgk2hSpelunk 0.9.1 is out 🪨 The headline: an official Windows build. One-line install.ps1 and you're indexing. Plus keychain-backed credentials, a leaner default model (~340MB, down from ~640), and no more OOM on big files. git tracks what changed. Spelunk remembers why.01 Jul 2026 06:47 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mpkwblbrgk2hhttps://bsky.app/profile/spelunk.cloud/post/3mpgmrf52cs2yWhat changes when it is not one engineer's agents sharing memory but a whole team's, and one person's sharper convention quietly becomes everyone's default? spelunk.cloud/blog/memory-your-whole-team-shares https://spelunk.cloud/blog/memory-your-whole-team-shares29 Jun 2026 13:46 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mpgmrf52cs2yhttps://bsky.app/profile/spelunk.cloud/post/3mp7gky4wyk2zgit tracks what changed. Spelunk remembers why. spelunk 0.9 is out, and we're calling it the release candidate for v1. Not a beta. A stable CLI we've been running on real work for months, with the why-layer behind your code now syncing across machines.26 Jun 2026 17:06 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mp7gky4wyk2zhttps://bsky.app/profile/spelunk.cloud/post/3moxcjjkjuk2nWrote up a design decision we have refused to walk back: the memory your agents build up should not live inside one agent vendor. A separate layer any harness can call, stored in your git history, not ours. spelunk.cloud/blog/memory-shouldnt-belong-to-your-vendor https://spelunk.cloud/blog/memory-shouldnt-belong-to-your-vendor23 Jun 2026 11:32 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3moxcjjkjuk2nhttps://bsky.app/profile/spelunk.cloud/post/3mouvzbsoqs2oAn agent shells out to Spelunk thousands of times a session. So the line we hold: no model in the hot path. Same query, same answer, no network, nothing to spin up. A memory layer you call that often has to be boring and fast, or it becomes a tax on every step.22 Jun 2026 12:43 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mouvzbsoqs2ohttps://bsky.app/profile/spelunk.cloud/post/3mokmhskm222bIf your agent's memory lives inside one coding-agent vendor, switching agents means amnesia. That's a reasonable bet, just not ours. Spelunk talks JSONL over stdout, exit codes, optional REST, so the memory layer doesn't change when the agent does. Claude Code today, whatever you use next year.18 Jun 2026 10:26 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mokmhskm222bhttps://bsky.app/profile/spelunk.cloud/post/3mod45ca3g22uLast release we removed six CLI commands. The one I miss least: an "ask" command that wrapped a model so the CLI could answer open-ended questions. Felt great in a demo. Slow, non-deterministic, needed a model configured before the tool did anything. Drew a line: no LLM in the CLI. Held it since.15 Jun 2026 10:45 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mod45ca3g22uhttps://bsky.app/profile/spelunk.cloud/post/3mo3uiwwj3k2uSmall thing that took us too long to get right: agent memory belongs inside git history, not in a file beside the code or a sidecar store. Beside-the-code drifts and conflicts. A sidecar is a second source of truth to back up. Git notes just clone with the repo. The why travels with the code.12 Jun 2026 13:40 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mo3uiwwj3k2uhttps://bsky.app/profile/spelunk.cloud/post/3mnys32is4k2dNice side effect of storing decisions in git notes with supersede semantics: when two old notes disagree - a stale convention and the one that replaced it - it surfaces on the first query, not three weeks into a refactor. More on how this works: spelunk.cloud/blog/memory-in-git-notes https://spelunk.cloud/blog/memory-in-git-notes11 Jun 2026 08:18 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mnys32is4k2dhttps://bsky.app/profile/spelunk.cloud/post/3mnsjsqaij22pAn AI agent can read what your code does in seconds. Ask it why it's that way — why this retry backs off for 800ms, why we stopped using the obvious library — and it answers just as confidently. And it's guessing. The why isn't in the code.08 Jun 2026 20:34 +0000at://did:plc:wmk3ple53epfty65wqpy2f56/app.bsky.feed.post/3mnsjsqaij22p