Repository navigation
Releases
GoneBy v1.1.0 — ctx-audit release
GoneBy 1.1.0 — the ctx-audit release
An external comparison (gottz.de/ctx-vs-goneby.html, by the ctx project) catalogued nine ways this project's documentation outpaced its code. Every claim was independently verified against a4e326e, found true, and is closed here with a named regression test. Full claim→fix→test ledger: docs/AUDIT.md. Credit where due — it was a good audit.
Fixed
- Project-scoped memory IDs — identical text in two projects no longer overwrites each other's entries.
- Judge fails open for real — short or empty verdict lists KEEP the unjudged entries, warn, and surface as
judge_fallback_batches(plugin and standalone judge both had the silent-drop bug). - Master capture switch now gates
wall_append(it computed the verdict and discarded it). - One shared WAL default (
~/.goneby) for CLI, MCP server, and Hermes plugin — the split-brain paths are gone;scripts/migrate_wal.sh(dry-run default, sha256-verified, non-destructive) moves existing stores. - Restart-safe recording — message identities persist in WAL metadata; dedup state re-seeds per WAL (builtin
hash()was salted per process and could never survive). - Deterministic SHA-256 dedup + trailing-punctuation merging (Latin & CJK); docs state exactly what merges.
- Qdrant works with its pinned client —
search()→query_points(); live-server testing then exposed a second defect: non-UUID string point IDs are rejected server-side, so IDs now map deterministically (UUIDv5) with the original recoverable from payload. - No provider hardcoded anywhere — the MCP judge is configured via
GONEBY_LLM_*(OpenAI-compatible default via the already-declared httpx; Anthropic as declared opt-in extragoneby[anthropic]). Unconfigured walks now return an actionablestage=judgeerror.
Added
- Position-bound WAL (v2 framing):
v2:<seq>:<base64>with file name + hashed directory token + sequence authenticated into the AEAD tag. Deleted lines report[GAP], reordered lines are excluded from judging, spliced-in lines from other logs fail their tags. Legacy lines stay readable, flaggedintegrity: unbound. Wrong-key reads say "wrong key" via the new.keyidsidecars. Honest limits: a trailing deletion is not detectable without a head-hash chain (documented). - Live integration tests against real Qdrant and Valkey containers (
@pytest.mark.integration, auto-skip when unreachable). - Backward-walk selection-quality harness (
scripts/eval_walk.py+ labeledtests/fixtures/walk_golden.json+docs/BASELINE.md) — the audit's strongest methodological hit was that selection had never been measured; now it can be, reproducibly. - Test suite: 172 → 205 passed, zero warnings, green under both
pytestandpython -m pytest, ruff clean.
Docs
The security/threat-model sections now say what the code actually does: the transcript log is encrypted and position-bound, and the searchable vector store holds plaintext by design (semantic search needs it — protect the store with store-side controls). "Keeps ~10-20%" and scale figures are labeled design targets until docs/BASELINE.md has measured rows.
Migration note: existing Hermes installs keep entries under <hermes-home>/plugin-data/goneby/ until you run scripts/migrate_wal.sh (review dry-run, stop the gateway, --apply). Until migrated, new writes go to the shared ~/.goneby default; GONEBY_WAL_PATH/GONEBY_DATA_DIR override.
GoneBy v1.0.0
GoneBy v1.0.0 — first stable release
Retroactive project memory for LLM agents: capture everything cheaply now,
learn what actually mattered at project close, remember it forever.
What's in this release
Core pipeline (all four phases)
- Encrypted per-project write-ahead log — ChaCha20-Poly1305, per-entry nonce,
append-only, corruption-tolerant reads - Backward walk: retrospective filtering judged against the shipped product —
verification, not prediction. Fails open; an unparseable judge never
destroys evidence - Embed + vector store with content-hash IDs: idempotent re-indexing,
Matryoshka truncation (1024→512 default) with unit-normalized storage - Semantic retrieval, project-scoped by default, cross-project opt-in
Integration surfaces
- Hermes plugin: automatic per-turn capture via
pre_llm_call, per-project
WAL naming resolved from session context (git repo root), recall injection
(opt-in),/gonebyslash command, 7 agent tools, coexists with any memory
provider - MCP server (
goneby serve) — any MCP client, no Hermes required; dual
support for mcp SDK 1.x and 2.x - CLI:
generate-key,append,read,status,serve,project,
mode,platform,gate
Capture policy — full user control
- Default: capture on everywhere
- Master gate, per-gateway platform kills (e.g. a Telegram gateway),
per-project.goneby.jsonmarkers, personal user overrides, and a global
opt-inmode for disable-by-default operation - Everything persisted in
~/.goneby/config.json; status surfaces the
effective verdict and why
Verified
- 158 tests pass (WAL crypto, store, scoping, walk, policy decision table,
plugin surface against a fake Hermes ctx, CLI, state.db resolution) scripts/smoke_test.pyproves a live stack end-to-end: embedder reach,
real-model ranking (related/unrelated cosine 0.67/0.25 with
Qwen3-Embedding-0.6B Q8_0 on llama.cpp), store round trip, project
isolation, WAL ciphertext-at-rest — with full cleanup- ruff clean; secret scan across all tracked files: zero hits
Docs
docs/SETUP.md— full stack from zero: library, key, llama.cpp acquisition- model URL, serve/verify commands, valkey or Qdrant, MCP client config,
Hermes plugin install, troubleshooting table
- model URL, serve/verify commands, valkey or Qdrant, MCP client config,
docs/OVERVIEW.md— mechanism, benefits, every option, honest limitsdocs/architecture.png/.html— the four-phase diagram
Install
git clone https://github.com/rahlquist/goneby && cd goneby
uv venv .venv && uv pip install --python .venv/bin/python -e ".[mcp,valkey]"Or pip the attached wheel: pip install goneby-1.0.0-py3-none-any.whl[mcp,valkey]
(sdist also attached). Full instructions: docs/SETUP.md.