What’s new in Lifebase.

Tasks

• Pause Task Notes with On Hold. Paused work is hidden from the default board, Important Tasks, and Task hub Action lists, and remains accessible in a dedicated On Hold view and the all-tasks view.
• Automatic maintenance preserves paused status and card order. Paused work is not automatically promoted or archived as completed; resumption guidance preserves open Actions and progress records.

Syncthing

• Android setup now directs you to install Syncthing-Fork from Google Play.

Account sign-in

• Sign in to the CLI with your Lifebase account through Google or GitHub and choose a linked license, while retaining license-key sign-in.

English edition

• Install Lifebase in English, including onboarding, agent instructions, Journal and Task templates, place categories, reference notes, and command messages. Existing English folder names and data fields stay the same in both editions.
• Each edition includes a README in its own language. Updates keep the installed content language and reject a package for another language.

Website and guides

• Launched lifebaseai.com in English and Korean. Explore Lifebase, compare plans, read release notes, and find installation, CLI, skill and AI agent setup guides.

Tarot images

• Tarot images now load from Lifebase static hosting instead of being bundled in the vault, reducing new-install and update downloads. Uncached images require internet access; card notes and readings remain local.
• Existing installations receive an AI-assisted follow-up guide to update image references in older notes and monthly Tarot galleries. It preserves note content, card orientation and display size, then removes only unused, unmodified bundled images after verification. Custom artwork is preserved.
• Removed the Tarot attachment exceptions from Git ignore rules. A local checker reports remaining image references, original bundled files and any paths requiring review before migration is considered complete.

Updating

• Use Lifebase CLI 0.1.10 or newer. The vault update and its required Tarot follow-up are separate steps; complete the follow-up before considering the migration finished.

AI agent integration

• Added a bundled lifebase-cli skill so connected agents use the supported CLI and machine-readable interface for status, release discovery, authentication, installation, local vault linking, session and device lifecycle, and agent setup. In-place release review remains isolated in lifebase-update, with explicit routing between the two skills.

Journal planning

• Daily plans now give every top-level schedule block an explicit end time. When only a start is known, agents infer a realistic planned end from the rest of the day and established evidence, asking only when no defensible candidate exists.

Syncthing

• Shared ignore rules now live in the synchronized .stignore.shared, while each device keeps a one-line .stignore bootstrap that includes it. Future ignore updates can propagate with the vault; existing devices need the bootstrap applied once.

Licensed updates

• Lifebase 0.2.2 requires Lifebase CLI 0.1.9 or newer so localized release guidance and target update-skill handoffs remain available throughout the update.
• Releases can now carry version-scoped required, recommended, or informational follow-up guidance for changes that cannot be completed safely inside the vault transaction. The CLI selects every applicable guide across skipped versions and keeps it visible through update preparation, review, status, finalization, and machine-readable results.
• When the lifebase-update package changed between the installed baseline and target release, agent-assisted reviews now read the target package from the protected handoff workspace before continuing. Reviews use the ordinary resume flow when that package is unchanged, and the installed skill and vault remain unchanged until finalization succeeds.
• Agent handoff requests now follow the installed content locale. Korean vaults show Lifebase 업데이트 마저 해줘; English and untranslated locales use the compact resume lifebase update fallback.

AI agent integration

• Lifebase can now expose its bundled skills and canonical vault instructions to OpenClaw, Gemini CLI, Google Antigravity, OpenCode, Cursor, GitHub Copilot, Cline, Windsurf, and Kiro in addition to Hermes, Codex, and Claude Code. The release keeps one canonical AGENTS.md and .agents/skills tree; Agent setup creates only the selected tool’s safe context adapter or removable workspace-local skill links without duplicating content or overwriting unrelated files.
• Agent setup now configures selected tools from one checklist. Hermes can start from Lifebase by default, while OpenClaw offers a separate, default-off option to move the vault into its workspace with safety checks and automatic connected-path updates.

Licensed updates

