vshulcz

7 ms·

1.
by vshulcz 9d ago
https://github.com/vshulcz/deja-vu
2.
by vshulcz 9d ago
Benched cold start recently: 19k LongMemEval sessions laid down in the real ~/.claude and ~/.codex layouts, 100 questions whose answer sits in exactly one session, scored by whether that session comes back (bias: I built deja, one
3.
Show HN: Injex – tiny typed DI for Python validates the graph before startup(github.com)
2 points by vshulcz 2mo ago|0 comments
4.
by vshulcz 2mo ago
That's why I ended up creating two forced paths for this. First, the SessionStart hook aggressively introduces context immediately after loading, completely bypassing the agent's requirements. Secondly, I'm forcibly changing
5.
by vshulcz 2mo ago
I intentionally used a dictionary for this. When I dig into old sessions, I'm usually looking for a very specific token (the exact error string, the unique function name, a specific cli flag) rather than a generic value. Adding semanti
6.
by vshulcz 2mo ago
This is a fair point of view and ofc it should be taken into account. When called automatically, a small overview (~2 KB) of the imported sessions is included in the context. However, when syncing, only data records are moved not instructio
7.
by vshulcz 2mo ago
My particular interest in deja was that I found a combination that I couldn't find on this list: zero dependencies, zero LLM calls, verbatim text search, proactive secret cleanup and P2P synchronization over SSH.
8.
by vshulcz 2mo ago
Yes, ctx is the closest cousin here. I actually linked it in my top comment. This causes a very similar itch, but we went a slightly different route regarding some implementation details Secrets: The ctx README mentions saving the text as i
9.
by vshulcz 2mo ago
Hi HN. I built deja after watching Claude Code and Codex debug the same problems more than once. The annoying thing was that the answer usually already existed somewhere in my old sessions. My records were stored on the disk for months (~3.
10.
Open-source memory for coding agents, synced over SSH(github.com)
131 points by vshulcz 2mo ago|35 comments
11.
by vshulcz 3mo ago
the variant-types-for-dispatch thing is a nice tradeoff, makes sense. honestly the strongest pitch in there is the "write the hot module in nimic instead of dropping to c/rust/cython" angle, which is basically the cython
12.
by vshulcz 3mo ago
The line I'd push on is "valid Python that runs unmodified in CPython." True at the syntax level, but the speedup isn't really coming from Nim as a backend, it comes from how much of Python's dynamism you can pin do
13.
by vshulcz 3mo ago
Even past the TLS point (CDNs terminate TLS, so they can read the body) there's a harder problem nobody's solved: to cache a QUERY the cache has to fold the body into the cache key, and there's no standard way to canonicalize