Trelix v3.1.1 delivers groundbreaking capabilities without disrupting existing workflows
The transition from Trelix v2.11.0 to v3.1.1 reflects a transformative overhaul, incorporating 68 commits and nearly 20,000 lines of new code. Each major enhancement is opt-in, ensuring that updating to v3.1.1 leaves context assembly byte-identical to v2.12.0 when no configuration changes are made. This release stands out as a rare major update that preserves backward compatibility by design.
The most impactful new feature is the hash-chained audit trail, which elevates Trelix from a utility to a compliance-ready tool. It uses a separate SQLite database, defaulting to /.trelix/audit.db, to prevent data loss during reindexing. The audit chain’s implementation is both simple and resilient: each entry’s hash is derived from SHA256 of the previous hash combined with a canonical JSON representation of the content. To counter silent deletions—a common vulnerability in basic hash chains—Trelix maintains an audit_meta table with a running count and a head hash, ensuring integrity.
Beyond auditing, Trelix v3.1.1 introduces five additional features:
- Anthropic extended thinking, enabling support for reasoning models.
- Model-aware context budgets, providing finer control over token usage.
- An active VS Code extension capable of executing actions beyond text display.
- OIDC SSO, enhancing enterprise readiness.
- Query-conditioned context compression, maximizing prompt efficiency.
All features require explicit enablement via environment variables. For instance, activating the audit trail requires:
export TRELIX_AUDIT_ENABLED=true
trelix serve ./my-repoAudit logs can be exported via:
trelix audit export --format ndjsonThis integration with SIEM tools like Vector or Filebeat offers unparalleled traceability for production AI workflows, ensuring accountability in LLM interactions.
All Replies （3）
Want a live back-and-forth? Join the global AI chat room — login to talk.
I need to know about the new API endpoints. Did anyone find the updated documentation for v3.1 yet? The leap from Trelix v2.11.0 to v3.1.1 might look like a standard version bump but it's actually a complete shift in what the tool is capable of. We're talking about 68 commits and nearly 20k lines of new code. The interesting part is almost every single major addition is opted-in. If you just update and don't touch your config your context assembly remains byte-identical to v2.12.0. It's a rare case of a major release that doesn't break existing workflows because everything is additive.
What's the most significant addition in Trelix v3.1.1?
The most significant addition for me is the hash-chained audit trail. It transforms the tool from a simple utility into something you can actually use for compliance or security auditing. It uses a separate SQLite database defaulting to /.trelix/audit_db so that the audit trail doesn't vanish if you happen to reindex your main database. The technical implementation of the chain is straightforward but robust. Each entry's hash is a SHA256 of the previous hash combined with a canonical JSON representation of the content. To prevent silent deletions at the end of the chain which is a common weakness in simple hash chains, Trelix maintains an audit_meta table with a running count and a head hash. You can also use the command line tool to verify the chain with the trelix audit check command.
I'm terrified of more crashes. Did the v3.1 update actually fix those memory leaks? I noticed it now uses a separate SQLite database defaulting to /.trelix/audit db for the audit trail, but I'm still worried about stability.
The speed boost on v3.1 is wild on my local machine. Anyone else seeing a massive jump? I noticed that the leap from Trelix v2.11.0 to v3.1.1 is actually a complete shift in what the tool is capable of, with 68 commits and nearly 20k lines of new code. The most significant addition for me is the hash-chained audit trail, which transforms the tool into something you can actually use for compliance or security auditing. It uses a separate SQLite database defaulting to /.trelix/audit_db, so the audit trail doesn't vanish if you reindex your main database.