Cambios
Qué hay de nuevo.
Releases, funciones y actualizaciones de seguridad. Suscríbete vía RSS.
- Release #
v1.3.2 — set up and connect everything from the app
On a clean machine the app used to open and go nowhere: it needs a background service running before it can create your vault, and installing ClauLock did not start one. It now starts the service itself the first time it needs it, so the setup wizard just works.
Connecting the tools that will use your secrets is now a button per tool. Cursor, Codex, Windsurf and Gemini used to require a terminal command; Claude Code needed one too. Connecting registers ClauLock for that tool and leaves the rest of its configuration untouched — restart the tool afterwards so it picks up the change.
A new Health section in Settings shows what ClauLock checks about your machine — is the service running, is your vault reachable, are your tools connected — and offers a one-click fix for the common problems. Where a repair needs a decision from you, it says what to do rather than pretending a button can decide it.
Assistants now know to ask before they are blocked. If you have put a secret behind approval, an assistant that needs it requests access with a reason and waits for you, instead of failing and — worse — asking you to paste the value into the chat.
Same invariant, as always: your assistant can use your secrets, and still cannot see them.
- Release #
v1.3.1 — Homebrew upgrades work again
On a Mac or Linux box where ClauLock came from Homebrew, running setup could replace brew's links with real files. Nothing looked wrong: brew kept reporting the new version, the formula stayed current, and the app kept working. But from that point on, upgrades stopped reaching the programs that actually run — you could upgrade for months and stay on the version you started with.
Setup now recognises a Homebrew-managed install and leaves those files alone, doing only the parts that are still needed: your vault, your keychain entry, the background service, and the assistant wiring. Upgrades go through brew, as they should.
If an earlier setup already broke the link on your machine, `clsec doctor` now reports it and prints the one command that repairs it. Worth running once if you installed with Homebrew before today.
No change to how secrets are stored or used, and nothing to redo.
- Release #
v1.3.0 — secrets with real structure, and 2FA that works
Until now a secret was one value with a name. In 1.3 it can hold the fields that actually belong together — a username next to its password, an API key next to its region and account id, a card next to its expiry. You pick the type when you create it and the app offers the fields that type usually carries, so you are filling in a form rather than inventing field names.
Every field carries a human label and a position you choose, so an entry reads like something a person wrote instead of a wall of slugs. Copy any one field in a single click; revealing still takes a deliberate second step behind Touch ID.
Two-factor codes are now first class. Paste an authenticator setup code once and ClauLock generates the live 6-digit code on your machine, with the countdown shown so you know whether to wait for the next one. Your AI can use that code in a command without the code — or the seed behind it — ever entering the conversation.
Your AI can now ask before it is blocked. Secrets you have gated behind approval used to fail first and explain later, which read like a broken tool. Now the assistant can request access up front, telling you which secret and why, and you approve it once with a time limit. It can also see what it currently holds and hand it back when the task is done.
Editing got easier: change a stored value from the app, reorder fields, and fix a description without recreating the entry.
Under the hood this release also closes a long list of hardening items from a full audit — tighter redaction of encoded values, plaintext cleared from memory on every path, reveals revoked the moment the vault locks, and stricter rules about which components may ask for what.
Same invariant, end to end: your AI can use your secrets — it still can't see them.
- Seguridad #
v1.2.1 — security hardening
1.2.1 is a security-hardening release following a full audit of ClauLock. The core guarantee held across every layer — the model never sees a plaintext secret — and this release tightens the defenses around it.
Redaction fails closed. If the output scrubber can't run for any reason, output is now withheld rather than shown, and even very short secrets are always redacted. A revealed secret is released only once it's recorded in the tamper-evident audit log.
Sync gets rollback protection. A compromised or misbehaving relay can no longer serve an older snapshot to quietly undo a credential rotation or bring back a secret you deleted — out-of-date snapshots are refused.
A more resilient app. The desktop app no longer blanks out on an unexpected error — you get a clear recovery screen instead — and anything copied to your clipboard is cleared automatically even if you close the window first.
Stronger supply chain. The installer verifies the release signature by default, and every shipped binary is signed, so a tampered download is caught before it runs.
Same invariant, end to end: your AI can use your secrets — it still can't see them.
- Release #
v1.2.0 — a calmer, 1Password-inspired workspace
ClauLock 1.2 reworks the desktop app around clarity. One title bar (no more doubled wordmark) with global search built in, a single collapsible sidebar, list rows trimmed to the essentials, and a read-first detail view that groups a secret's fields into one card — editing is now an explicit step.
The detail panel stays hidden until you pick a secret, so a fresh launch or a filtered list feels calm instead of cluttered.
Window dragging is back: you can move and reposition the window across displays again (a regression from the new title bar, now fixed).
Same invariant, end to end: your AI can use your secrets — it still can't see them.
- Función #
v1.1.0 — accounts & contacts for your secrets
ClauLock 1.1 adds a lightweight CRM over your vault. Create accounts (a client company or an individual) and contacts, then link them to a secret by role — account, owner, billing, technical, or security. Now "the Stripe key for Acme Corp, security contact Jane" is something you and your agent can actually find.
The privacy line holds and gets stronger: contact details (email, phone) are encrypted at rest and shown only in the app. Your AI agent can route by an account or contact's name and role, but the daemon never hands it an email or phone number — the same way it never hands over a secret value.
Everything stays local and end-to-end: the model can use your secrets and now understands who they're for, without ever seeing the secrets or anyone's personal details.
- Release #
v1.0.0 — new identity + structured secrets
ClauLock turns 1.0 with a complete visual rebrand. The new mark is the placeholder you already use — curly braces holding a keyhole — because that's exactly what ClauLock does: your agent references a secret by name, and the value stays locked. The app and the site move to a warm Vault palette (espresso, bone, champagne gold) that sets ClauLock apart from the sea of cold-blue security tools.
Structured secrets: a single entry — a login, a database, a cloud account — can now hold many fields (username, password, host, one-time-code seed, recovery codes), each revealed only with Touch ID and never shown to your agent.
Faceted Secrets workspace: organize by client, provider, project, or environment, with smart views, favorites, a deployment map, bulk actions, and per-field reveal.
Same invariant, end to end: the model can use your secrets — it still can't see them.
- Release #
v0.6.0 — DMG installer + first-run auto-detection
ClauLock now ships a real .dmg installer next to the .app.zip and the brew tap. Drag-to-Applications, eject, launch from Spotlight. The .dmg and the .app inside are both signed with our Apple Developer ID and notarized, so Gatekeeper accepts the install offline.
First-run auto-detection: the UI now opens the onboarding wizard automatically the first time you launch it without an existing vault. No flag, no terminal — drag-to-Applications, double-click, you're in the wizard. The previous CLI-driven onboarding still works exactly the same.
Tray + Dock pattern carried over from v0.5.2: Dock icon visible at launch, menu-bar tray icon also visible, close-to-tray instead of quit. If you prefer a pure-menu-bar boot, set CLAULOCK_BACKGROUND=1.
- Fix #
v0.5.2 — UX hotfix: Dock icon + window on launch + tray click
v0.5.0 ran as a pure menu-bar app (no Dock icon, window hidden at boot). On a fresh launch users saw nothing happen — no Dock bounce, no window. v0.5.2 reverts to the standard Mac layout: Dock icon visible, window opens at launch, menu-bar tray icon also present. Closing the window goes to the tray; quit comes from the tray menu.
Tray click no longer fails on the first try. Earlier versions had a small race where the very first click could miss its anchor and swallow itself; v0.5.2 always opens the popover.
Tray icon now shows "ClauLock" next to it on macOS so it's findable in cluttered menu bars and notch laptops.
- Release #
v0.5.0 — Menu-bar app + popover + branded icons
Left-click the menu-bar icon for a 320×420 popover that shows vault status, secret count, anything overdue, and one-click actions for Lock now, Add secret, and Open the full window. Right-click for a native menu (Lock now, Open ClauLock, Settings, Quit).
Closing the main window now keeps the process alive in the menu bar — your audit log, status, and quick actions stay one click away. Quit from the tray menu when you actually want to exit.
New branded icons: a cyan lock on a deep-ink background, designed at full 1024×1024 so the macOS .icns and Windows .ico render crisp at every size, plus a monochrome menu-bar template that recolors for light/dark/highlighted states automatically.
Note: v0.5.0 originally launched as a pure menu-bar app (no Dock icon). v0.5.2 reverts to the standard Mac layout — see that entry.
- Seguridad #
v0.4.0 — Apple Developer ID notarization + Touch ID native
Every macOS binary in the release is signed with our Apple Developer ID and submitted to Apple for notarization before shipping. Gatekeeper accepts ClauLock as "Notarized Developer ID" on every install — no "unidentified developer" warning, no right-click-to-open dance.
Touch ID now drives the vault unlock natively, end-to-end. Earlier macOS releases occasionally fell back to the device passcode when our entitlement didn't match what newer macOS expected; v0.4.0 ships the right entitlement so Touch ID is the only thing you ever see.
- Función #
v0.3.1 — Onboarding wizard in the desktop app
Same five steps as the terminal version (welcome → passphrase → unlock method → first secret → done) but in the ClauLock desktop window. Your passphrase only ever lives in the typing field — it's wiped from memory the moment the vault commits.
If you install via `clsec install`, the GUI opens by itself when the install finishes; if it can't reach the desktop app it falls back to the terminal wizard with a one-line pointer. Set CLAULOCK_NO_UI=1 to skip the GUI launch entirely.
- Función #
v0.3.0 — `clsec setup` first-run wizard
Run `clsec setup` and you walk through five screens: welcome (with the never-reveal model in plain English), passphrase + confirmation, unlock method (Touch ID / polkit / passphrase-only), an optional first secret, and a final health checklist. The passphrase is zeroed from memory the moment it's committed.
The wizard works in any terminal — SSH, container, headless CI runner — and the desktop GUI version of the same flow landed in v0.3.1.
- Fix #
v0.2.1 — Install robustness on macOS Tahoe
`clsec install` now writes binaries atomically — every step (copy, sign, verify, rename) is checked, and the destination only receives a fully-valid file or stays untouched. Filesystem races that occasionally produced zero-byte binaries on APFS are eliminated.
When macOS won't grant the Keychain biometric entitlement we asked for, `clsec install` now degrades cleanly to device-only or passphrase-only mode instead of aborting. The doctor check tells you which mode you're in. v0.4.0's Developer ID notarization removes the underlying issue entirely.
Launching the background daemon now has a foreground fallback: if launchd refuses to bootstrap the agent, `clsec install` keeps running with the daemon in the foreground and tells you what to look at. No more silent "I/O error" dead-ends.
The placeholder-substitution and output-scrubber hooks now ship inside the release tarball at a stable path, and `clsec install` finds them automatically. Without these, Claude's Bash tool calls would lose the never-reveal guarantee — keeping them in the tarball makes the invariant a default, not a configuration step.
The doctor check now distinguishes "no Keychain entry by design" (you chose `--no-keychain`) from "Keychain entry missing" (something broke). And the cosmetic "SHA256SUMS not found" warning on signed builds is silenced.
- Nota #
Site: Founders wall, OG cards, /compare polish, Windows .msi (beta), perf
The marketing site now opens with the leak, not the architecture: "You pasted a GitHub token into chat last week, didn't you?" Five new home sections walk through how a real paste plays out — the popup, the comparison vs. cloud password managers, common Claude workflows, an audit-log preview, and a public Founders wall. A new blog post tells the story end to end (EN + ES).
Performance + privacy foundation: scroll-reveal animations honor `prefers-reduced-motion`, fonts are self-hosted instead of a third-party CDN (faster paint, no font-loading privacy leak), and the install picker now follows the visitor's OS for both the primary and the secondary download paths.
Windows .msi installer is in beta — drag-to-run on Windows 10+, supply-chain story identical to every other artifact (minisign + cosign). The Authenticode signing certificate isn't live yet, so SmartScreen will show a one-time warning on first launch.
- Release #
v0.2.0 — cross-device sync (E2EE) + Pro/ENT relay
ClauLock now syncs secrets across your machines without ever giving the relay anything but encrypted blobs. The sync key is derived locally from your passphrase, separately from your local and backup keys; the relay can store and serve, but it can't read. The MCP server can't call sync either — only your CLI and UI can — so an exfiltration attempt from a compromised model can't reach the network path.
Pairing a new device uses SPAKE2 with a six-word code (or a QR you can scan from your phone). Vault format moves to v2 with per-record timestamps for clean last-writer-wins on simultaneous edits; older vaults open transparently and upgrade in place on the next write.
Pro tier (hosted): a relay we run for you, Stripe-billed, with the same never-reveal guarantee as the local install. Pricing and the Founder offer live on the pricing page.
Enterprise tier (self-hosted): the same relay binary, packaged with a Postgres + object-store bundle and an offline-verified license. License expiry flips the relay to read-only — it never bricks, you can always migrate off. Custom pricing.
On the desktop side, the ClauLock UI gains a Pair page and a sync status card that counts what was pulled, pushed, kept, and rejected.
- Release #
v0.1.2 — Windows port
ClauLock is now a tri-platform tool. The Windows port adds native binaries with a Windows-native keystore (DPAPI), a Windows-native IPC transport (Named Pipes) with peer authentication, and locked memory for the encryption key — symmetric with the macOS Keychain and Linux secret-service paths that have shipped since v0.1.0.
Install on Windows: `irm https://claulock.com/install.ps1 | iex`. The PowerShell installer mirrors the macOS / Linux flow — verify, extract to your user-local app data, add to PATH. macOS and Linux paths are unchanged.
Outstanding for upcoming releases: a fully Rust-native installer flow for Windows, a Microsoft Store / winget submission, and a desktop UI Windows bundle.
- Release #
v0.1.1 — supply chain audit fixes
Three CRITICAL fixes that unblocked the public install paths:
1) install.sh shipped with a literal `__MINISIGN_PUBKEY_PLACEHOLDER__` — the build never substituted it, so curl-pipe-sh fell through to a runtime fetch from a path that 404'd. Fix: embed the real pubkey (id 82B01474F764C7B2) in the proper two-line minisign format and correct the fallback URL to where the mirror actually stores it.
2) v0.1.0 release tarballs were missing the `clsec-scrub` binary, which `clsec install` requires. Fix: add `clsec-scrub` to release.yml's CLAULOCK_BINARIES and the tap formula's File.exist? install loop. v0.1.1+ tarballs ship all five binaries.
3) .deb / .rpm / .pkg builders hardcoded LICENSE-MIT in their file lists, but LICENSE-MIT was removed in the v0.1.0 license restructure. Fix: handle both the legacy v0.1.0 set (LICENSE-MIT + LICENSE-APACHE) and the v0.1.1+ set (LICENSE-APACHE + LICENSE-BSL + NOTICE) gracefully.
Plus a sweep of audit findings: README badges, SECURITY.md verification URLs, packaging/keys/README.md, CLA.md, threat-model cosign example, brand-page key-link 404s — all corrected to point at github.com/Mackint0uch/claulock-releases (the public mirror) instead of the still-private source repo.
- Release #
v0.1.0 — first public release
ClauLock is now public. Install with `curl -fsSL https://claulock.com/install.sh | sh` on macOS 13+ or a modern Linux.
What's in the box: encrypted vault (XChaCha20-Poly1305 + Argon2id), local daemon, 16 MCP tools for Claude Code, Tauri UI for unlock/reveal/approve, importers for .env / 1Password / Doppler, rotation queue with overdue notifications, per-secret usage timeline, audit log with deep-link filtering.
Release artifacts are signed with minisign + Sigstore cosign and include SLSA provenance. Verify by hand following packaging/RELEASE.md.
- Función #
Fase 2 — rotation + timeline + deep-links
The Tauri UI now surfaces rotation due-dates prominently: a red banner on the Secrets page counts every overdue secret and deep-links to a filtered rotation queue. The queue itself is sortable and shows 'days overdue' at a glance.
Each secret has a new usage timeline panel showing the last 30 days of unlocks, reveals, and exec uses, with one click to open the audit log pre-filtered to that secret.
Metadata (tags, rotation policy, description) is editable inline from the Secrets detail drawer — no modal, no round-trip.
- Función #
Output scrubber + unified error formatter
The scrubber watches every byte leaving the wrapped command and replaces any substring matching a vault secret with the original {{NAME}} placeholder before it reaches Claude. This catches the common leak path where a tool prints the value it was given (auth failures, debug output, badly scoped set -x).
Error messages across CLI + UI now flow through a single formatter so 'vault is locked' reads identically whether it's a Bash tool call or a /secrets page load.
Las entradas del changelog son bilingües en términos técnicos. Para contexto narrativo en español, visita el blog.