What’s new in Lifebase.

Fixes

• Clear the pending update pointer after successful update finalize --keep-handoff while preserving the review workspace. Retained review files no longer break status checks or block the next update. Failed validation still preserves the pending review for retry.

Network reliability

• Allow at least two seconds for each IPv4/IPv6 connection attempt so slower routes can complete license checks, sign-in, and logout without extra Node.js options. Keep automatic address selection, longer user-configured attempt timeouts, and existing overall request deadlines.
• Explain connection and request timeouts instead of showing only fetch failed. Failed logout now includes the underlying error and keeps the saved session when server deactivation cannot be confirmed. JSON error codes and exit codes remain unchanged; timeout details include a transport_code.

Documentation

• Add a link to the Lifebase website in the README.

Account sign-in

• Choose Lifebase account or License key inside Sign in and Change license. Account sign-in uses browser approval with Google or GitHub, then selects a linked license in the terminal.
• Add lifebase login and login --no-browser for account sign-in, including approval from another device. Temporary codes expire after ten minutes; automated key activation keeps its existing contract.
• Preserve the current session until replacement sign-in succeeds. Store only the selected license session, and end account-issued sessions when the account or license ownership link is removed.

Content languages

• Install the English or Korean edition of Lifebase 0.3.0. The CLI checks the selected language against the downloaded archive and its release state before creating the vault.
• Updates and existing-vault activation read the language from the local vault state. Ordinary updates keep that language and reject a different --locale, including updates prepared from local ZIPs. Base and target releases must match the installed language.
• Korean releases before 0.3.0 remain compatible with their original archive names and state files without language metadata. Release caches continue to separate languages.

Lifebase updates

• Update releases can now carry validated, localized follow-up guides for work outside the vault transaction. Human output follows the pending or selected release locale across preparation, review, status, finalization, and automatic apply, with Korean headings and level labels and an English fallback for untranslated locales. The JSON contract retains every applicable guide, while follow_up_required distinguishes required external work from a successfully completed vault update.
• When agent review is required and the lifebase-update package changed between Base and Target, the CLI now stages the complete target package outside the vault and makes reading it the first human and JSON handoff step. Unchanged packages use the ordinary resume action without agent_bootstrap, while changed packages can guide older installations without partially updating the vault before transactional finalization.
• Agent handoff requests now follow the installed content locale. Korean vaults use Lifebase 업데이트 마저 해줘; English and untranslated locales retain the compact resume lifebase update fallback. A changed target update skill appends its exact staged path without replacing the familiar request.
• Release choices are sorted by semantic version inside the CLI before it determines the latest compatible release, default selection, and badges, so an unordered server response cannot change the menu result.

Lifebase updates

• Update review now keeps a fixed decision bar below the conflict list, showing every available outcome and a plain-language explanation for the selected one. Saved drafts explicitly prompt the user to choose Use edited result, unavailable edited results remain visible but disabled, and the file column reserves enough space for the longest status so moving between files or saving a draft no longer shifts the list. Reopening a fully resolved review shows the list again and waits for Enter instead of finalizing immediately.

Agent setup

• Added OpenClaw, Gemini CLI, Google Antigravity, OpenCode, Cursor, GitHub Copilot, Cline, Windsurf, and Kiro integration alongside Hermes, Codex, and Claude Code. Claude setup creates a safe CLAUDE.md adapter and .claude/skills links, Gemini creates a safe GEMINI.md adapter, Cline and Kiro receive links in their own project skill directories, and OpenClaw uses its validated config writer. All integrations derive from canonical AGENTS.md and .agents/skills content without packaging duplicate tool-specific trees or overwriting unrelated files.
• Agent setup now presents every detected tool in one hierarchical checklist. Hermes can use the Lifebase vault as its Gateway default path, while an explicit default-off OpenClaw option can move the vault into its workspace with destination checks, connected-path updates, and rollback on failure. Equivalent dry-run and non-interactive flags are available for automation.
• Skill discovery now accepts only portable SKILL.md entries with valid frontmatter, a directory-matching name, and a non-empty description, while continuing to ignore unrelated or malformed folders when at least one valid skill is available.

Lifebase updates

• Pending updates now use one compact file list: Up and Down select a file, Left and Right choose Local, Merge required, an edited result, or Target, and L/M/T apply an outcome in bulk. D opens a scrollable Combined diff that aligns Base, Mine, Release, and any Draft with persistent text labels and distinct semantic colors; number keys retain the separate views for detailed inspection. Long diffs identify the active view and its own change count, support Page Up/Page Down, and jump between changes with N/P. E creates or resumes an external-editor draft without changing the vault. Drafts remain explicitly unresolved until Use edited result is selected. R removes a selected draft after confirmation without changing Base, Local, Target, or the vault. Protected paths name why they must stay local, such as Symlink, Linked parent, or Directory.
• Added lifebase update diff, lifebase update edit, and lifebase update reset-draft for direct review, plus the merge-required decision for withdrawing an earlier choice without deleting an edited draft. A premature finalize rejection no longer rewrites the handoff report or makes its workspace unusable.
• lifebase update decide accepts multiple review paths in one command, allowing large reviews to group every keep, replace, or completed merge decision without editing internal JSON.
• Review decisions now start empty, so finalization cannot silently preserve unreviewed conflicts. lifebase update review, simplified update decide --vault, and update cancel keep humans and agents out of internal JSON while exposing only the review paths they need.
• Pending reviews created by CLI 0.1.6 no longer treat its prefilled keep-local defaults as user choices; they reopen as unresolved and require explicit decisions before finalization.
• Starting a new update no longer overwrites an unfinished handoff. Interactive users can resume or explicitly restart it, while automation receives a structured pending-update error.
• AI-produced merged files are now content-addressed when their decision is recorded and rejected if they change before finalization.
• Non-interactive updates now report an explicit pending_review, ready_to_apply, applied, or up_to_date status with completion, vault-change, automatic-change, review, and unresolved counts. Initial JSON, detailed review, and recorded-decision results advance through review, decide, and finalize actions using an executable command plus complete argument array instead of internal updater paths. lifebase status also reports an unfinished update and its next step.
• The updater now migrates away from older packaged Claude adapters: untouched CLAUDE.md and materialized .claude/skills files are removed with their empty directories, customized copies require an explicit review decision, and setup-created local links remain outside the release baseline.

