Alluvia

v0.3.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 13d MCP Developer Tools

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

ai-memory claude cursor developer-tools knowledge-management local-first

+2 more

mcp sqlite

Affected surfaces

auth

ReleasePort's take

Light signal

editorial:auto 9d

Starting with v0.3.0, MCP writes require explicit opt‑in via the rate_proposal and propose_next APIs.

Why it matters: MCP API (rate_proposal, propose_next) behavior changes; deployments must enable writes to avoid silent failures.

AI summary

MCP writes become opt‑in via config or env var.

Type	Severity	Summary	CVE
Breaking	High	MCP writes become opt-in by default. MCP writes become opt-in by default. Source: llm_adapter@2026-07-18 Confidence: high	—
Feature
Feature	Medium	Distillation processes newest sessions first. Distillation processes newest sessions first. Source: llm_adapter@2026-07-18 Confidence: high	—
Feature	Medium	First-run cap limits initial distillation to ~50 recent sessions. First-run cap limits initial distillation to ~50 recent sessions. Source: llm_adapter@2026-07-18 Confidence: high	—
Feature	Low	Windows CI is now tested. Windows CI is now tested. Source: llm_adapter@2026-07-18 Confidence: high	—

Full changelog

The first five minutes, fixed — and MCP writes become opt-in.

Newest sessions first — distillation now always processes your most
recent sessions first, so the map is freshest where it matters.
First-run cap — the very first refresh distills your ~50 most recent
sessions and says so ("the remaining N backfill automatically on the next
refresh"). You see labeled themes, connections, and unfinished threads in
minutes instead of waiting out a full-history distill — and the label/
status stages keep budget headroom on day one. Tune or disable with
ALLUVIA_FIRST_RUN_CAP (0 turns it off). (#11-class first-run failures,
designed out.)
MCP is read-only by default (#12) — rate_proposal and propose_next
(the tools that write your judgments or spend your LLM budget) now return
a clear "disabled" message unless you opt in on your machine:
[mcp] writes = true in config.toml or ALLUVIA_MCP_WRITES=1. Surprise
writes are impossible, not merely detectable.
Windows CI (#13) — the platform detection that already claimed Windows
is now tested there.
Docs: SECURITY.md (private vulnerability reporting), CONTRIBUTING.md,
a ChatGPT-history import guide, and a README that says the quiet part
loudly: the whole product works end-to-end on a free-tier key.

Install: uv tool install alluvia · PyPI · Closes #12, #13

MCP write operations (`rate_proposal`, `propose_next`) are now disabled by default; opt‑in required via `[mcp] writes = true` in config.toml or `ALLUVIA_MCP_WRITES=1`.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Alluvia

Get notified when new releases ship.

About Alluvia