• Lifebase 0.2.1 requires Lifebase CLI 0.1.7 or newer so setup-time agent integrations and safe migration away from older packaged Claude adapters are available before installation or update.
• Update review now presents every conflict in one compact keyboard-driven list. A combined diff aligns the original passage, personal changes, release changes, and any edited draft with both persistent labels and distinct colors; separate views remain available for detailed inspection and long-document navigation. Users can edit a safe draft outside the vault, reset only that draft after confirmation, keep the local file, use the edited result, use the new release, or leave the item for AI-assisted merge. Partial drafts remain visibly unresolved and can be resumed without losing work. Paths that cannot be replaced identify whether a symlink, linked parent, directory, or other special file requires local preservation. Fully decided reviews finish immediately; unfinished merges can be resumed by telling an AI agent resume lifebase update.
• Updates now preserve symbolic-link and other non-file conflicts for review instead of aborting the entire handoff, while continuing to apply safe release changes without following the blocked path.
• Non-interactive updates now clearly report whether the vault was updated, is current, is ready to apply, or still needs review, together with conflict counts and the next CLI action. Status also reveals an unfinished update, and each structured action advances cleanly from review to decision to finalization without presenting internal updater JSON paths as instructions.
• Updates remove untouched Claude compatibility files from older releases as they move to setup-time integration, while customized files remain explicit review items and locally created tool adapters remain local-only.

Licensed installation and updates

• Added a guided lifebase command that signs in with a license key, chooses an installation location and authorized release, accepts the terms, installs Lifebase, and configures a detected AI agent.
• Added Lifebase One, Plus, and Lifetime access. One provides its selected Lifebase version on one active device; Plus and Lifetime provide every release covered by the license on up to five active devices.
• Content language and exact release are chosen independently from sign-in, so every license can use any published language available for its authorized version. The newest eligible release is recommended, and releases requiring a newer CLI are identified before installation.
• Lifebase can create a new vault or detect, locate, and link an existing one. Disconnecting forgets only the local path, and signing out releases the current device without deleting the vault.
• Installation paths are checked before download, with guided choices for Documents, the current directory, or a custom absolute path and clear recovery from invalid input or cancellation.
• Updates preserve personalized vault content. Changes that can be applied safely finish automatically; conflicting paths remain local for AI-agent review and transactional completion.
• License and release checks send only the identifiers and security metadata needed to authorize delivery. Vault paths, note names, file contents and hashes, local changes, merge decisions, and AI prompts are not sent to the licensing service.

Quick-start onboarding

• After validating the trusted bundled Lifebase templates and scripts, onboarding now enables both Templater’s Trigger Templater on new file creation and Enable startup templates permissions and reads back their device-local values.
• Reorganized onboarding as one structured 19-result checklist: nine required quick-start outcomes, six recommended personalization outcomes, and four optional setup outcomes.
• Only quick start gates the first useful Lifebase session. It begins with autonomous device and vault configuration, then asks only for user-owned facts, meaningful preferences, credentials, or real authorization blockers instead of requiring repeated 진행해 approval turns.
• Tracks only the later-stage areas the user selects; unselected or deferred items may remain unchecked when the checklist is archived and can be reopened individually later.
• Makes a tested Lifebase 일일 유지보수 automation mandatory during quick start, using a detected vault root and timezone while leaving Journal wrap-up and automatic day planning opt-in.
• Keeps the checklist at the result level while dedicated owners handle Syncthing, Git, independent backup, import, mandatory automation, and their verification details.

Obsidian hotkeys

• Bundles Mod+Alt+, and Mod+Alt+. for the left and right sidebars, mapping to Cmd+Option on macOS and Ctrl+Alt on Windows and Linux.
• Removes custom back and forward overrides so Obsidian’s default Mod+Alt+Arrow navigation-history shortcuts remain active.
• Introduces the bundled shortcuts naturally while explaining Lifebase’s core features. Device-local Templater readiness is handled by the preceding autonomous environment setup instead of becoming a user questionnaire.

First daily plan

• Added a starter day proposal for users without schedule history, covering sleep, a morning routine, morning and afternoon activity, lunch, dinner, and evening rest.
• Uses 09:00 - 18:00 as the generalized regular-workday candidate, while adapting weekends, days off, shifts, and special schedules around known commitments; users can answer 추천대로 or provide only the differences in one reply.
• Keeps approval for one date date-specific and records a reusable weekday, weekend, or shift pattern only after the user confirms that it should be reused.
• Runs this short planning bootstrap from the first real schedule request even before quick-start onboarding reaches its Journal item, while letting that item reuse the confirmed result later.

Task checkbox lifecycle

• Standardized Task Actions on four synchronized Obsidian Tasks states: [ ] Todo, [/] In Progress, [x] Done, and [-] Cancelled.
• Actions now reserve completion and cancellation dates for terminal states, while agents require direct evidence before marking work as started, completed, or cancelled.
• Daily quests use the same four checkbox meanings without Tasks metadata; journal wrap-up settles every retained quest as completed or cancelled instead of leaving an open state on a closed day.
• Extended the Tasks validator and fixtures to enforce the plugin status configuration, allowed checkbox symbols, compatible terminal date markers, and settled daily quests in newly wrapped journals.

