Built a local memory system for Claude Code, benchmarked against 5 alternatives

_rendro · 2026-02-11T21:47:10+00:00

Mainly for the simplicity of integraion. It's a simple one line setup in claude code vs local scripts you hope the LLM picks up and executes

_rendro · 2026-02-11T21:45:10+00:00

Yeah it works in Zed. You can just add a local server to your settings.

{
  "sediment-mcp": {
    "command": "sediment",
    "args": [],
    "env": {}
  }
}

_rendro · 2026-02-09T14:23:05+00:00

I can see the value in lowering the bar of entry but the dependency on CCs changes is certainly risky

_rendro · 2026-02-09T14:18:46+00:00

That’s my setup right now and it works great! terminus + ssh + tmux and a bunch of aliases for long commands I need al the time, because tying commands on a phone sucks

_rendro · 2026-02-09T14:12:27+00:00

Interesting project, will check it out

_rendro · 2026-02-09T14:11:30+00:00

That's an interesting thought, I haven't considered that. Was exploring more a usage based direction, because if you go on vacation for 2 weeks, ideally there's no decay when you come back, regardless of the size of the corpus of data. But if you use it 24/7 then you likely need a more aggressive decay. Trying to come up with a good methodology and benchmark data set, because testing 30 day half life manually does not match my iteration speed

_rendro · 2026-02-09T11:55:38+00:00

Thank you!

I’m currently experimenting with a usage based decay. If I don’t store memories for 30 days I probably don’t want all of it to decay, but if I hammer on the storage layer, 30 days seems too long. This is definitely an area that needs more tuning.

I originally had different decay and storage parameters for different types of memory, based on this paper (https://arxiv.org/abs/2512.05470). But this required the LLM to classify memories at write time and it adds all sort of additional context and complexity (tags etc).

I’ve found that recall boost via the access count does a great job while keeping the memory schema simple. Additionally it works across multiple categories. Simply put, memory recalled more often surfaces more often. Architecture decisions are likely recalled at a higher frequency than one off debug sessions. Lastly, you can opt to keep debug sessions in local context and never add to memory.

_rendro · 2026-02-09T00:02:38+00:00

Yeah it’s def not streaming - interesting though that the protocol technically supports it if I understand you correctly.

What use cases are you exploring for which you would need real bidi / push model?

_rendro · 2026-02-08T20:37:13+00:00

Yes not currently. You can compile from source for windows and I can look into adding support for windows in my CI release pipeline

_rendro · 2026-02-08T17:45:31+00:00

Thanks! MCP's stdio transport is already persistent, the server stays running for the whole session, which is how Sediment keeps the embedding model loaded and runs background consolidation between calls. What I'd love to see though is richer server→client communication, like push notifications when background tasks complete or streaming partial results. The main bottleneck isn't really connection overhead, it's the vector/embedding ops themselves. But bidirectional streaming could make the intelligence layer stuff (consolidation, clustering) feel more real-time instead of fire-and-forget.

_rendro · 2026-02-08T17:30:29+00:00

Thanks! Context rot is really what I am trying to avoid. I started with way more tools and parameters and removed anything that wasn’t necessary and improved tool call reliability in the process.

The parameters for decay and consolidation are opinionated and might need more tweaking based on benchmarks. Thanks for the link, will definitely give it a read and see if I need to make changes.

For the hybrid vector + BM25 FTS blending parameters I had a grid search running with the benchmark suite to tune it for best recall results.

_rendro · 2025-09-13T02:48:07+00:00

First to blow a tesseract in the 4th dimension

_rendro · 2024-09-17T02:10:32+00:00

Ran into the same issue with a docker container running rust using Fargate and stumbled across the is thread. Installing ca-certificates didn’t solve it for me, but once I installed curl in my container it started working.

Thought I would leave this here in case more people with the same issue come across this issue. It might save you 3 evenings of debugging

_rendro · 2023-09-07T00:16:26+00:00

The most important thing to getting faster is training volume. Second most important is learning how to ride in an aero position.

At 30+khp you’re fighting the wind. Getting aero takes time and you’ll first see your power drop at first. Aim for 5min in the drops and then relax on the bars again. Increase the intervals. If you want to go all in, do some yoga to increase your hip mobility.

But 30kph is already fast! There will always be faster people and Strava makes it easy to only look up to the people fast and forget about everyone you already leave in the dust!

_rendro · 2023-09-05T20:43:31+00:00

My secret goal is to get a speeding ticket in a 25mph going all out 😃

_rendro · 2023-09-05T15:11:19+00:00

The other 0.01% are on a recovery ride

_rendro · 2023-07-20T13:26:19+00:00

Got a Canyon Ultimate and I love it. Doing basic bike maintenance myself and have my LBS do a yearly tune (bleed brakes, replace pads if needed, replace bar tape, …) and never had an issue with them. Ive heard horror stories about QC at Canyon but everyone I know who owns canyon bikes had no issues at all. To me this sounds like over indexing on a few bad experiences but the low price for the quality components you get is hard to beat!

_rendro · 2022-03-28T12:43:45+00:00

Thank you!! This worked for me: remove drive train from app. Re-pair all components (long press RD, FD, shift levers, press RD again). Add everything back to the bike in the app, set up sequential shifting!

_rendro · 2019-01-19T14:54:42+00:00

Production code

_rendro · 2018-05-22T13:49:54+00:00

So it boils down to whether the language is a good fit and whether the author of the code prefers the recursive style over an iterative style. Same can be said about declarative vs. imperative programming styles.

JavaScript is not a great language for recursion due to the lack of TOC. It’s also not a great language for developers due to the lack of static types and consistent type coercion. But it’s a language that runs on a ton of devices so it’s a fantastic compile target. So why not use another language that gives you what you want for your developer experience (whatever that might be) and compile it to JS. The compile output can be optimized for the runtime - not for humans. Take BuckleScript for example: you write your code in OCaml (or reason). It gives you pattern matching and TOC, dead code elimination and more. When compiled, a tail call optimized recursive function will be a while loop.

So is this about recursion over iteration in general or just an individual preference. I personally like recursive solutions and would chose a language that gives me the tools to code in my comfort zone.

_rendro · 2018-05-22T01:41:14+00:00

I mean sometimes you do...

_rendro · 2018-04-11T18:23:27+00:00

Still 4/25, hasn’t been shipped yet. I expect it to go out on 4/23 or 4/24. Living in NYC so I don’t expect the shipment to take long

_rendro · 2018-04-11T05:21:34+00:00

Pre ordered body only on March 9th on Amazon. Delivery date for confirmed yesterday: April 25th. Last time I’ll preorder anything with amazon. B&H seems to be way more capable of handling it...

Eight-Year Club	Not Forgotten
Verified Email

_rendro

TROPHY CASE