OpenLex 0.2.3

Security

• The legacy desktop server (desktop/server) listened on all network interfaces; it now listens on 127.0.0.1 only. A test checks that every server in the engine, the desktop shell and the legacy server binds to loopback.

Added

• AI record: a tamper-evident log of what the AI did (which model, which sources, what was sent online, which actions were approved), hash-chained so later edits are detectable, readable and exportable from the Word pane, the terminal app and the CLI.
• Releases are built, signed and attested on GitHub: a reproducible CLI tarball, an SBOM (CycloneDX), Sigstore signatures (*.bundle) and GitHub build provenance for every file. The install scripts are release files too (releases/latest/download/install.sh and install.ps1). How to check a download: docs/VERIFY.md.
• The install scripts also check the signature (with cosign) or the GitHub attestation (with gh) when those tools are installed, and say which checks were made.
• CI on Linux, macOS and Windows with Node 20 and 22, and a packaging smoke test.
• SECURITY.md, CONTRIBUTING.md and this changelog.

Changed

• Prompts, start-up messages, report footers, exports and user agents say OpenLex instead of LexVault. Data folders, settings and identifiers that existing installs depend on keep their names.
• npm test runs node --test test/*.test.js (Node 22 no longer accepts a folder).

Fixed

• Windows: on-device OCR kept umlauts and the section sign (PowerShell now reads and writes UTF-8).
• Changes to openlex.json made twice within the same second are no longer missed.
• Two saves of a file within the same millisecond no longer overwrite each other's earlier-version copy.
• Windows: the plugin updater extracts with the system tar.exe, not a GNU tar from Git for Windows on PATH.
• Desktop app: the engine log file handle is no longer leaked on every engine start.

---

Verify this download: every file is signed (Sigstore, *.bundle) and has a build provenance attestation from this repository's release workflow. See docs/VERIFY.md.

OpenLex 0.2.2

OpenLex 0.2.2

Word add-in: the main tool for lawyers, redesigned.

• A calm pane: your matter, the conversation, "Your data" and one main action, Review this contract. Everything else is in What can I do here? (⌘K / Ctrl+K).
• Review a contract clause by clause: choose the side you act for, a firm checklist and focus areas. Each finding goes into the document as a tracked change plus a comment with the legal basis. The review ends with a summary, Accept/Reject per finding and Save as Word/PDF.
• See what it's doing: a few plain steps while it works, "Your data: ✓ Nothing has left this computer" (or exactly where it went), numbered sources under each answer, and "checked against … ✓" on every suggestion. Stop keeps what was written.
• Comments in Word work again, your draft is never overwritten, and the pane is keyboard- and screen-reader-friendly and follows Word's light/dark theme.

Document analysis and matter overview (Word menu, /analyse, openlex analyse):

• A summary, parties, key terms, deadlines, obligations, and risks with suggested fixes. Every finding quotes the document word for word, and findings whose quote can't be found are removed. You get a readable report and a Word report.
• Matter at a glance (openlex matters show): findings, deadlines, decisions, notes and sources, with recall search (openlex recall "liability cap") and a memo export.

Terminal app:

• Works in the folder you start it in: it reads what's there, asks before saving or renaming, always asks before deleting, and can't reach anything outside.
• Clearer everywhere:
  • you always know where you are and which keys work;
  • a first-run tour, examples and "Did you mean /model?";
  • Esc never quits, and errors explain what to do;
  • /copy, /save, /transcript;
  • accessibility settings: screen-reader mode, reduced motion, plain ASCII, no colour-only meaning.

Install / upgrade

curl -fsSL https://openlex.pinemarshlands.com/install | bash
brew upgrade openlex      # or: brew install n9394/openlex/openlex

Needs Node.js 20+. The Word add-in installers on the website will follow with the next installer build.

OpenLex 0.2.1

OpenLex 0.2.1

Terminal app. Type openlex and a full-screen app opens: a setup wizard (where the AI runs, your key, where client data may go), matters with a privileged switch, chat with sources, files dragged into the window, and every task (review, chronology, translate, compare, review grid, plans) in an Actions menu. Choose who OpenLex works as with Tab instead of typing @.

Change things mid-session. /model, /key, /data, /as, /privileged, /permissions, /clear. From the command line: openlex use, openlex key, openlex policy, openlex providers, openlex test.

It asks before it acts. Saving files, running commands, opening the web or using a connector needs your OK: allow once, always for this matter, always, or don't allow. Firm rules that forbid something always win; with nobody to ask, the answer is no.

Any model, driven by a profile. Thinking, tool calling, temperature and context come from a model profile (openlex models), not from checks on the name. Firms can change or add profiles in openlex.json.

Leaner prompts. Instructions reach the model at the step that needs them: a plain question starts with ~360 tokens of instructions instead of ~1,900. openlex prompts "question" shows what each step gets.

More:

• The firm's own databases and subscriptions as data sources.
• run_bash off by default and sandboxed.
• Privileged matters can't be opened up to a cloud model.
• Guides for lawyers in docs/guides.
• The desktop app works without an account.
• A Windows installer (install.ps1, not yet tested on Windows).

Install / upgrade

curl -fsSL https://openlex.pinemarshlands.com/install | bash
brew upgrade openlex      # or: brew install n9394/openlex/openlex

Needs Node.js 20+.

OpenLex 0.2.0

First release of the open-source OpenLex engine and CLI (community build).

Install

brew install n9394/openlex/openlex

or unpack openlex-0.2.0.tar.gz anywhere (needs Node ≥ 20) and run ./openlex.

Start

openlex serve        # the local engine (keeps running)
openlex status
openlex ask "Which GDPR article governs processors?"

Bring your own model: a cloud key (Anthropic, OpenAI, Azure, Mistral, OpenRouter, Bedrock, Vertex) or a local llama.cpp (brew install llama.cpp + a GGUF). The data policy is local-only until you allow a provider.

In this release: matters and per-matter data policy, firm library and clause library, workflows (review, chronology, translate, compare), review grid with Excel export, skills and playbooks as files, plans with checkpoints, monitors (EUR-Lex, Austrian federal gazette, RSS, pages), lists, the harness map (openlex.json: model routing per role, hooks at decision points, agent profiles), System One decision-model connector (Kev / Jev), MCP client and server, local API. Docs: docs/HARNESS.md, docs/LOCAL_API.md.