Journal wrap-up reconciliation

• Reconciles the actual timeline before settling daily quests or related Tasks, separating confirmed activity from plans and inference.
• Removes or replaces unsupported planned blocks and prevents planned placement or agent-written restatements from becoming circular completion evidence. Later direct evidence may still revise an earlier settled state without inventing missing times.
• Preserves user-recorded completed quests through first and repeated wrap-up passes, permits explicit corrections and evidence-backed cancellation-to-completion updates, and blocks silent completion downgrades instead of relying on syntax validation alone.

Daily tarot

• Leads each reading with the card’s specific upright or reversed meaning instead of treating the Journal schedule, Tasks, or current condition as the interpretation’s main subject.
• Allows vivid, card-supported possibilities while keeping daily context optional and limited to one well-matched scene.
• Varies the interpretation, opening, and ending instead of repeatedly reducing difficult cards to cautious advice about rest, recovery, or doing less.

Journal

• Added a Tarot record calendar gallery to the monthly journal template, collecting daily tarot cards from that month.

Task lifecycle dates

• New Task Notes now record their first Task Board registration date in an immutable created_date, separate from planned or actual start and completion dates.
• Task Board cards show one status-specific relative date: registration for Backlog, start for Planned and In Progress, and completion for Done; Task List keeps all three exact source dates visible.
• Task maintenance and validation now preserve valid creation dates, normalize only clear format typos, and leave missing, invalid, or historically uncertain values for evidence-based review.

Task Action dashboard

• Dated Task Action views now group actions by note and heading, then order those groups by their nearest action date so the most imminent work appears first.

Obsidian compatibility

• Removed the bundled Image Toolkit plugin and its settings because supported Obsidian versions now provide a native image lightbox with fullscreen viewing, zoom, and pan controls.
• Updated the bundled Day Planner Enhanced to 0.6.4, Custom Attachment Location to 11.6.3, and Templater to 2.25.0 from the product maintainer’s tested Lifebase configuration.
• Updated the Templater AGPL notice and bundled Corresponding Source archive for 2.25.0.

This release adds customization-safe in-place updates and refreshes the bundled Obsidian plugins without treating a user’s editable vault as a replaceable application directory.

Safe release updates

• Added the $lifebase-update skill and deterministic updater for previewing and applying a release ZIP to an existing vault.
• Added .lifebase-state.json, a hidden release baseline containing file hashes and ownership policy for detecting local modifications during future updates.
• Restores release-owned version, README, license, and legal metadata from the target package while updating other product and structured files only when their installed bytes still match the previous release.
• Leaves user-owned note areas for agent review and supports explicit keep-local, use-target, and accept-merged decisions for every conflicting path.
• Refuses partial updates with unresolved review items, creates a rollback ZIP outside the vault, verifies every written path, and rolls back a failed write transaction.
• Supports one-time baseline adoption for personalized vaults. Updating from 0.1.0 requires the original 0.1.0 release ZIP because that version predates the installed state file.

Obsidian compatibility

• Updated the bundled Base Board to 2.5.1, Custom Attachment Location to 11.6.0, Day Planner Enhanced to 0.6.3, and Templater to 2.24.3.
• Migrated Templater configuration to its v2 schema while preserving regex-based automatic templates for journals, scraps, and Task Notes.
• Removed stale empty overrides that disabled Obsidian’s close-window command and Templater’s create-note-from-template command. Operating-system-specific sidebar and navigation-history shortcuts remain unbound for onboarding.
• Updated the Templater AGPL notice and bundled Corresponding Source archive for 2.24.3.

The first official Lifebase release. It provides an Obsidian vault that connects journals, schedules, tasks, practical life information, knowledge, career records, and durable personal context under a shared operating model for the user and their AI agents.

Feature overview

Area	Included capabilities
Records	Daily, monthly, and yearly journals with notes, photos, and tarot records
Planning	Time-blocked schedules, daily quests, day planning, and wrap-up
Execution	Task Notes, Task Actions, and Base Board task management
Life	Practical life, health, places, travel, money, and home records
Knowledge	Topic, library, and study knowledge management
Long-term context	Profile, preferences, routines, people, and analysis snapshots
Automation	Onboarding, sync, backup, import, and maintenance skills

Records and durable context