Lifebase updates

• Existing vaults that manage .claude/skills as an internal symbolic-link alias of .agents/skills can now update without duplicate conflict entries or a symlink-component failure. The updater preserves the alias and applies or reviews canonical skill files only once.
• Other release paths reached through symbolic links or represented by non-file filesystem objects now become preserve-only review conflicts instead of aborting handoff preparation. Safe changes can still complete after review without following or overwriting the blocked path.

Lifebase updates

• Fixed updates from real Lifebase release ZIPs being rejected when the packaged manifest and the CLI enumerated the same files in different locale-dependent path orders. Manifest verification now compares each unique path, SHA-256 digest, and size without weakening integrity checks.

Startup and CLI updates

• CLI release checks now run alongside the initial license check. Declining an available CLI update continues only the current session, asks again on the next interactive launch, and defaults the prompt to updating. A result that says the installed CLI is current is refreshed after fifteen minutes so a newly published version is not hidden by the longer available-update cache.
• The interactive wizard caches its license-scoped Lifebase update recommendation for ten minutes, while Retry and the Update action still request current server data.
• lifebase update now uses the content locale already confirmed for the installation when --locale is omitted. An explicit locale remains available as an intentional advanced override.

Guided updates

• The interactive wizard now checks for a newer compatible Lifebase release available to the current license. When one exists, it shows the version change and promotes Update to the first, recommended action without blocking local actions if the check is offline or unavailable.

Agent setup

• Agent setup now lists the readable Lifebase skills it will expose and ignores unrelated runtime directories. A skills root is accepted when it contains at least one readable SKILL.md.

CLI updates

• The interactive wizard now checks periodically for newer CLI releases and asks before updating through the package manager that owns the current installation.
• Added installation-source detection and safe update adapters for npm, future Homebrew Formula, and future winget packages. Unknown or local installations are never overwritten automatically, direct and JSON commands stay unchanged, offline checks remain silent, and declined updates are deferred for 24 hours.

Authentication

• macOS now saves the revocable login session through native Keychain Services without exposing a terminal password-data prompt or placing the session in command-line arguments.
• Successful sign-in now states that the license key itself is never stored.

Documentation

• Reworked the npm package README into a standalone user guide with guided setup, command workflows, security and privacy details, troubleshooting, and a dedicated integration contract for AI agents.

Guided terminal workflow

• Added an interactive lifebase wizard for license activation, new and existing vault setup, release selection, updates, AI-agent configuration, status, license changes, logout, and local disconnect.
• Added arrow-key menus with responsive Lifebase branding, distinct current and recommended states, scrolling release lists, q to quit a menu, and Esc to return from nested prompts.
• The wizard now returns to its refreshed main menu after recoverable actions. Ctrl+C exits cleanly without exposing an internal stack trace.
• Added guided destination choices for Documents, the current directory, and a custom absolute path, with validation before terms acceptance or download.

Authentication and vault connection

• License keys are verified immediately. Successful activation stores the returned session in the operating system credential store and restores it on later runs.
• Status distinguishes the customer-facing plan, authorized versions, license expiry, session inactivity expiry, and active-device usage such as 2/5.
• Added explicit actions to link or locate an existing Lifebase vault, disconnect its local path without deleting files, change licenses, and log out while preserving the vault.
• Suspended licenses keep their saved local state and explain why server actions are unavailable; revoked licenses require another valid key.

Installation and updates

• Added exact authorized release selection by content language and version instead of a stable/beta channel. The newest eligible release is recommended, prereleases are labeled, and releases requiring a newer CLI are disabled.
• Added lifebase releases to list supported versions available to the current license, with --include-legacy for support-ended versions that remain explicitly downloadable under that license. Interactive installation and update discovery omit legacy releases, while exact authorized version requests continue to work.
• Added verified release download and installation with clear handling for unavailable, nonempty, or unwritable destinations.
• Added customization-safe updates that automatically apply conflict-free changes and hand conflicting paths to a local AI agent for review and transactional completion.
• Update review decisions accumulate across repeated lifebase update decide commands until every review item is resolved.
• Kept the CLI version independent from the installed Lifebase product version.

Commands, agents, and packaging

• Added stable non-interactive and JSON command contracts for agents and automation without mixing terminal decoration into JSON output.
• Added local agent setup for detected Hermes, Codex, and Claude Code installations.
• Ships as one TypeScript npm package across macOS, Linux, and Windows. Python and platform-specific native binaries are not required; Node.js 20 or newer is the only CLI runtime.