• Organizes records around Journal, Tasks, Life, Knowledge, Career, Ideas, and Archive.
• Uses _Profile for durable facts, preferences, wellbeing, routines, important people, and dated analysis snapshots.
• Provides hubs, frontmatter conventions, tags, wikilinks, and filename rules so users and agents navigate with the same model.
• Includes a Life/Places system for places worth revisiting, organized around experience and practical information.
• Includes a career structure for employment history, projects, reusable career materials, and applications without assuming a particular career stage.

Journal and daily planning

• Provides daily, monthly, and yearly templates with time-based navigation.
• Maintains a consistent daily-note order for schedules, daily quests, tarot, notes, agent notes, and photos.
• Supports day planning from existing schedules and recurring patterns, end-of-day reconciliation, and concise logging of meaningful outcomes.
• Can incorporate user records and previous card context when drawing today’s tarot during current-day planning.
• Creates a new analysis snapshot when the durable Profile has materially diverged from the latest snapshot instead of rewriting history.

Tasks and execution

• Separates multi-step, stateful Task Notes from one-step Task Actions.
• Provides templates, playbooks, and validators for a Base Board Task Board and Obsidian Tasks.
• Keeps recurring habits in daily quests and date-specific one-off work in Task Actions to reduce duplicate tracking.
• Supports status promotion for imminent Task Notes, completed-work review, and Archive movement.

Resumable onboarding and import

• Tracks setup progress in Inbox/Lifebase 시작 체크리스트.md, allowing onboarding to stop and resume from the first incomplete item.
• Applies and verifies one selected setup item at a time before marking it complete.
• Covers profile basics, agent behavior, Obsidian, scheduling, Tasks, sync, backup, automation, and existing-data import.
• Leaves items selected as “Later” incomplete so they remain available in a future onboarding session.
• Imports existing Obsidian vaults, Notion exports, and Markdown collections through a small preservation pilot before full migration.

Sync, backup, and attachments

• Recommends Syncthing and guides setup across the current computer, an Android phone, and additional PCs.
• Keeps Git as an optional advanced layer for reviewing Markdown and configuration history.
• Guides Restic or Backrest repository creation, encrypted backups, snapshot checks, and restore tests.
• Stores media under _attachments/images/YYYY/MM/DD/ and provides WebP and MP4 optimization with validation.
• Keeps personal attachment binaries out of Git while including the fixed tarot card images required by the bundled tarot notes.

Obsidian and AI agents

• Includes configuration for Templater, Dataview, Base Board, Tasks, Day Planner, Calendar, Periodic Notes, Custom Attachment Location, and Image Toolkit.
• Provides Lifebase-named template commands for journals, quick Task Actions, Task Notes, and scheduled maintenance.
• Leaves operating-system-specific sidebar and navigation-history shortcuts unbound by default, then applies and verifies the appropriate macOS, Windows, or Linux bindings during onboarding.
• Includes shared AGENTS.md instructions and a Claude Code import file for the installed vault.
• Provides 14 local skills covering note writing, day planning and wrap-up, daily tarot, onboarding, import, structure review, Syncthing, Restic, attachment optimization, and Task maintenance.
• Uses .agents/skills as the canonical skill source while materializing the same skills for .claude/skills.

Distribution and integrity

• Packages one stable lifebase/ vault inside Lifebase-0.1.0.zip, so users do not need to rename the extracted vault folder.
• Includes a polished English product guide for extracting the package, opening the vault, onboarding, synchronization, backup, imports, AI-agent use, and licensing.
• Displays release, product, data format, storage model, platform, and license badges at the top of the bundled README.
• Records the installed product version in the README version badge and .lifebase-version.
• Includes the proprietary license, English and Korean terms, and licenses and source notices for bundled third-party components.
• Produces a deterministic ZIP, a SHA-256 checksum, and a maintainer-only file manifest.
• Validates required files, wikilinks, filename portability, the tag registry, JSON, skill copies, and private path leakage before release.

Getting started

1. Extract Lifebase-0.1.0.zip.
2. Open the generated lifebase/ directory as an Obsidian vault.
3. Review the bundled community plugins and enable the ones you intend to use.
4. Open Inbox/Lifebase 시작 체크리스트.md, or explicitly invoke $lifebase-onboarding in an AI agent.

Notes

• Syncthing is the recommended synchronization method. Git and Restic or Backrest are optional.
• Bundled community plugins remain governed by their respective third-party licenses. Compatibility with future Obsidian or plugin versions is not guaranteed.
• Lifebase stores user-owned records in editable Markdown. Back up the current vault and review changes before applying an update.