---
url: /guide/overview/overview.md
---
import { FreeDownloadButton } from '../../../../theme/components/FreeDownloadButton';
import { CommercialContent } from '../../../../theme/components/CommercialContent';
# Get LifeOS
## Get Pro Version
### Demo Video
> Visit Youtube for more information: https://www.youtube.com/watch?v=C1Ph\_j00\_Sc
### Get Link
[LifeOS Pro Get Link](/plugin/lifeos/pricing.md)
### Usage Instructions
After purchasing LifeOS Pro, please refer to [Usage Instructions](/guide/overview/usage.md)
## Experience Basic
### Demo Video
> Visit Youtube for more information: https://www.youtube.com/watch?v=m-hD48UYRts
### How to obtain
### Usage Instructions
After downloading the Basic, please refer to [Usage Instructions](/guide/overview/usage.md)
---
url: /guide/overview/usage.md
---
# Usage
> [Basic](/guide/overview/overview.md#experience-basic) can refer to the following steps:
>
> 1. Example Vault Selection
> 2. Scenario 2
> 3. Scenario 3
After extracting the complete package, the main folders are:
```text
LifeOS Pro/
├── Example Vault/
│ ├── LifeOS Pro Memos Vault/
│ ├── LifeOS Pro Memos Blank Vault/
│ ├── LifeOS Pro IPO Vault/
│ ├── LifeOS Pro IPO Blank Vault/
│ ├── LifeOS Pro GTD Vault/
│ ├── LifeOS Pro GTD Blank Vault/
│ ├── LifeOS Pro PARA Vault/
│ ├── LifeOS Pro PARA Blank Vault/
│ ├── OPC LifeOS Vault/
│ └── OPC LifeOS Blank Vault/
└── Plugin/
```
According to your usage scenario, select one of the scenarios, and follow the steps one by one!
## Example Vault Selection
After extracting the complete package, enter `LifeOS Pro/Example Vault/`. It contains five filled examples, from easiest to hardest: `LifeOS Pro Memos Vault`, `LifeOS Pro IPO Vault`, `LifeOS Pro GTD Vault`, `LifeOS Pro PARA Vault`, and `OPC LifeOS Vault`. Each has a matching `Blank Vault` beside it for your own main vault after learning the workflow.
Choose by the bottleneck you need to remove, not by the longest feature list:
1. No stable daily capture habit; you only want bullets and tasks -> **Memos**.
2. You want the fewest categories needed to turn sources into useful output -> **IPO**.
3. Tasks are scattered; next actions and waiting-for items are unclear -> **GTD**.
4. Projects, responsibilities, and reusable knowledge all need structure -> **PARA**.
5. Products, customers, revenue, and delivery need one system -> **OPC**.
The recommended order is **Memos -> IPO -> GTD -> PARA -> OPC**, from lowest to
highest upkeep. It is not a mandatory migration path: start with the simplest
structure that solves the current problem, or skip ahead when the need is clear.
Templates share Markdown, periodic notes, and task syntax, but they are not
one-click skins. Memos can keep every old daily note while growing into IPO,
GTD, or PARA. Conversions among those three require reviewed reclassification.
OPC normally starts in its Blank Vault and receives selected material. Never
overwrite working settings with a Blank Vault's `.lifeos/settings.json`. See
[Upgrade from Memos](/guide/example-vaults/memos.md#upgrade-from-memos).
After installing the LifeOS Skill, an agent can run the migration. For example:
```text
Migrate this vault from GTD to PARA. Move only historical material that is useful now.
Show the folder and settings-field diff first. Do not overwrite settings or move files yet.
```
The agent records the scope, preserves periodic notes and custom templates,
merges only confirmed structural settings, and proposes destinations in bounded
batches. Files stay in place when links, attachment ownership, or name
collisions are unsafe. The profile manifest changes only after target entry
points, task queries, and links have been checked.
### LifeOS Pro PARA Vault
A complete [CODE](/guide/intro/second-brain.md#code-model)/[PARA](/guide/intro/second-brain.md#para-organization) practice for users who already need to manage projects, ongoing responsibilities, and reusable knowledge together. Start with Memos instead when daily capture is not stable yet.
### LifeOS Pro IPO Vault
In knowledge management, IPO typically refers to the process of Input, Processing, and Output. This model describes the entire journey of knowledge from acquisition and processing to application.
In the IPO model:
1. **Input**: This marks the starting point of knowledge management, involving the collection and acquisition of information. Input can include data, documents, research, personal experiences, external information, etc. The quality of input is crucial to the entire knowledge management process.
2. **Processing**: At this stage, the input information is analyzed and refined to make it useful and applicable. Processing activities may include analysis, synthesis, evaluation, interpretation, storage, and sharing of knowledge. The goal of this phase is to transform raw data and information into valuable knowledge.
3. **Output**: This is the final stage of knowledge management, where processed knowledge is applied to real-world problems to create value. Output can include decisions, solutions, new products, improved processes, training materials, etc.
Can be simply understood as a simplified version of the [CODE](/guide/intro/second-brain.md#code-model)/[PARA](/guide/intro/second-brain.md#para-organization) practice, it greatly reduces the entry threshold for beginners. Users only need to focus on input, output, and themes, and easily record, organize, and use notes.
At the same time, you can also base this on it to design your own note system and workflow without PARA, which is a very imaginative feature!
### LifeOS Pro GTD Vault
GTD is better for users who want the vault to answer "what is the next action?" before anything else. It keeps the project concept, but separates execution into inbox, next actions, waiting-for items, someday/maybe, reviews, and archive.
Choose this vault when:
1. Your day contains many small tasks, follow-ups, and delegated items.
2. You want to stabilize the task system first, then grow the knowledge base later.
3. You already understand the GTD Capture → Clarify → Organize → Engage → Review loop and want to use it directly in LifeOS.
The GTD vault uses tags such as `#gtd/next`, `#gtd/waiting`, `#gtd/someday`, and `#ctx/*`. Project notes remain the source of truth; action pages aggregate what should be done or followed up now.
### OPC LifeOS Vault
Best for one-person companies, side businesses, consulting services, or indie products. It organizes operations through a CEO dashboard, seven departments, input/output pipelines, and `.AI.md` pages.
### LifeOS Pro Memos Vault
Recommended for Logseq, flomo, and usememos users. It enables periodic notes only and disables PARA and theme notes by default. The filled version demonstrates bullets, tasks, and review with two daily notes and one weekly note; the daily template stays empty while weekly-to-yearly templates keep task and record queries.
After learning, open `LifeOS Pro Memos Blank Vault` as your own main vault instead of clearing the example.
## Scenario 1: Upgrade from LifeOS to LifeOS Pro
If you have used the Basic, simply enable the new plugin in the existing repository, PRO version is compatible with all functions of the Basic:
1. Copy the 'plugin/lifeos-pro' directory to the ' .obsidian/plugins' directory
:::warning
.obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method
1. MacBook: Use the shortcut key Command + Shift + .
2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders
:::
2. Copy the existing LifeOS configuration file from ' .obsidian/plugins/periodic-para/data.json' to ' .obsidian/plugins/lifeos-pro/data.json'
3. Find the Basic LifeOS plugin in the third-party plugin list and disable it first to avoid conflicts caused by running LifeOS and LifeOS Pro at the same time
4. Find LifeOS Pro in the third-party plugin list and enable it
* Open the LifeOS Pro plugin configuration page in the 'third-party plugin'
5. Click the 'activate upgrade' panel, input the email and activation code (usually in the email you received), and click the 'upgrade now' button at the bottom to upgrade to the latest version of the plugin
6. Restart Obsidian
7. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience
8. Go to [Pro Version](/guide/pro/distinct-with-free.md) to view more usage instructions
## Scenario 2: Use Existing Example Repository
1. Open Obsidian, choose "Open local repository", enter the extracted `LifeOS Pro/Example Vault/` folder, and use the Memos -> IPO -> GTD -> PARA -> OPC easiest-to-hardest order to open one of the five filled examples: `LifeOS Pro Memos Vault`, `LifeOS Pro IPO Vault`, `LifeOS Pro GTD Vault`, `LifeOS Pro PARA Vault`, or `OPC LifeOS Vault`. Remember to select "Trust repository author and enable plugins".
2. Open the LifeOS Pro plugin configuration page in the 'third-party plugin'
4. Restart Obsidian
5. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience
6. Go to [Pro Version](/guide/pro/distinct-with-free.md) to view more usage instructions
After learning the workflow, do not manually erase the sample content. Open the matching `LifeOS Pro Memos Blank Vault`, `LifeOS Pro IPO Blank Vault`, `LifeOS Pro GTD Blank Vault`, `LifeOS Pro PARA Blank Vault`, or `OPC LifeOS Blank Vault` as your own main vault. Blank vaults do not duplicate plugin binaries; if the plugins are not installed yet, copy them from the complete package's top-level `Plugin/` folder into `.obsidian/plugins/`.
## Scenario 3: Use LifeOS Pro in an Existing Repository
1. Copy `.obsidian/plugins/lifeos-pro` from any LifeOS Pro example vault to the `.obsidian/plugins` directory of your existing repository
:::warning
.obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method
1. MacBook: Use the shortcut key Command + Shift + .
2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders
:::
2. Find LifeOS Pro in the third-party plugin list and enable it
3. Prefer opening the matching `Blank Vault` as a new main vault. If you must merge with an existing repository, copy `.lifeos`, templates, and the folder structure from the selected blank vault. PARA, IPO, GTD, and OPC use different structures, so choose only one instead of mixing them together.
4. If you did not copy the full `.obsidian` settings, make sure the community plugins used by that example vault are installed and enabled. The GTD vault mainly relies on Tasks queries; older templates may still use Dataview or Templater.
5. Open the LifeOS Pro plugin configuration page in the 'third-party plugin'
6. Click the 'activate upgrade' panel, input the email and activation code (usually in the email you received), and click the 'upgrade now' button at the bottom to upgrade to the latest version of the plugin
7. Restart Obsidian
8. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience
9. Go to [Pro Version](/guide/pro/distinct-with-free.md) to view more usage instructions
## Read next after setup
After installation, plugin activation, and the example vault check are done, read these case studies. They are not extra setup steps. They show how to use LifeOS Pro in daily work, projects, research, and reviews.
* [A Day with Obsidian LifeOS](/case/daily-workflow.md) — plan the morning, execute during the day, and close the loop
* [Manage a Full Project with LifeOS Pro](/case/project-management.md) — use theme notes to hold project context
* [A Research Workflow with Obsidian LifeOS](/case/research-workflow.md) — collect sources and turn them into output
* [Make Obsidian Notes Askable with DeepAsk](/case/ai-powered-notes.md) — connect AI after your notes are already working
* [Run a Useful Weekly Review with LifeOS](/case/weekly-review.md) — bring daily notes, tasks, and projects back together
# Next Step
Expand the left 'knowledge base directory', continue to read the current manual!
# Reference Material
## How to Migrate to LifeOS/Obsidian
See [How to Migrate to LifeOS/Obsidian](/guide/migrate/index.md).
## Main System and Sub System of LifeOS
See [Main System](/guide/core/main-system.md) and [Sub System](/guide/core/sub-system.md).
---
url: /guide/intro/obsidian.md
---
# What is Obsidian
It introduces itself on the official website as follows:
* [Obsidian](https://obsidian.md/) is the private and flexible note‑taking app that adapts to the way you think.
LifeOS uses Obsidian as its implementation tool, mainly to leverage its powerful customization abilities and rich plugin ecosystem!
Obsidian is a private and flexible note-taking application that adapts to your thinking patterns, as described on its official website. It is a Markdown-based note-taking software with several distinctive advantages that make it stand out among other note-taking tools:
## Markdown Support
* Uses plain text format, making files lightweight and portable
* Grants full control over Markdown file management
## Local Storage
* Saves notes locally, ensuring data privacy and maximum security
* Fully functional offline
## Powerful Linking Capabilities
* Supports bidirectional linking to create network-like note structures
* Includes graph view to visualize connections between notes
## Plugin System
* Extensible via community-driven plugins (calendar, task management, etc.)
* Supports custom scripting for advanced users
## High Customizability
* Custom themes via CSS modification
* Configurable workspaces for different needs
## Efficiency
* Fast performance due to local storage
* Extensive keyboard shortcuts for quick operations
## Free Core Features
* The basic version is free for personal use, it's a great choice for those who want to manage their notes and tasks without spending money.
LifeOS adopts Obsidian as its foundation specifically to leverage its powerful customization and rich plugin ecosystem for building comprehensive personal productivity systems.
:::info
If you like VSCode, you'll probably like Obsidian too—the difference is VSCode is for coding while Obsidian is for note-taking.
:::
:::tip On your phone: try Aino Mobile
While using Obsidian + LifeOS on your desktop, you do not need the Obsidian mobile app. **Aino Mobile** (iOS / Android) opens your Obsidian vault directly — quick capture, inbox collection, calendar and tasks, plus AI answers, all compatible with the LifeOS workflow.
→ [Get Aino Mobile](https://aino.md/download/)
:::
---
url: /guide/intro/life-os.md
---
# What is LifeOS
Obsidian LifeOS is a life management system built on Obsidian—a simple, effective, and user-friendly Obsidian template ready to use out of the box!
Most Obsidian templates overwhelm beginners by installing dozens of community plugins and exposing their complex functionalities all at once. This forces new users to painstakingly learn each plugin's usage, leaving them little time to focus on actually taking notes.
LifeOS takes a different approach by creating a dedicated plugin specifically for its template! With this plugin, you don’t need any programming knowledge—simple visual clicks allow you to effortlessly create periodic notes and PARA notes. Just read through the LifeOS tutorial, and you'll quickly master the template.
## LifeOS Core Features
### 📦 Ready-to-Use
Download the example repository and start using immediately without complex configuration
### 😄 Effortless Journaling
Record bullet notes effortlessly in a diary, and combine with usememos for quick mobile recording
### 🤖 Quick Retrieval
Provide indexing functionality to help you quickly retrieve scattered files, tasks, and bullet notes
### 📇 Periodic Notes
Easily manage tasks, goals, and time with periodic notes
### 🧠 Knowledge Management
Provide the best PARA practice under Obsidian, aiming to be your second brain
### 🔌 Dedicated Plugins
Comes with dedicated plugins for visual creation of PARA notes and periodic notes, convenient and quick
### 📅 Schedule Planning (Pro)
Simply drag and drop to schedule tasks on the big calendar. Support subscribing to remote calendars for centralized management
### 📒 Theme Mode (Pro)
Supports creating your own note system and workflow independently of PARA
### 📝 Advanced List (Pro)
The advanced list indexing feature supports search, sorting, and filtering, making it easy to find scattered files, tasks, and bullet notes
## Summary
💡 LifeOS is not just an Obsidian template; it's more like a comprehensive personal Obsidian productivity system ⚙️. Whether it's for your personal life 🏠 or for work 💼, effective recording and management can be accomplished within this Obsidian framework.
🗂️ It's based on the PARA knowledge management system, categorizing all content into projects, areas, resources, and archives, making management both scientific and efficient.
📅 Additionally, LifeOS includes a periodic notes arrangement, such as annual notes, quarterly notes, monthly notes, weekly notes, and daily daily notes, meticulously planning and tracking everything from long-term goals to daily tasks 🔍.
Such a template acts like installing a smart brain 🧠 into your Obsidian, helping you better capture ideas, achieve self-awareness, and ensure that every moment of focus is worthwhile.
---
url: /guide/intro/second-brain.md
---
# What is a Second Brain
## First Brain vs Second Brain
The first brain is our actual brain, which, as long as we are alive, is constantly working, performing tasks such as knowledge management, task management, goal management, and more. Most of the time, we can't multitask effectively, so the first brain is more like a CPU, with various types of tasks competing for CPU cycles. When there are too many tasks to handle, the brain becomes overwhelmed because it has to process current tasks while maintaining the context for other tasks for switching between them. This makes it hard for us to focus on executing the current task, and at that point, we need an external system to assist the first brain. This is where the second brain comes in.
The second brain is an external system. If the first brain is likened to a CPU, then the second brain is more like a storage system. It serves as a cache between the first brain and the real world, reducing the first brain's load and allowing it to focus on the current task. It can be compared to memory and hard disk, except that memory communicates with the CPU (first brain) more frequently and with faster read speeds. This storage system holds the things that the first brain does not need to be constantly aware of. Of course, these things must be deliberated by the first brain to decide whether they are worth storing, and the content can be records, to-dos, processes, with the medium being text, images, videos.
For example, when using a second brain for task management, we store important and urgent tasks in memory and less important, not urgent ones on the hard disk; this week's tasks in memory, and this month's tasks probably on the hard disk. Thus, by leveraging the second brain, we can focus on the present without stress and switch contexts when necessary.
You can call it a second brain, but from different perspectives, I can also call it "LifeOS," because I record everything on it, living and working; I can also call it "Programmable Personal Productivity System," I've written a lot of code on it for querying and automation, and it’s also the productivity system I use to manage tasks and goals; it even resembles a "Monorepo Project," where each folder is a project, and the README.md in each project describes the current project's meta-information like a Package.json.
## The CODE Model
The CODE model was proposed by time-management coach Tiago Forte in ["Building a Second Brain"](https://www.buildingasecondbrain.com/book) and stands for four steps: Capture, Organize, Distill, and Express.
CODE represents four core steps:
* Capture
* Organize
* Distill
* Express
Here is an overview of each step of the CODE model:
### Capture
This step refers to the process of seizing inspiration and information. When you receive any information or idea, you should record it quickly for subsequent processing. The purpose of capture is to reduce the memory burden on the brain.
### Organize
After capture, the next step is to systematically organize the information. By classifying, sorting, and archiving, you can ensure that each piece of information is saved in an easily retrievable place. The specific practice is the well-known [PARA organization method](/guide/intro/second-brain.md#the-para-method).
### Distill
The distillation process involves summarizing and condensing information, retaining only the most valuable insights and data. This usually means simplifying information to the core points for quick digestion and review.
### Express
The final step is transforming your thoughts and learning into an external form, such as writing, teaching, or creating some form of work. By expressing, you not only integrate and consolidate your knowledge, but you can also share with others and receive feedback.
Tiago Forte's underlying idea is that by externalizing and appropriately managing your knowledge, you can use information more efficiently, create value, and improve personal and professional efficiency. This model is particularly suitable for today's information overload digital age, emphasizing not only the collection of information but also the active processing and utilization of this information.
## The PARA Method
The [PARA](https://fortelabs.com/blog/para/) method is a personal knowledge management system created by time-management coach Tiago Forte.
PARA stands for four core categories:
* Projects
* Areas
* Resources
* Archives
This system is dedicated to helping people organize digital information, such as documents, notes, and files, making it more efficiently accessible and usable.
### Projects
* Definition: A project is a series of tasks with specific outcomes and deadlines.
* Features: Projects are short-term, dynamic, and change over time.
* Examples: Writing reports, organizing events.
### Areas
* Definition: Areas are parts of life that require ongoing maintenance and for which you are responsible.
* Features: Areas are relatively stable, requiring regular review and updates but lacking a specific end time.
* Examples: Health, finances, personal development.
### Resources
* Definition: Resources are collections of information and knowledge about specific topics or interests.
* Features: Resources may support projects or areas but are not directly linked to specific activities or responsibilities.
* Examples: Summaries of books, research materials, educational courses.
### Archives
* Definition: Archives are projects, areas, and resources that are no longer active or currently needed.
* Features: Archives store infrequently used information but are always ready for retrieval.
* Examples: Documents from completed projects, outdated resources.
**Benefits of Using PARA**
* **Reduces decision fatigue**: Clear categories simplify decisions about how to organize and access information.
* **Increases efficiency**: Systematizing information by category allows for faster retrieval of what you need.
* **Supports personal and professional development**: Projects and areas drive goals and personal growth, while resources and archives support these efforts.
**Steps to Implement PARA**
1. **Review existing information**: Check your existing notes, files, and materials.
2. **Categorize**: Classify information according to PARA's four categories.
3. **Maintain**: Regularly review projects and areas to ensure information is active and relevant.
4. **Migrate**: Move inactive information to archives.
The PARA method can be applied to different platforms and tools, such as note applications (e.g., Obsidian, Evernote, Notion), document storage services (e.g., Google Drive, Dropbox), etc. The key is to establish an organizational system that fits these four categories.
---
url: /guide/beginner-guide/pre-knowledge.md
---
# Prerequisites
## Markdown Syntax
Obsidian is a bi-directional linking note-taking software based on Markdown files, so you must understand the basic syntax of Markdown! Additionally, beyond the basic Markdown syntax, Obsidian has extended some special Obsidian-style syntax!
Here's a brief introduction to the syntax you need to know to get started with LifeOS. If you need to learn more, please refer to:
* [Basic Markdown Syntax](https://www.markdownguide.org/basic-syntax/)
* [Obsidian Flavored Markdown Syntax](https://help.obsidian.md/obsidian-flavored-markdown)
### Lists
The syntax for lists is very simple. In any Markdown file, by typing a list identifier followed by a space, you create a list. List identifiers can be hyphens (-), asterisks (\*), or plus signs (+), or even numbers (1.).
In LifeOS, list syntax is typically used to create "Theme Fleeting Notes." We recommend using hyphens (-), as shown in the example below:
```markdown
- Today the weather is nice and clear
- Beautiful scenery everywhere
- Lists can also be indented, just press the tab key
```
[Learn more](https://www.markdownguide.org/basic-syntax/#lists-1)
### Tasks
The task syntax is very similar to the list syntax. We just need to input a space and brackets after the list identifier, as shown in the example below:
```markdown
- [x] Go out to buy groceries
- [ ] Update information
- [ ] Contact parents
```
[Learn more](https://www.markdownguide.org/extended-syntax/#task-lists)
### Bi-directional Links
Type two consecutive left brackets to trigger the bi-directional link syntax, as shown in the example below:
```markdown
[[File name]]
```
If you need to display the file content, add a ! before \[\[, as shown in the example below:
```markdown
![[File name]]
```
If you need to reference a specific block of content in a file, you can use the blockid syntax, as shown in the example below:
```markdown
![[File name#^id]]
```
Recommended plugin for easily copying file blocks as !\[\[File name#^id]]: [Copy Block Link](https://github.com/mgmeyers/obsidian-copy-block-link)
[Learn more](https://help.obsidian.md/links)
## Obsidian Operations
### What is a Vault?
**A vault is Obsidian's core working unit**, equivalent to a **dedicated knowledge repository**. Each vault can have customized plugins, themes, and shortcuts to meet the needs of different scenarios (such as learning, project management, writing), and LifeOS provides an example vault! In general, you only need one vault, which is the LifeOS vault.
### What are Plugins?
**Plugins are Obsidian's functional extension modules**, giving the note-taking tool more flexibility and productivity. Obsidian provides **core plugins** (basic functions), third-party developers contribute **community plugins** (advanced functions), and LifeOS, in addition to providing an example vault, also provides a plugin of the same name, LifeOS. With this plugin, LifeOS has many enhanced features, such as advanced lists, home view, big calendar, and more.
### Is LifeOS a Vault or a Plugin?
LifeOS is a life management system built on Obsidian. It is a simple, effective, and user-friendly example vault, and it also has a dedicated plugin, also called LifeOS, which allows the author to provide enhanced functionality for the LifeOS example vault through programming!
### How to Open the LifeOS Example Vault?
Open the Obsidian software, click on the switch vault button in the bottom left corner, then click "Manage vaults"
After entering the page below, select "Open" local repository
Find the directory where the LifeOS example vault is located and open it as a vault
---
url: /guide/beginner-guide/core-concept.md
---
# Core Concepts
> Read this Core Concepts guide all the way through because it is the key to the whole LifeOS system: you do not need perfect folders on day one. Use pressure-free capture, then easy retrieval through theme tags and indexes.
## Theme Tags
When creating a theme note through the "Theme Notes" form, the first thing you need to input is the "Theme Tag," which serves as the unique identifier for the theme note and runs throughout the entire LifeOS!
Its main function is to index tasks, fleeting notes, and files under a specific theme. Please observe the following images. Tasks, fleeting notes, and files recorded anywhere, as long as they are tagged with the corresponding theme note's "Theme Tag," will be included in the index file of the "Theme Note." It is this "automatic inclusion" function that allows you to truly achieve "pressure-free recording." Whenever you record a "task" and "fleeting note" in a periodic note, such as a daily note, as long as you add the corresponding "Theme Tag," it will be included! In the future, you can view these records in the "Theme Index File," which makes it very convenient to "retrieve" your recorded "fragment notes." Easy "retrieval" enables "pressure-free recording"!
Similarly, any non-periodic note file, as long as the "Theme Tag" appears in its main text, can also be included in the index file of the "Theme Note":
## Note Templates
In Obsidian, templates are pre-defined note templates that can be used to quickly create notes with fixed formats. Templates typically include a fixed structure and content, and can include placeholders, variables, and dynamic content. This is particularly useful for repetitive work or commonly used note formats.
For example, the daily note template in the LifeOS Pro example vault has the following format. The example below uses the Pro built-in template syntax; community / open-source LifeOS still uses the legacy Templater syntax. See [Template Syntax](/guide/beginner-guide/template-syntax.md) for the compatibility table.
````markdown
## Project List
%%Today's snapshot of projects%%
{{snapshot:Project}}
## Daily Records
%%Your records%%
## Habit Tracking
%%Check-ins will not be counted as tasks%%
- [ ] Glass of water upon waking up
- [ ] Breakfast
- Water - [ ] +1 - [ ] +1 - [ ] +1 - [ ] +1 - [ ] +1 - [ ] +1
- [ ] Original English
- [ ] Project time statistics
- Take a break - [ ] +1 - [ ] +1 - [ ] +1
- Standing desk - [ ] +1 - [ ] +1 - [ ] +1 - [ ] +1
- [ ] Record expenses
## Energy Allocation
%%Today's project list, automatically calculates project time proportion based on time spent%%
```LifeOS
ProjectListByTime
```
## Completed Today
%%List of tasks completed today, extracted from all notes%%
```LifeOS
TaskDoneListByTime
```
````
This way, the daily notes created each day have the same format and are pre-filled with most modules, such as project list, daily records, habit tracking, energy allocation, tasks completed today, and other modules!
Similarly, weekly notes, monthly notes, quarterly notes, and yearly notes also have their own templates, which are stored by default in the "0. Periodic Notes/Templates" directory. You can change their storage location in the LifeOS plugin settings.
In addition, theme notes (PARA notes) also have their own templates, which are stored by default in the Template file in the corresponding directory, such as "1. Projects/Template", "2. Areas/Template", "3. Resources/Template", "4. Archives/Template". You can also change their storage location in the LifeOS plugin settings. When creating theme notes, these templates are used to create "Theme Index" notes. For example, the "Project Template" in the LifeOS example vault has the following format:
````markdown
%%Set project deadline and result description%%
- [ ] #{{tags}} Deadline 📅 {{date+7:YYYY-MM-DD}}
- Result Description
## Tasks
%%Query tasks based on the tags field in the current file's [Properties](https://help.obsidian.md/Editing+and+formatting/Properties), extracted from all notes%%
```LifeOS
TaskListByTag
```
## Lists
%%Query bullet lists based on the tags field in the current file's [Properties](https://help.obsidian.md/Editing+and+formatting/Properties), extracted from all notes%%
```LifeOS
BulletListByTag
```
## Files
%%Query file lists based on the tags field in the current file's [Properties](https://help.obsidian.md/Editing+and+formatting/Properties), extracted from all notes%%
```LifeOS
FileListByTag
```
````
In this way, each theme note's index can index "Tasks", "Lists", and "Files" under their respective "Theme Tags"!
Whether it's periodic note templates or theme note templates, you can modify them based on the default templates according to your own needs, so the notes created will better meet your individual requirements!
## Note System
LifeOS's core adopts two systems: one is the theme note system, and the other is the periodic note system. The former generally uses the PARA organizational method, managing knowledge by dimensions such as "Projects", "Areas", "Resources", while the latter uses time as a dimension, managing tasks/goals/time through recording "Daily Notes", "Weekly Notes", "Monthly Notes", "Quarterly Notes", "Yearly Notes".
### Periodic Note System
#### Long-term Notes
From Figure 1, we can also discover that for the periodic note system, from "Long-term Notes", to "Short-term Notes", to "Daily Notes", the predictability of "Periodic Notes" gets higher and higher. How to understand predictability? For example, compared to planning a year in "Yearly Notes" and what needs to be done in the next week in "Weekly Notes", the latter obviously has more predictability!
Therefore, in "Long-term Notes", due to low predictability, it is more suitable for "Goal Management"!
Although we don't know the specific tasks needed for "This Year" or "This Quarter", we can work top-down, focusing on long-term goals, i.e., setting goals for this "time period" in "Yearly Notes" and "Quarterly Notes", which keeps us maintaining a sense of direction!
##### Long-term Notes Example
#### Short-term Notes
With clear goals, naturally, in "Monthly Notes" and "Weekly Notes", we can break down the goals set in "Yearly Notes" and "Quarterly Notes", i.e., bottom-up, focusing on short-term "Task Management"!
The specific approach is to open "Yearly Notes" and "Quarterly Notes" at the beginning of each week and month, and plan the tasks for "This Week" and "This Month" according to your set goals!
##### Short-term Notes Example
#### Daily Notes
Daily notes are "Daily Records". I usually use them to:
1. Record anytime, anywhere, so that they can be indexed by "tags" in the "Knowledge Management" "\*.README.md"
2. Capture ideas and insights, achieving self-awareness
3. Track project time, ensuring focus on projects
##### Daily Notes Example
### Theme Note System
From Figure 1, we can find that for the theme note system, from "Archives", to "Resources", to "Areas", to "Projects", the operability of "Knowledge Notes" gets higher and higher. How to understand operability? For example, compared to what to do next in the "Parenting" area and what to do next in the "Parenting-Organizing Full Month Celebration" project, the latter obviously has more operability!
#### Theme Note System Example
#### Tags vs. Folders?
We already have "[Theme Tags](/guide/beginner-guide/core-concept.md#theme-tags)" as the unique index, so why not just create a single index file for each theme? Why do we still need "Folders"?
We often hear debates about whether to use "Tags" or "Folders" in note-taking software. I believe this is not a "choose only one" issue. The correct understanding should be "Tags are great, but we need to allow for the existence of folders." How to understand this?
**Example🌰:**
1. Common scenario for tags: In periodic notes, I can casually record a task or fleeting thought, and as long as I add a "Theme Tag", I can find this record in the corresponding theme index file. Given that tasks or fleeting thoughts are often just a few sentences, and the frequency of writing is high, this operation is much more efficient than creating a note file in a folder and then recording it there!
2. Common scenario for folders: In the theme note folder, I need to write a medium to long document, such as a research report, meeting minutes, or annual summary. Then I create a note in the folder. These types of notes often require you to invest more energy in writing, some lasting for an hour or two, some for a day or two. Given the length of medium to long documents and the lower frequency of writing, maintaining them in the form of folders and files is more appropriate!
So, under LifeOS, we need to flexibly use tags or folders according to the length of the notes. The principle is "short tasks and fleeting thoughts use tags, medium to long documents use files."
#### Tags vs. Theme Tags?
Theme notes are uniquely identified by "[Theme Tags](/guide/beginner-guide/core-concept.md#theme-tags)", but "Tags" are not necessarily theme notes. In LifeOS, tags have the following uses, such as:
These tags make it convenient for you to search and view in the future, and may also be potential "Theme Notes". For example, you can create a theme for "#Festival", and all records about festivals will be indexed by this theme!
### Relationship between Theme Notes and Periodic Notes
Refer to the diagram of "[Theme Tags](/guide/beginner-guide/core-concept.md#theme-tags)". Simply put, "Theme Notes" are used to index your "Fleeting Thoughts", "Tasks", and "Files" of "a certain theme" scattered in "Periodic Notes".
### Theme Notes vs. CODE/PARA
Refer to "[Template Selection](/guide/overview/usage.md#example-template-selection)". Simply put, PARA/CODE is just a special form of theme notes. You can use theme notes to create workflows other than "PARA/CODE" ([Custom Workflow](/guide/best-practice/custom-workflow.md)).
## Summary
These two systems create two contexts, keeping me focused:
* Time-based periodic note system: at certain time points, work based on the corresponding periodic notes. The notes contain enough context to perform time-dimension-related "Task Management", "Goal Management", and "Time Management";
* Theme-based PARA note system: when I want to investigate a certain theme, work based on the corresponding theme index (\*.README.md). The notes have already collected considerable context, allowing for theme-dimension-related "Knowledge Management";
---
url: /guide/beginner-guide/template-syntax.md
---
# Template Syntax
LifeOS currently has two template syntaxes. Choose the one that matches your version:
* **LifeOS Pro / Aino LifeOS**: use the built-in syntax, such as `{{snapshot:Project}}`, `{{date}}`, and `{{tags}}`. This syntax does not require Templater.
* **Community / open-source LifeOS**: only supports the legacy Templater syntax, such as `<% LifeOS.Project.snapshot() %>`. If you use the open-source version, do not replace those templates with the new syntax.
## Basic Variables
These variables work in periodic note templates and theme note templates:
| Variable | Description |
| ------------------------------------------- | ------------------------------------------------------------------------ |
| `{{date}}` | The note date, formatted as `YYYY-MM-DD` |
| `{{date:FORMAT}}` | Format the note date with Day.js, for example `{{date:YYYY-MM-DD dddd}}` |
| `{{date+N:FORMAT}}` / `{{date-N:FORMAT}}` | Offset the note date by N days |
| `{{monday:FORMAT}}` ... `{{sunday:FORMAT}}` | Date for a weekday in the current week, useful for embedding daily notes |
| `{{time}}` | Current time, formatted as `HH:mm` |
| `{{time:FORMAT}}` | Format the current time with Day.js |
| `{{title}}` / `{{filename}}` | New note filename without `.md` |
| `{{year}}` / `{{month}}` / `{{day}}` | Year, month, and day |
| `{{week}}` / `{{weekYear}}` | Week number and week year |
| `{{quarter}}` | Quarter, such as `Q1` |
| `{{periodType}}` | Period type: `Daily`, `Weekly`, `Monthly`, `Quarterly`, `Yearly` |
| `{{tags}}` | Theme tag passed when creating a theme note, without the leading `#` |
## Weekday Date Variables
In weekly note templates, use `{{monday:FORMAT}}` through `{{sunday:FORMAT}}` to reference each day in the current week. Chinese locales default to Monday-start weeks; other locales default to Sunday-start weeks. A custom week-start setting takes precedence.
For example, if your daily note filename is `YYYY-MM-DD`:
```markdown
![[{{monday:YYYY-MM-DD}}]]
![[{{tuesday:YYYY-MM-DD}}]]
![[{{wednesday:YYYY-MM-DD}}]]
![[{{thursday:YYYY-MM-DD}}]]
![[{{friday:YYYY-MM-DD}}]]
![[{{saturday:YYYY-MM-DD}}]]
![[{{sunday:YYYY-MM-DD}}]]
```
If your daily note filename is `YYYYMMDD dddd`, you can write:
```markdown
![[{{sunday:YYYYMMDD dddd}}]]
```
## Snapshot Variables
LifeOS Pro snapshot variables use this syntax:
```markdown
{{snapshot:Project}}
{{snapshot:Area}}
{{snapshot:Resource}}
{{snapshot:Archive}}
{{snapshot:Theme}}
```
They generate a numbered list of theme index files under the matching folder. For example, `{{snapshot:Project}}` scans the project folder, finds each project's index file, and generates:
```markdown
1. [[1. Projects/Project A/README|Project A]]
2. [[1. Projects/Project B/README|Project B]]
```
If you use the `*.README.md` index mode, LifeOS Pro follows your current setting when resolving index files.
## Conditional Blocks
You can render different content for weekdays and weekends:
```markdown
{{if weekday}}
## Workday Plan
- [ ] Handle today's focus task
{{else}}
## Weekend Review
- [ ] Do a light review
{{endif}}
```
`weekday` means Monday through Friday. Saturday and Sunday use the `{{else}}` branch. If there is no `{{else}}`, weekends render empty content.
## Periodic Note Example
```markdown
## Project List
{{snapshot:Project}}
## Daily Records
%%Your records%%
## Tomorrow
{{date+1:YYYY-MM-DD}}
```
## Theme Note Example
When creating a theme note, `{{tags}}` is replaced with the current theme tag. When writing it as an inline tag, add `#` yourself:
````markdown
---
tags:
- { { tags } }
---
## Tasks
- [ ] #{{tags}} Deadline 📅 {{date+7:YYYY-MM-DD}}
```LifeOS
TaskListByTag
```
````
## Community / Open-Source Compatibility
Community / open-source LifeOS relies on Templater and only supports the legacy syntax:
```markdown
<% LifeOS.Project.snapshot() %>
<% LifeOS.Area.snapshot() %>
<% LifeOS.Resource.snapshot() %>
<% LifeOS.Archive.snapshot() %>
```
Theme tags still use Templater frontmatter variables:
```markdown
#<% tp.frontmatter.tags %>
```
If you maintain an open-source vault or an older example vault, keep using this legacy syntax and make sure Templater has `Trigger Templater on new file creation` enabled.
## Migration Safety Rules
When using the "Review & Safely Migrate" feature to convert old templates to the new syntax:
* **Automatic migration only applies to templates without residual scripts**. If your template only contains recognized legacy patterns such as `tp.date.now`, `tp.frontmatter.tags`, `tp.file.title`, or `snapshot()`, the migration will complete automatically.
* **Templates containing custom JavaScript scripts will NOT be modified automatically**. If your template includes custom Templater scripts such as `<%* let ... %>`, `<% if ... %>`, or `tp.user.*`, the system will not write to the file, preventing damage to your custom logic.
* **Re-check any time from the Settings page**. Open Settings → Periodic Notes or Theme Notes tab, click the "!" button, and select "Review & Safely Migrate" to re-scan the latest template state.
* **Conditional directives remain in the template source**. Seeing `{{if weekday}}`, `{{else}}`, and `{{endif}}` in `Templates/Daily.md` is expected. A generated dated note should contain only the selected content branch and none of those directives.
* **Manual migration suggestions**: Replace an old `.weekday()` script with `{{if weekday}}...{{else}}...{{endif}}` only after confirming that the old script means Monday through Friday. Moment's `.weekday()` depends on the locale's first day of the week, so LifeOS does not guess this conversion. Keep Templater or manually rewrite any other complex scripts before migrating.
---
url: /guide/quick-start/getting-started.md
---
# Start LifeOS in 10 Minutes
If you are new to LifeOS, do not start by configuring everything from scratch. Open the prepared example vault first, follow the 4 steps below, and learn the workflow by seeing it work.
This example vault uses the basic LifeOS plugin and is meant for practicing the record, theme, and task workflow in Obsidian.
> After the example vault works, read [Core Concepts](/guide/beginner-guide/core-concept.md) all the way through. It is the key to understanding LifeOS: pressure-free capture, then easy retrieval through theme tags and indexes.
## Step 1: Download the Example Vault
Download the basic example vault:
* [GitHub: basic example vault main.zip](https://github.com/quanru/obsidian-example-lifeos/archive/refs/heads/main.zip)
After unzipping it, open the actual vault folder. It is usually named `obsidian-example-lifeos-main`, and it should contain the `.obsidian` settings folder.
## Step 2: Open It in Obsidian
1. Open Obsidian.
2. Choose "Open folder as vault".
3. Select the extracted `obsidian-example-lifeos-main` folder.
4. If Obsidian asks whether you trust the vault, confirm the source before enabling community plugins.
If you are unsure which folder to select, see [Download Vault](/guide/quick-start/download-vault.md).
## Step 3: Practice 3 Actions First
Do not read every concept before trying the workflow. Do these 3 actions first:
1. Open today's daily note and write one record.
2. Open or create a project / theme note and see how related tasks are collected.
3. Open the task or index view and confirm that the task can be retrieved.
Once these work, you have understood the core LifeOS loop: **capture -> connect to a theme -> review and move forward**.
## Step 4: Choose Your Next Step
* Want to stay with free features first? Read [Basic Feature Overview](/guide/quick-start/free-feature-overview.md).
* Already using Pro? Read [Pro Version Feature Overview](/guide/quick-start/pro-feature-overview.md).
* Want to migrate your own Obsidian vault? Read [manual setup and folder structure](/guide/quick-start/how-start.md).
Practicing with the example vault first is more reliable than configuring your own vault on day one. Move your real notes only after each module makes sense.
---
url: /guide/quick-start/download-vault.md
---
# Download the Example Vault
This is the recommended starting point for new users: download the example vault, open it in Obsidian, and see how records, themes, and tasks flow through LifeOS.
This vault uses the basic LifeOS plugin and contains Obsidian `.obsidian` settings.
## Download Links
Download the basic example vault:
* [GitHub: basic example vault main.zip](https://github.com/quanru/obsidian-example-lifeos/archive/refs/heads/main.zip)
After unzipping it, select the actual vault folder. It is usually named `obsidian-example-lifeos-main`, and it should contain the `.obsidian` folder.
## Open It in Obsidian
***
***
After opening the vault, return to [Start LifeOS in 10 Minutes](/guide/quick-start/getting-started.md) and complete the first practice flow.
---
url: /guide/quick-start/free-feature-overview.md
---
import { FreeDownloadButton } from '../../../../theme/components/FreeDownloadButton';
# Basic Feature Overview
All features in the Basic are completely free!
> Visit Youtube for more information: https://www.youtube.com/watch?v=m-hD48UYRts
## Visual Note Creation
In the form in the upper left corner (**If the form doesn't exist, click the small icon with a + sign in the left sidebar to bring it up**), you can easily create periodic notes and theme notes with mouse clicks!
Periodic Notes
Theme Notes
## Task Management
Task collection and indexing
Task organization
## Goal Management
Annual goals from planning to implementation
## Time Management
## Usememos Synchronization
---
url: /guide/quick-start/pro-feature-overview.md
---
# Pro Version Feature Overview
The Pro version includes all the features of the Basic! In addition, it offers the following Pro features:
> Visit Youtube for more information: https://www.youtube.com/watch?v=C1Ph\_j00\_Sc
:::tip Also considering Aino Desktop?
LifeOS Pro continues as the Obsidian plugin path. Aino Desktop is a standalone AI-native desktop app. Both work around Markdown files, folders, tags, and wikilinks. See [Obsidian vs Aino](/guide/pro/aino-desktop.md).
:::
## Big Calendar Schedule Planning
Through simple drag and drop, you can plan the deadline for each task, supporting day view, week view, and month view. Easily manage your time, improve efficiency, and calmly handle each day!
Day View
Week View
Month View
### Schedule View
### Four-quadrant view
## Remote Calendar Two-way Sync
Supports subscribing to remote calendars using ICS and CalDAV protocols, such as TickTick and Feishu Calendar. This allows you to centralize all your calendar data for easy viewing and planning. For subscription methods, please refer to ["Calendar Subscription"](/guide/pro/calendar-sub.md#calendar-subscription).
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
## Advanced Lists
Are you struggling with long lists of tasks, bullet points, and files? This time, we bring you the ultimate solution! 🔍
Advanced lists have the following features:
* Indexing functionality, supporting search, sorting, and filtering, allowing you to easily find tasks, flash notes, and files scattered throughout!
* Creation functionality, allowing you to create tasks, flash notes, and files for the current theme with just one click!
Creating Tasks
Creating Flash Notes
Creating Files
* Copy functionality, copying the advanced list as text, using it as context for a specific theme, and sending it to AI tools, allowing you to leverage AI capabilities for deeper conversations!
## Home View
LifeOS aims to be your life system. The new homepage is simple and practical, giving you a clear overview of the system's inputs, projects (themes), tasks, and outputs, helping you better coordinate life and work.
### Workflow
All-in-one project management, forming an efficient closed loop from input to delivery, connecting every step and driving projects forward steadily.
### Habit Statistics
More than just recording — it analyzes the overall completion of habit modules in your journal, helping you scientifically understand your habit-building cycles.
### Flash Thought Wandering
Revitalize your historical notes, spark endless creativity, and let old thoughts grow new branches.
## Theme Notes
PARA notes have been upgraded to theme notes, with added toggle options, greatly reducing the learning curve for beginners. Users only need to focus on input, output, and themes to easily record, organize, and use notes.
At the same time, you can also use this as a foundation to move beyond PARA and create your own note system and workflow!
## Task Creation
Supports multiple entry points for creating tasks — whether you're recording in notes, planning on the homepage, organizing in advanced lists, or scheduling in the big calendar, you can quickly create tasks anytime, anywhere. For details, see [Task Creation](/guide/pro/task-create.md).
Create in Notes
Create in Home View
Create in Big Calendar
## Task View
A persistent sidebar task management panel that lets you view and manage tasks at any time. You can also drag tasks into the big calendar to plan your schedule. For details, see [Task View](/guide/pro/task-view.md).
## Pomodoro Timer
A built-in focus timing tool that supports Pomodoro mode (25-minute focus + 5-minute break) and free timing mode, helping you better manage time and improve productivity. For details, see [Pomodoro Timer](/guide/pro/pomodoro.md).
* **Dual-mode Timing**: Pomodoro mode and free timing mode to flexibly meet different scenarios
* **Project Association**: Associate timing with projects, and automatically log duration to the daily journal upon completion
* **Automation**: Auto-rest, auto-start next Pomodoro — no manual operation needed
* **Mini Timer**: Minimize to a floating timer for easy progress tracking while working on other pages
* **Statistics**: Today's Pomodoro count, focus duration, historical totals — all at a glance
## Convenience Features
Multiple thoughtful convenience features to enhance your daily experience. For details, see [Convenience Features](/guide/pro/convenient.md).
* **Auto-insert Timestamp in Daily Records**: Automatically insert timestamps when typing in daily records
* **Right-click Tag to Create Theme Notes**: Right-click a tag to quickly create or jump to the corresponding theme note
* **Right-click Theme Folder for Quick Transitions**: Freely move folders between "Projects", "Areas", "Resources", and "Archives" directories
* **Click Folder to Jump to Theme Index**: Click a folder name to directly jump to the theme index file
* **Click File Title to Focus in Sidebar**: Click a file title to automatically expand and focus the corresponding file in the sidebar
* **Auto-focus When Opening Journal**: Automatically focus on the last line of the daily records module when opening today's journal
---
url: /guide/quick-start/how-start.md
---
# How to Start Using LifeOS
:::tip
If this is your first time using LifeOS, start with [Start LifeOS in 10 Minutes](/guide/quick-start/getting-started.md) and practice with the example vault first. This page is better used after the example works, when you want to understand folder structure, plugin installation, and manual setup.
:::
## Directory Structure Description
It is recommended to read through the directory structure once, as it helps to deepen your understanding!
The directory below is interactive and clickable. Click the + sign to expand!
```tree
.
├── -1. Capture // Used to practice the CODE model's Capture step
│ └── README.md // Capture index file
├── 0. PeriodicNotes // Periodic notes system, each year has its own folder
│ ├── README.md // Usage instructions for periodic notes
│ ├── 2023
│ │ ├── Daily // Diary directory, each month has its own folder
│ │ │ └── 06
│ │ │ ├── 2023-06-01.md // Diary note
│ │ │ ├── 2023-06-02.md
│ │ │ └── 2023-06-03.md
│ │ ├── Weekly // Weekly note directory
│ │ │ ├── 2023-21.md // Weekly note
│ │ │ └── 2023-W22.md
│ │ ├── Monthly // Monthly note directory
│ │ │ ├── 2023-06.md // Monthly note
│ │ │ └── 2023-07.md
│ │ ├── Quarterly // Quarterly note directory
│ │ │ ├── 2023-Q1.md // Quarterly note
│ │ │ └── 2023-Q2.md
│ │ └── 2023.md // Annual log
│ └── Templates // Template files for periodic notes, use corresponding templates when creating daily notes, weekly logs, monthly logs, quarterly logs, and annual logs
│ ├── Daily.md
│ ├── Monthly.md
│ ├── Quarterly.md
│ ├── Weekly.md
│ └── Yearly.md
├── 1. Projects // PARA notes' Project category
│ ├── README.md // Project usage instructions
│ ├── Template.md // Project template file, used when creating a project
│ └── personal-brand-wot-sharing-meeting // Project example
│ ├── Attachments
│ │ └── PPT materials
│ │ ├── bit-logo.svg
│ │ └── warning.svg
│ ├── ChatGPT
│ │ ├── Why Frontend Engineering.md
│ │ ├── What is Frontend Engineering.md
│ │ └── The Contents of Frontend Engineering.md
│ ├── PPT Outline.md
│ ├── 2023-WOT-Share Session.README.md // Project index file, filename format requirement like XXX.README.md
│ ├── Architecture Diagrams
│ │ ├── Monorepo.svg
│ │ └── Polyrepo.svg
│ ├── Rehearsal
│ │ ├── Transcript.md
│ │ ├── Existing Problems.md
│ │ ├── Rehearsal Notes.md
│ │ ├── Potential Audience Questions.md
│ │ └── Live Presentation Tips.md
│ ├── Main Outline.md
│ ├── Previous Themes.md
│ └── x company's Practice in Frontend Engineering.pdf
├── 2. Areas // PARA notes' Area category
│ ├── README.md // Area usage instructions
│ ├── Template.md // Area template file, used when creating a project
│ ├── personal-brand // Area example
│ │ └── personal-brand.README.md // Area index file, filename format requirement like XXX.README.md
│ ├── work
│ │ └── work.README.md
│ ├── marriage-relationship
│ │ └── marriage-relationship.README.md
│ ├── parental-relationship
│ │ └── parental-relationship.README.md
│ └── parenting
│ └── parenting.README.md
├── 3. Resources // PARA notes' Resource category
│ ├── README.md // Resource usage instructions
│ ├── Template.md // Resource template file, used when creating a project
│ ├── knowledge-management // Resource example
│ │ └── knowledge-management.README.md
│ └── photography
│ └── photography.README.md
├── 4. Archives // PARA notes' Archive category
│ ├── README.md // Archive usage instructions
│ ├── Template.md // Archive template file, used when creating a project
│ └── parenting-take-a-name // Archive example
│ ├── program
│ │ ├── README.md
│ │ ├── index.js
│ │ ├── nameCandidateList.md
│ │ └── package.json
│ ├── Five Elements
│ │ ├── Earth.md
│ │ ├── Wood.md
│ │ ├── Water.md
│ │ ├── Fire.md
│ │ └── Metal.md
│ ├── Single Characters.md
│ ├── Rules.md
│ ├── Lin Yiru.png
│ ├── parenting-take-a-name.README.md
│ ├── Candidates List.md
│ ├── Programmed Naming.md
│ └── Five Elements and Meaning Lookup.md
├── 5. Express // Used to practice the CODE model's Express step
│ └── README.md // Express index file
├── README.md
├── Home.canvas
└── Tasks.md
```
## Setting Up a Repository from Scratch
### Installing the LifeOS Plugin
> Choose one of the following
#### Basic
[Click here to open Obsidian and install the LifeOS plugin](https://obsidian.md/plugins?id=periodic-para)
#### Paid Version
Download the following three files and place them in the corresponding files in the Obsidian repository's `.obsidian/plugins/lifeos-pro/` directory.
> Right-click this link, click "Save Link As...", to download
* https://lifeos.vip/lifeos-pro/manifest.json
* https://lifeos.vip/lifeos-pro/main.js
* https://lifeos.vip/lifeos-pro/styles.css
:::warning
.obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method
1. MacBook: Use the shortcut key Command + Shift + .
2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders
:::
### Installing Third-Party Plugins
* Dataview: [Click here to open Obsidian and install the Dataview plugin](https://obsidian.md/plugins?id=dataview)
* Templater: [Click here to open Obsidian and install the Templater plugin](https://obsidian.md/plugins?id=templater-obsidian)
Refer to the image below, enable "Trigger Templater on new file creation" in Templater
### Configuring Periodic Notes
Refer to the image below, configure your periodic notes directory and the titles for each module
Refer to the image below, configure your template files for periodic notes. Each time you create a periodic note, it will use the corresponding template to create a new note
### Configuring Theme Notes
Refer to the image below, configure your theme notes directory and the titles for each module
Refer to the image below, configure your template files for theme notes. Each time you create a theme note, it will use the corresponding template to create a new note
## Using a Ready-Made Example Repository
Refer to: ["Scenario 2"](/guide/overview/usage.md#scenario-2-use-existing-example-repository)
---
url: /guide/quick-start/how-update.md
---
# How to Update LifeOS
## Basic
The Basic of the plugin is available on the official plugin marketplace, so you can update it directly from the marketplace:
## Pro Version
The Pro version of the plugin needs to be updated using the update button within the LifeOS plugin:
---
url: /guide/example-vaults/index.md
---
# Example Vault Guides
LifeOS Pro example vaults can be opened directly in Obsidian. The complete package's `Example Vault` folder contains five filled examples—Memos, IPO, GTD, PARA, and OPC. Learn in one, then open its matching `Blank Vault` as your own main vault.
Start with the bottleneck you need to remove now:
| Vault | Choose it when your main problem is | Daily entry point | Upkeep |
| ------------------- | -------------------------------------------------------------- | ----------------------- | ----------- |
| [Memos](/guide/example-vaults/memos.md) | You lack a capture habit and only want bullets and tasks | Today's daily note | Lowest |
| [IPO](/guide/example-vaults/ipo.md) | You want a few categories that turn sources into useful output | `2. Themes/README.md` | Low |
| [GTD](/guide/example-vaults/gtd.md) | Tasks are scattered; next actions and follow-ups are unclear | `TASK.md` | Medium |
| [PARA](/guide/example-vaults/para.md) | Projects, responsibilities, and reusable knowledge all matter | `1. Projects/README.md` | Medium-high |
| [OPC](/guide/example-vaults/opc.md) | You already operate a one-person business, product, or service | `CEO Dashboard.md` | Highest |
The default recommendation runs from easiest to hardest: **Memos -> IPO -> GTD
-> PARA -> OPC**. Start with Memos when daily capture is not stable; skip ahead
when you already have a clear bottleneck. Memos is a time-based foundation that
can grow into IPO, GTD, or PARA.
The blank versions are `LifeOS Pro Memos Blank Vault`, `LifeOS Pro IPO Blank Vault`, `LifeOS Pro GTD Blank Vault`, `LifeOS Pro PARA Blank Vault`, and `OPC LifeOS Blank Vault`. They keep settings, folder skeletons, templates, and essential query pages without sample projects or business data.
Open the specific vault folder in Obsidian. Blank vaults do not duplicate plugin binaries; if needed, copy the plugins from the complete package's top-level `Plugin/` folder into `.obsidian/plugins/`.
## Can templates be switched?
They share Markdown, periodic notes, and task syntax, so content can move, but
templates are not one-click skins:
* **Memos -> IPO / GTD / PARA** keeps all periodic and daily notes, then adds the
target folders, templates, and settings.
* **IPO / GTD / PARA conversions** require reviewed semantic reclassification.
* **Any template -> OPC** should normally start in `OPC LifeOS Blank Vault`, then
receive selected operating material.
* **Returning to Memos** means stopping use of the taxonomy, not deleting old
folders and breaking links or historical queries.
Never overwrite a working vault with a Blank Vault's `.lifeos/settings.json`.
Back up first and add only the reviewed target folders and settings.
---
url: /guide/example-vaults/para.md
---
# PARA Example Vault
`LifeOS Pro PARA Vault` is the best complete starter vault for Obsidian LifeOS. Periodic notes keep the timeline, while projects, areas, resources, and archives organize long-term knowledge.
## Open the Vault in Obsidian
Start from the root `README.md`, then open `1. Projects`, `2. Areas`, `3. Resources`, and `4. Archives`. PARA is not about sorting every file at once; it helps you decide whether something is active, maintained, reference material, or finished.
## Open a Project Index
Project folders are for work with a clear outcome and end point. A project index keeps goals, tasks, material, and review notes together, while tasks created in daily notes can flow back through tags and links.
## 10-Minute Practice
1. Open today's daily note and write: `Today I am turning the LifeOS Pro example vault into my own work vault.`
2. Add a task: `- [ ] Create one real project and complete its README #personal-brand/LifeOS`.
3. Open the LifeOS task view and confirm the task is recognized.
4. In `1. Projects/`, create `Website Docs Refresh` from `Template.md`.
5. Use DeepAsk to generate a project review from the current project and recent daily notes.
Replace content before renaming folders so the default LifeOS Pro settings keep working.
## What to Read Next
* [Main System](/guide/core/main-system.md) — Understand how PARA and periodic notes work together.
* [Theme Notes](/guide/pro/theme-note.md) — Create project, area, and resource indexes with LifeOS Pro.
* [Task View](/guide/pro/task-view.md) — Aggregate `- [ ]` tasks from across the vault.
* [DeepAsk](/guide/ai-integration/deepask.md) — Generate reviews from projects and recent daily notes.
* [Complete Project Life Cycle](/guide/best-practice/project-life-cycle.md) — Move from creation to execution to archive.
---
url: /guide/example-vaults/ipo.md
---
# IPO Example Vault
`LifeOS Pro IPO Vault` splits knowledge work into input, themes, and output. It fits writers, researchers, indie builders, and people who often produce proposals.
## Open the Vault in Obsidian
Start with the relationship between `1. Input`, `2. Themes`, and `3. Output`. Input stores raw material, themes process it over time, and output holds articles, proposals, scripts, or product copy.
## Open a Theme Index
A theme is not just a folder. It is a long-running processing line. Link multiple input notes to the same theme, then ask DeepAsk to generate an output outline from the theme index and related material.
## 10-Minute Practice
1. Create `User Feedback - LifeOS Example Vault.md` under `1. Input/`.
2. Add three feedback points: users do not know which vault to download, do not understand theme notes, and do not know how DeepAsk should help.
3. Create `Example Vault Onboarding Experience.md` under `2. Themes/`.
4. Link the input to the theme and write one judgment: onboarding docs should help users choose templates by scenario.
5. Create `LifeOS Example Vault Selection Guide.md` under `3. Output/`.
6. Use DeepAsk to generate an outline from the input and theme.
## What to Read Next
* [Connections](/guide/basic/connection.md) — Link input, themes, and output with tags and wikilinks.
* [Retrieval](/guide/basic/retrieval.md) — Find material through tags, index files, and folders.
* [Theme Notes](/guide/pro/theme-note.md) — Use themes as the processing layer for material.
* [Advanced List](/guide/pro/advanced-list.md) — Turn scattered records into filterable lists.
* [DeepAsk](/guide/ai-integration/deepask.md) — Generate outlines from input and theme context.
---
url: /guide/example-vaults/gtd.md
---
# GTD Example Vault
`LifeOS Pro GTD Vault` starts with execution. It puts unclear material into the inbox, then turns it into next actions, waiting-for items, someday items, projects, or reference material.
## Open the Vault in Obsidian
The GTD example vault starts from `1. Inbox` and `2. Actions`. Everything unclear enters the inbox first, then moves into next actions, waiting-for items, someday items, projects, or reference material.
## Review Next Actions
`Next Actions.md` groups executable tasks by context. After the Tasks plugin is enabled, these queries aggregate tasks from daily notes, projects, and the inbox, so you only need to clear the inbox regularly and work from the action list that matches your current context.
## 10-Minute Practice
1. Add three unclear items to `1. Inbox/Inbox.md`.
2. Turn one into a next action: `- [ ] Polish the LifeOS GTD example-vault guide #gtd/next #ctx/computer`.
3. Turn one into a waiting-for item: `- [ ] Waiting for Alex to confirm pricing-page copy #gtd/waiting`.
4. Move one idea you will not do now into `Someday Maybe.md`.
5. Open `TASK.md` and confirm the Tasks plugin aggregates the action lists.
6. Use `Weekly Review.md` to check whether there is still unclarified input.
## What to Read Next
* [Task Creation](/guide/pro/task-create.md) — Create tasks from notes, calendar, and task views.
* [Task View](/guide/pro/task-view.md) — Aggregate next actions, waiting-for items, and lists.
* [Calendar View](/guide/pro/calendar.md) — Put dated actions onto the calendar.
* [Pomodoro](/guide/pro/pomodoro.md) — Execute actions and record time.
* [Review](/guide/basic/review.md) — Clear the inbox, waiting-for items, and someday list regularly.
---
url: /guide/example-vaults/opc.md
---
# OPC LifeOS Example Vault
`OPC LifeOS Vault` is a LifeOS Pro example vault for a one-person company. It splits solo operations into a CEO dashboard, seven departments, input/output pipelines, and AI dashboards.
## Start With the Operating View
After opening the vault, start from `OPC LifeOS.md`, `CEO Dashboard.md`, and `CEO Dashboard.AI.md`. The point is not to sort files first; it is to see the current company state: goal, revenue, leads, projects, risks, and this week's focus.
:::tip The same OPC template can open in Aino
The core assets of OPC LifeOS are still Markdown files and folders. You can use it in Obsidian + LifeOS Pro, or open the same Vault in Aino Desktop and use the AI sidebar to refresh CEO and department `.AI.md` briefs. See [Obsidian vs Aino](/guide/pro/aino-desktop.md).
:::
## 10-Minute Practice
1. Open `CEO Dashboard.md` and `CEO Dashboard.AI.md`.
2. Open `3 Departments/04 Sales & Customer Department/04 Sales & Customer Department.md`.
3. Add a daily note record: `#OPC/sales-customer Alex is interested in the OPC setup service and wants delivery timing before next Wednesday.`
4. Create a raw lead note under `1 Input/Inbox`.
5. Create a quote draft under `2 Output/Drafts`.
6. Use DeepAsk to read the CEO dashboard, Sales & Customer department, recent daily notes, and input/output material, then refresh `CEO Dashboard.AI.md`.
Every department has `Agent.md`, `Soul.md`, `Memory.md`, and a sibling `.AI.md` dashboard, so AI can generate operating briefs from stable context.
## Open a Department
Each department is a topic directory. In daily work, put raw leads under `1 Input/Inbox` and quote drafts under `2 Output/Drafts`, while sales decisions, quote templates, customer profiles, and follow-up cadence live in `04 Sales & Customer Department`.
## Review the AI Dashboard
In Obsidian, open `CEO Dashboard.AI.md` and ask DeepAsk to refresh the operating brief from the current index file, sibling material, recent daily notes, and input/output pipelines. Department `.AI.md` files work the same way: read the department index first, then the department files, then summarize state, risks, and next actions.
## What to Read Next
* [DeepAsk](/guide/ai-integration/deepask.md) — Generate CEO and department `.AI.md` operating dashboards.
* [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) — Let AI maintain the vault with stable rules.
* [Main System](/guide/core/main-system.md) — Understand how knowledge management and periodic notes work together.
* [Sub System](/guide/core/sub-system.md) — Turn goals, tasks, and time management into operating rhythm.
* [Theme Notes](/guide/pro/theme-note.md) — Maintain the seven departments as long-lived topic directories.
---
url: /guide/example-vaults/memos.md
---
# Memos Template Quick Start
`LifeOS Pro Memos Vault` is recommended for Logseq, flomo, and usememos users. It demonstrates continuous capture with two sample daily notes and one sample weekly review; use `LifeOS Pro Memos Blank Vault` as your own main vault afterward.
## Template structure
* Both vaults use a daily template with one empty Daily Record heading for bullets and `- [ ]` tasks.
* `LifeOS Pro Memos Vault` also includes `2025-01-06.md`, `2025-01-07.md`, and `2025-W02.md` to demonstrate ordinary records, open tasks, completed tasks, and periodic review.
* Weekly, monthly, quarterly, and yearly templates keep four LifeOS queries: due tasks, recorded tasks, recorded bullets, and completed tasks.
* The templates contain no project, area, or theme snapshots and no `ProjectListByTime` or `AreaListByTime` queries.
## Use it in Obsidian
1. Open `LifeOS Pro Memos Vault` from the complete package's `LifeOS Pro/Example Vault/` folder as a local vault.
2. If LifeOS Pro is not installed, copy `Plugin/lifeos-pro` from the package root into this vault's `.obsidian/plugins/`.
3. Open `0. PeriodicNotes/2025/Daily/01/2025-01-06.md`, `2025-01-07.md`, and `0. PeriodicNotes/2025/Weekly/2025-W02.md` to understand records, tasks, and review queries.
4. When you finish learning, open `LifeOS Pro Memos Blank Vault` in Obsidian, create today's daily note, and begin your own records.
Do not clear the example vault. `LifeOS Pro Memos Blank Vault` keeps the same settings and daily-to-yearly templates without sample date folders.
## When should you upgrade?
Stay with Memos while time-based retrieval is enough. Upgrade only when a real
new problem appears:
| New problem | Upgrade to | What it adds |
| --------------------------------------------------------------- | ---------- | ------------------------------------------------- |
| Collected sources need to become articles or deliverables | IPO | Input, topic processing, and output pipeline |
| Tasks need clear next-action, waiting, and review states | GTD | Inbox, action states, projects, and reviews |
| Projects, responsibilities, and reference knowledge all compete | PARA | Projects, areas, resources, archive, and indexing |
| Products, customers, revenue, and delivery need one system | OPC | CEO cockpit, departments, and operating pipelines |
## Upgrade from Memos
The table runs from IPO through OPC in increasing complexity. Old daily notes
do not need to move when upgrading to IPO, GTD, or PARA:
1. Back up the vault and keep the current periodic-note folder, date folders,
and custom templates.
2. Explore the target filled example and confirm it solves the problem.
3. Add folders and templates from the target Blank Vault; never overwrite the
whole `.lifeos/settings.json`.
4. Enable the target capability in LifeOS Pro and verify each path.
5. Use the new structure for new material first. Move or tag old records only
when doing so creates real retrieval value.
Existing `- [ ]` and `- [x]` Markdown tasks continue to appear in task and review
queries.
For OPC, start in `OPC LifeOS Blank Vault`, then copy the daily notes and
operating material you need. Its dashboards, departments, agent files, and
periodic-note path should not be introduced by overwriting settings in place.
## Can you switch back?
Yes, through migration—not as a one-click toggle. To return to Memos, stop using
the taxonomy but keep old folders so links remain valid. IPO, GTD, and PARA
conversions require reviewed semantic reclassification in batches.
---
url: /guide/config/index.md
---
# Configuration
**Typically, you don’t need to modify the settings, as LifeOS provides an out-of-the-box example vault with all configurations pre-adapted for its directory structure.**
You may need to adjust the plugin settings in the following scenarios:
1. Changing the default directories in the example vault, such as the locations for periodic notes, topic notes, etc.
2. Modifying headings in the example vault’s diary templates, like "Habit Tracking," "Project List," or adjusting headings in seasonal templates, such as "Key Dimensions."
3. Using a self-hosted Usememos service.
4. Subscribing to a remote calendar.
So, how do you access the LifeOS plugin settings? Here’s a step-by-step guide using the LifeOS Pro plugin as an example:
First, click the gear icon in the bottom-left corner.
Next, select "LifeOS Pro" from the third-party plugins in the sidebar.
Each setting in the plugin comes with a description. Adjust them according to your needs—no further details are provided here.
---
url: /guide/free/distinct-with-pro.md
---
# Differences from the Pro Version
The Pro version includes all features of the Basic. For detailed documentation on Pro version features, see: [Pro Version Features](/guide/pro/distinct-with-free.md)
## Feature Differences
| Feature | Pro Version | Basic |
| --------------------- | ----------- | ----- |
| Note Creation | ✅ | ✅ |
| Task Management | ✅ | ✅ |
| Time Management | ✅ | ✅ |
| Goal Management | ✅ | ✅ |
| Bullet Record List | ✅ | ✅ |
| Move between PARA | ✅ | ✅ |
| Custom Date Formats | ✅ | ✅ |
| Theme Notes | ✅ | ❌ |
| Home View | ✅ | ❌ |
| Task Creation | ✅ | ❌ |
| Task View | ✅ | ❌ |
| Calendar View | ✅ | ❌ |
| Calendar Subscription | ✅ | ❌ |
| Advanced Lists | ✅ | ❌ |
| Pomodoro Timer | ✅ | ❌ |
| Convenience Features | ✅ | ❌ |
---
url: /guide/free/create-note.md
---
# Creating Notes
> Based on LifeOS Basic 1.20.8
## Creating Periodic Notes
### **User Guide**
> Detailed explanation based on the image above
#### **Switching Note Types**
* **Feature Description**: By clicking the "Note Type" button at the top of the interface, users can switch between different note types.
* **Operation Instructions**:
* After clicking, you can switch between "Periodic Notes" and "Theme Notes" to choose the note type that suits your recording needs.
#### **Periodic Notes Tab Switching**
* **Feature Description**: This function allows users to quickly switch between different types of periodic notes when creating and viewing them.
* **Operation Instructions**:
* At the top of the calendar page, you will see a "Periodic Notes" tab. After clicking on this tab, you can select different types of periodic notes.
* Users can choose appropriate periodic note types based on their needs. For example, you can choose different cycle types such as weekly, monthly, etc. for recording.
* This switching operation allows users to conveniently manage notes in different cycle views, ensuring that the periodicity of records better meets your usage requirements.
#### **Navigation for Different Time Units**
* **Feature Description**: Users can quickly browse other dates using the navigation buttons above the calendar.
* **Operation Instructions**:
* Click the "Previous Year" button to return to last year.
* Click the "Previous Month" button to return to the previous month.
* Click the "Next Month" button to view next month's calendar.
* Click the "Next Year" button to go to next year.
#### **Quick Jump to Specific Date**
* **Feature Description**: You can jump directly to notes related to that date by clicking on a specific date in the calendar.
* **Operation Instructions**:
* For each date in the calendar, if there is a small dot above it, it indicates that notes have been created for that date. Click on that date to jump to the notes for that date.
* If there is no small dot above the date, it indicates that no notes have been created for that date yet. Click on that date to create a new note.
#### **Viewing Existing Notes**
* **Feature Description**: Users can see existing note records for a date through the small dots on the calendar date.
* **Operation Instructions**:
* The small dots above each date indicate that notes have been created for that date. After clicking on these dates, you will be guided to the relevant note page.
#### **Date Marking**
* **Feature Description**: Special marking on a date indicates that it is the current date.
* **Operation Instructions**:
* Specially marked dates will display different marking symbols, identifying that date as the current date. Click to create notes for the current date.
* Depending on different themes, the marking style may vary. In the current example, it's the "Border" theme marking.
#### **Accessing the Website**
* **Feature Description**: Users can access the LifeOS official website by clicking the "?" button at the top of the calendar.
* **Operation Instructions**:
* Click the "?" icon to jump to the LifeOS official website for more information or support.
### Periodic Notes Settings
#### Detailed Settings for "Periodic Notes" Tab
1. **Enable (Switch)**
* **Description**: When this switch is turned on, it indicates that the "Periodic Notes" function is activated. When turned off, this function will not be used, and subsequent configuration items will not take effect in the system.
* **Typical Usage**: If you want to use the "Periodic Notes" function (such as daily, weekly journals) in your current note system, make sure this switch is turned on.
2. **Periodic Notes Directory**
* **Description**: This specifies a folder path for storing all periodic note (such as daily, weekly, monthly journals) files.
* **Operation Suggestion**: It is recommended to use a relative path or default project path (such as `PeriodicNotes`). This makes it easier to manage note files uniformly in the future.
3. **Habit Title**
* **Description**: You can customize a title name for "Habit Tracking" or "Habit List" here. This title will be inserted into the corresponding position of periodic notes (such as daily/weekly/monthly journals, etc.) for recording or tracking your daily habits. Tasks under this title (statements starting with `-[]` syntax) will not be counted as tasks.
* **Example Scenario**: Automatically insert a paragraph titled "Habit" in each daily or weekly note to facilitate recording daily/weekly habit check-ins.
4. **Project List Title**
* **Description**: This customizes a title for the "Project List". When generating periodic notes, the system will insert this title position in the corresponding note template for you to list or track projects.
* **Example Scenario**: Automatically insert "Project List" in weekly or monthly templates to record project progress for the week/month.
5. **Domain List Title**
* **Description**: Similar to the above, you can customize a title to list "Domain" or "Dimension" content in periodic notes.
* **Example Scenario**: Insert "First Things Dimension" in quarterly or annual notes to record and manage higher-level domain classifications.
6. **Week Start Day**
* **Description**: Set the start date of each week. Choosing "Auto (Monday)" means the week starts from Monday, or you can set other start dates according to personal needs.
* **Effect**: Also affects calendar display.
7. **Lunar Calendar**
* **Description**: When this switch is turned on, lunar dates and some Chinese holiday information will be displayed in the calendar or related periodic notes.
* **Applicable Scenario**: If you need to pay attention to lunar solar terms or traditional holidays, you can turn this on. If there is no such need, it can be turned off to simplify the interface.
8. **Advanced Settings (Switch)**
* **Description**: When turned on, you can make more in-depth, personalized configurations for periodic notes, such as customizing template file paths.
* **Usage**: When you need more flexible configuration (such as file directory structure or template path) beyond the default settings, you can turn on this option.
9. **Custom Template File Path**
* **Description**: After "Advanced Settings" is turned on, you can customize template file paths for different periodic notes. Including:
* **Daily Journal Template** (Daily)
* **Weekly Journal Template** (Weekly)
* **Monthly Journal Template** (Monthly)
* **Quarterly Journal Template** (Quarterly)
* **Yearly Journal Template** (Yearly)
* **Function**: The system will automatically reference the corresponding Markdown template files according to the paths configured here to generate various types of periodic notes, avoiding repetitive writing of formats, paragraph structures, etc.
* **Example**: Such as `PeriodicNotes/Templates/Daily.md`, indicating generating daily journals from the `Daily.md` template in the `PeriodicNotes/Templates/` folder.
***
#### "Daily Record" Synchronization Settings
1. **Daily Record (Switch)**
* **Description**: When this is turned on, the system will synchronize daily records from the specified service to the current note system, or create them automatically according to your chosen method.
* **Typical Scenario**: If you need to connect with note services like [usememos](https://usememos.com), you can configure it here.
2. **Title**
* **Description**: Set a title name to mark daily records synchronized from external sources.
* **API**
* **Description**: Fill in the API root address for communicating with external services (such as `usememos`).
* **Note**: Please confirm the API version requirements (such as `< 0.22.0` or `>= 0.22.3`) to ensure the system can correctly interface with the service.
* **Token**
* **Description**: Fill in the "Access Token" obtained from the external service for authentication and authorization.
* **Note**: Please keep this Token confidential to avoid misuse by others.
* **Auto Create (Switch)**
* **Description**: When turned on, if the system detects that notes for a certain date have not been created yet, it will automatically generate note files or records for that date according to the template.
* **Usage**: Very convenient for users with a large volume of daily notes, as it can avoid manually creating daily journals every day.
* **Warning (Switch)**
* **Description**: When this is turned on, if the system detects that notes for that date do not exist, it will send you a reminder to prevent omissions.
* **Usage**: Very practical for people who need to be constantly reminded to supplement or check their daily notes, avoiding missing records.
## Creating Theme Notes
## Concepts and Available Methods Explanation
### Task
1. Concept: Statements created using the \` - \[ ] \` syntax.
2. Collection Scope: All notes, different methods have different collection scopes on different pages, please refer to the methods below for specifics.
3. Available methods:
1. TaskRecordListByTime
2. TaskDoneListByTime
1. Description: Parse the filename of the current periodic note, extract tasks recorded and completed within the corresponding period, for example:
1. If this statement is in a daily note template, creating a daily note will extract the list of tasks completed that day from all notes;
2. If this statement is in a weekly note template, creating a weekly note will extract the list of tasks completed that week from all notes;
3. If this statement is in a monthly note template, creating a monthly note will extract the list of tasks completed that month from all notes;
4. If this statement is in a quarterly template, creating a monthly note will extract the list of tasks completed that quarter from all notes;
5. If this statement is in an annual template, creating a monthly note will extract the list of tasks completed that year from all notes;
2. Usage Method:
````markdown
```LifeOS
TaskDoneListByTime
```
````
3. Effect Image:
3. TaskListByTag
1. Description: Get the ["Theme Tag"](/guide/beginner-guide/core-concept.md#主题标签) set in the current file, query tasks with that theme tag throughout the entire repository
2. Usage Method
````plain text
```LifeOS
TaskListByTag
```
````
* Effect Image
### Bullet (Flash Note)
1. Collection Scope: All notes
2. Available methods:
1. BulletListByTag
1. Description: Get the ["Theme Tag"](/guide/beginner-guide/core-concept.md#主题标签) set in the current file, query flash thoughts with that theme tag throughout the entire repository
2. Usage Method
````plain text
```LifeOS
BulletListByTag
```
````
3. Effect Image
### File (File)
1. Collection Scope: All notes
2. Available methods:
1. FileListByTag
1. Description: Get the ["Theme Tag"](/guide/beginner-guide/core-concept.md#主题标签) set in the current file, query files with that theme tag throughout the entire repository
2. Usage Method
````plain text
```LifeOS
FileListByTag
```
````
* Effect Image
### Project (Project)
:::tip
This section shows the legacy Templater syntax for community / open-source LifeOS. The new LifeOS Pro built-in syntax uses `{{snapshot:Project}}`; see [Template Syntax](/guide/beginner-guide/template-syntax.md).
:::
1. Available methods:
1. ProjectListByTime
1. Description: Daily, weekly, monthly, quarterly, annual project lists from daily, weekly, monthly, quarterly, annual notes, automatically statistics project time proportion based on time consumption
2. Usage Method:
````markdown
```LifeOS
ProjectListByTime
```
````
* Effect Image
2. LifeOS.Project.snapshot()
1. Description: Project Today Snapshot
2. Usage Method:
```markdown
<% LifeOS.Project.snapshot() %>
```
* Effect Image
### Area (Area)
:::tip
This section shows the legacy Templater syntax for community / open-source LifeOS. The new LifeOS Pro built-in syntax uses `{{snapshot:Area}}`; see [Template Syntax](/guide/beginner-guide/template-syntax.md).
:::
1. Available methods:
1. AreaListByTime
1. Description: Summarizes area time for the selected period. In addition to time recorded directly against an area, project time is automatically rolled up through hierarchical tags (for example, area tag `A` and project tag `A/A-1`)
2. Usage Method
````plain text
```LifeOS
AreaListByTime
```
````
* Effect Image
2. LifeOS.Area.snapshot()
1. Description
2. Usage Method
```plain text
<% LifeOS.Area.snapshot() %>
```
* Effect Image
---
url: /guide/free/task-management.md
---
# Task Management
Task collection and indexing
Task organization
## Task Collection
Whether in "Daily Notes", "Weekly Notes", "Monthly Notes", or "PARA Notes", I quickly create tasks using Markdown's - \[ ] Task 1 syntax, thereby completing task collection. You don't need to be particularly concerned about which note you record tasks in; what you need to care about is tagging each record with appropriate "Tags". If there's a specific deadline, you can also trigger deadline input by typing "due".
Why can you be unconcerned about where you collect tasks? Because you can review this task in multiple places, such as the root directory's task index, task collection modules in weekly notes, monthly notes, quarterly notes, yearly notes, and PARA notes' \*.README.md index files.
## Task Organization
Since collected tasks can be easily accessed from various modules, you can place individual tasks as "block links and block references" into corresponding modules when planning "Weekly Notes" and "Monthly Notes", serving as "This Week's" and "This Month's" to-do items!
---
url: /guide/free/target-management.md
---
# Goal Management
Annual goals from planning to implementation
## Goal Setting
At the beginning of each year, plan your annual goals through the "Yearly Note". You can approach this from the important matters dimension (i.e., "Areas"), or through a role dimension, which makes it easier for you to maintain a sense of purpose in each "Area" and "Role".
## Goal Breakdown
At the beginning of each quarter, break down the annual goals set in the "Yearly Note" through the "Quarterly Note". After all, annual goals are significant and cannot be accomplished overnight. The breakdown in the "Quarterly Note" serves as a roadmap for completing the "Annual Goals".
## Goal Decomposition
The above two steps only address goal setting and breakdown. Goal achievement still needs to be implemented through individual "Tasks". So how do we do this? It's simple: at the beginning of each month, break down and organize the "Tasks" needed for the month by referring to the "Quarterly Note". Then at the beginning of each week, we just need to select and transfer tasks from the "Monthly Note" to the "Weekly Note";
---
url: /guide/free/time-management.md
---
# Time Management
Friends often ask me how to practice time management in Obsidian LifeOS? 📊
For time management in Obsidian LifeOS, my recommendation is to only track your time spent on key matters, as these are the things you truly need to invest significant time and energy in. If you're spending too little time on key matters, you need to spend more! 📈 Tracking unimportant matters is actually a waste of time.
According to the PARA organization method, each project is your "key matter," so we only need to track time spent on these! 🔑
In practice, many people mistakenly think this can be automatically tracked, but in reality, the time spent on each project every day needs to be recorded manually, because only you know where your time went! However, you can use tools like the Pomodoro timer 📱 or Timemator 🖥️ to track time. My method is to use computer screen-on time as the total daily time spent, and Timemator records the time spent on various projects each day. This way, weekly, monthly, quarterly, and yearly project lists can automatically calculate the proportion of time spent. 📅
**Summary**
## 1️⃣ Tool Assistance
Use tools like the Pomodoro timer or Timemator to manually record daily time consumption on various projects. ⌛🔧
:::tip Pro Version Built-in Pomodoro Timer
LifeOS Pro has a built-in [Pomodoro Timer](/guide/pro/pomodoro.md) that automatically records time spent to your daily note's project list after timing completes - no manual entry required!
:::
## 2️⃣ Manual Tracking
In the project list section of a daily note, manually track the time spent on each project and enter the day's total time on a separate final line. This provides the source data for weekly, monthly, quarterly, and yearly notes. 📝
```markdown
## Project List
- [[Product Launch]] 3hr00
- [[Technical Refactor]] 1hr00
- [[Team Management]] 0hr30
8hr20
```
:::warning Do Not Omit the Total Time
The final **`8hr20`** line is the day's total time and the baseline LifeOS uses to calculate project time proportions. Keep the total on its own line without a list marker. The total does not have to equal the sum of project time; in this example, the projects account for 4hr30 and the remaining 3hr50 is time not assigned to a project.
The formula is: **project time proportion = time spent on one project ÷ total time for the day**. Convert both values to minutes first. For example, Product Launch is 3hr00 (180 minutes) and the day's total is 8hr20 (500 minutes), so `180 ÷ 500 = 36%`.
:::
## 3️⃣ Periodic Summarization
The LifeOS plugin reads data from step 2 and automatically calculates the proportion of time spent on each project in "Weekly Notes," "Monthly Notes," "Quarterly Notes," and "Yearly Notes." 📉📆
Through this management method, you can truly understand "where your time went," more efficiently adjust and plan your time, and give your key matters more attention! 🚀
---
url: /guide/pro/distinct-with-free.md
---
# Differences from the Basic
The Pro version includes all features of the Basiced documentation on Basic featurBasiceatures]\(../free/Basic.md)
## Feature Differences
| Feature | Basicon |
| --------------------- | ------- | --- |
| Note Creation | ✅ | ✅ |
| Task Management | ✅ | ✅ |
| Time Management | ✅ | ✅ |
| Goal Management | ✅ | ✅ |
| Theme Notes | ✅ | ❌ |
| Home View | ✅ | ❌ |
| Task Creation | ✅ | ❌ |
| Task View | ✅ | ❌ |
| Calendar View | ✅ | ❌ |
| Calendar Subscription | ✅ | ❌ |
| Advanced Lists | ✅ | ❌ |
| Pomodoro Timer | ✅ | ❌ |
| Convenience Features | ✅ | ❌ |
---
url: /guide/pro/aino-desktop.md
---
import {
ProductComparison,
ProductBoundaryNotice,
ProductDecisionGuide,
} from '../../../../../shared-site-theme/ProductComparison';
# Obsidian vs Aino
LifeOS Pro will continue as the Obsidian plugin path. Aino Desktop is a new standalone desktop app path. They are not replacements for each other; they are two Markdown Workspaces for opening and operating on the same kind of note assets.
If you like the Obsidian plugin ecosystem, themes, custom workspaces, and local scripts, Obsidian + LifeOS Pro remains a good choice. If you want a more out-of-the-box AI note workspace, Aino Desktop is worth considering.
## Capabilities and Boundaries
See the complete 10-part capability and boundary comparison
## Stay With LifeOS Pro
Choosing LifeOS Pro means Obsidian remains your primary workspace. LifeOS Pro enhances periodic notes, theme notes, tasks, calendar, advanced lists, and daily convenience features inside Obsidian.
This path fits when:
* Your Obsidian plugin setup is already stable.
* You need community plugins, themes, hotkeys, and local scripts.
* You want the LifeOS methodology inside an existing Obsidian Vault.
* You want control over every plugin and workspace detail.
## Consider Aino Desktop
Aino Desktop is an AI-native Markdown workspace. It can open Obsidian Vaults, use Memos / IPO / GTD / PARA / OPC example vaults from easiest to hardest, and integrate the AI sidebar, tasks, calendar, templates, and workspace views more tightly.
This path fits when:
* You want less setup and more out-of-the-box workflow.
* You want AI to naturally read the current note, tags, files, and template context.
* You want a desktop workspace for one-person company operations, project management, review, and content production.
* You want to keep Markdown files instead of moving into a private database.
## The Same Markdown Assets
LifeOS Pro and Aino Desktop both work around Markdown files, folders, tags, and wikilinks. Aino's commitment is: no private syntax lock-in, and no note format that only Aino can read.
:::tip
You can use Obsidian as a highly extensible editor, and Aino as an AI-native desktop view layer. Use only one app to edit the same file at the same time to avoid write conflicts.
:::
## How Much Is Shared?
LifeOS Pro shares the LifeOS business core, data structures, and most product views, using Aino Desktop as the interaction and visual baseline. Obsidian still owns the editor, file explorer, workspace layout, theme variables, and plugin lifecycle, so those host boundaries use dedicated adapters instead of copying Aino directly.
Equivalent workflows such as Home, Workbench, periodic notes, and tasks should remain aligned. Opening files, switching native views, browser integration, and mobile behavior are implemented through Obsidian adapters. Shared functionality does not guarantee identical pixels or identical host capabilities.
## Continue Reading
* [Obsidian vs Aino](https://aino.md/guide/intro/obsidian-vs-aino?utm_source=obsidian_site\&utm_medium=docs\&utm_campaign=workspace_choice) — Read the standalone desktop app perspective on the Aino site.
* [OPC LifeOS Example Vault](/guide/example-vaults/opc.md) — The same OPC template can be opened in Obsidian LifeOS Pro and Aino.
* [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) — Let AI maintain your LifeOS Vault with stable rules.
---
url: /guide/pro/theme-note.md
---
# Theme Notes
## What are Theme Notes?
They are the basic units of LifeOS. Every topic in your life and work can be viewed as a theme!
**It can be a project with a clear deadline, such as**
**It can also be an area that you need to continuously improve and focus on, such as**
**It can even be a topic you're interested in, such as**
Each theme note has its own unique ID, which is the ["Theme Tag"](/guide/beginner-guide/core-concept.md#主题标签). It's essential to understand the concept of ["Theme Tags"](/guide/beginner-guide/core-concept.md#主题标签) as they are used throughout the entire LifeOS system. We strongly recommend reading the ["Theme Tags"](/guide/beginner-guide/core-concept.md#主题标签) documentation thoroughly!
## How to Create Theme Notes?
In the form in the upper left corner (**If the form doesn't exist, click the small icon with a + sign in the left sidebar to bring it up**), switch to the theme note form, enter the ["Theme Tag"](/guide/beginner-guide/core-concept.md#主题标签), and you can create it! After creation, it will jump to the "Theme Index File". Each theme index file has its own three ["Advanced Lists"](/guide/pro/advanced-list.md), which are used to index "Theme Tasks", "Theme Bullets", and "Theme Files" that are "tagged with the current theme tag" scattered throughout the entire repository!
---
url: /guide/pro/home-view.md
---
# Home View
## Workflow
One-stop project management, from input to delivery, forming a closed loop, linking each step, driving the project forward steadily.
## Habit statistics
Not just recording, but also analyzing, statistics on the overall completion of the habit module in the diary, scientifically understanding your habit formation cycle.
## Flash random
Activate your historical notes, sparking endless creativity and allowing old thoughts to grow new branches.
---
url: /guide/pro/habit-statistics.md
---
# Habit Statistics Guide
LifeOS Pro reads standard Markdown check-ins from daily notes and summarizes completions, streaks, and trends. The feature is enabled by default, while built-in example templates keep it disabled and contain no preset habits. Enable and configure it only when it supports your own goals.
## 1. Enable It and Set the Heading
Open **LifeOS Pro Settings → Periodic Notes**:
1. Turn on **Habit Statistics**.
2. Set **Habit Header** to `Habit`, or use your own heading.
3. Confirm that the daily-note folder and template path are correct.
Turning Habit Statistics off hides both the header field and the Home entry. Existing daily-note content remains untouched.
## 2. Configure the Daily Template
Open the daily template configured for the current vault and add this section:
```markdown
## Habit
- [ ] Morning stretch
- [ ] Read for 20 minutes
- Water
- [ ] +1
- [ ] +1
- [ ] +1
- [ ] +1
```
Regular checkboxes are counted by day. An item with multiple `+1` children is counted by completion. The level-two heading in the template must match the Habit Header setting.
This format uses only Markdown. It does not require Obsidian Tasks, Dataview, or another plugin, so the same daily template also works in Aino Desktop.
## 3. Review the Results
After checking off habits in daily notes, open **LifeOS Home → Habit Statistics** to review completion rates, totals, and streaks across different time ranges.
Start with two to four behaviors that matter. A long checklist adds friction to every daily note and makes the statistics less focused.
## Troubleshooting
Check that the feature is enabled, the heading matches, the daily note is inside the periodic-notes folder, the items use standard Markdown checkboxes, and the note has been saved.
Continue reading: [Home View](/guide/pro/home-view.md) · [Choosing Between Aino Desktop and LifeOS Pro](/guide/pro/aino-desktop.md)
---
url: /guide/pro/task-create.md
---
# Task Creation
## Creating in Notes
## Creating in LifeOS Pro Home Page
## Creating in LifeOS Pro Advanced Lists
## Creating in LifeOS Pro Big Calendar
---
url: /guide/pro/task-view.md
---
# Task View
Permanent sidebar task management, which can also be dragged to the big calendar for schedule planning!
See [Task Creation](/guide/pro/task-create.md) for creating tasks.
---
url: /guide/pro/calendar.md
---
# Calendar View
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
---
url: /guide/pro/calendar-sub.md
---
# Calendar Subscription
LifeOS Pro supports multiple ways to subscribe to remote calendars, allowing you to centrally manage all your schedules in Obsidian.
## Subscription Methods Comparison
| Method | Sync Direction | Use Case |
| ------------------------ | ----------------- | ----------------------------------------------------------------- |
| iCloud Calendar (CalDAV) | Two-way sync | Apple ecosystem users, need phone reminders |
| Google Calendar (CalDAV) | Two-way sync | Google ecosystem users, need cross-platform reminders |
| CalDAV Calendar | Varies by service | Enterprise calendar subscription (Feishu is read-only, see below) |
| ICS Calendar | One-way pull | Read-only subscribe to TickTick, Outlook Calendar, etc. |
## Import from CalDAV Account
### Subscribe to iCloud Calendar (Two-way Sync)
> iCloud Calendar supports two-way sync: not only can you view iCloud calendar events in Obsidian, but you can also push tasks from Obsidian to iCloud Calendar, enabling reminders on iOS, Android, macOS, Windows, Linux, and other platforms.
**Step 1: Get App-Specific Password**
1. Visit https://icloud.com, after login, open https://account.apple.com/account/manage
2. Click to generate an "App-Specific Password". You need to name the password first, for example, "Calendar"
**Step 2: Configure iCloud Calendar**
1. In the calendar configuration page of the LifeOS Pro plugin settings, enable "iCloud Calendar Subscription"
2. Enter your Apple ID (username) and the app-specific password generated in the previous step
3. Enter `caldav.icloud.com` for the server address
4. The plugin will automatically fetch your iCloud calendar list, select the default push calendar
**iCloud Sync Features**
* **Enable Push to iCloud**: When enabled, local tasks can be pushed to iCloud Calendar; when disabled, only pulls tasks from remote without pushing local tasks
* **Delete Completed Tasks**: When enabled, completed and cancelled tasks will be automatically deleted from iCloud Calendar
* **Reminder Settings**: Configure reminders separately for all-day events and timed tasks
* All-day event reminders: Set how many days in advance and the specific reminder time
* Timed task reminders: Set how many minutes/hours/days/weeks in advance to remind
### Subscribe to Google Calendar (Two-way Sync)
> Google Calendar supports two-way sync: not only can you view Google Calendar events in Obsidian, but you can also push tasks from Obsidian to Google Calendar, enabling reminders on Android, iOS, Web, and other platforms.
**Step 1: Create Google Cloud OAuth Credentials**
1. Visit [Google Cloud Console](https://console.cloud.google.com/) and sign in with your Google account
2. Create a new project (or select an existing one)
3. In the left menu, click "APIs & Services" → "Enabled APIs & services"
4. Click "+ ENABLE APIS AND SERVICES", search for and enable [CalDAV API](https://console.cloud.google.com/apis/library/caldav.googleapis.com)
5. In the left menu, click "Credentials" → "+ CREATE CREDENTIALS" → "OAuth client ID"
* Select "Desktop app" for application type
* Enter "LifeOS" or any name you prefer
* After creation, copy the generated "Client ID" and "Client secret"
**Step 2: Configure Google Calendar**
1. In the calendar configuration page of the LifeOS Pro plugin settings, enable "Google Calendar Subscription"
2. Enter the "Client ID" and "Client Secret" obtained in the previous step
3. Click the "Connect" button, and a browser will open the Google authorization page
4. If you see "This app isn't verified" warning, click "Advanced" → "Go to LifeOS (unsafe)" to continue authorization
5. After successful authorization, click the "Refresh" button to fetch the calendar list, and select the default push calendar
**Google Sync Features**
* **Delete Completed Tasks**: When enabled, completed and cancelled tasks will be automatically deleted from Google Calendar
* **Reminder Settings**: Configure reminders separately for all-day events and timed tasks
* All-day event reminders: Set how many days in advance and the specific reminder time
* Timed task reminders: Set how many minutes/hours/days/weeks in advance to remind
:::tip About the "Not Verified" Warning
Due to Google's strict verification process for third-party applications, personally created OAuth apps will display this warning. This is normal and you can safely proceed with authorization, as this is your own app that only accesses the calendar data you authorize.
:::
### Subscribe to CalDAV Calendar
> CalDAV is a universal calendar sync protocol that allows you to view remote schedules in Obsidian. Some CalDAV services also support two-way sync (pushing tasks to remote calendars).
Supported platforms: Feishu, DingTalk, WeCom, Tencent Meeting, QQ Mail, etc.
:::warning Note: Feishu Calendar is Read-Only
Feishu CalDAV only supports **one-way sync (read-only)** and cannot push tasks to Feishu calendars via CalDAV protocol (PUT requests return 409 error). If you need phone reminders, please use iCloud Calendar, Google Calendar, or DingTalk Calendar as your "Default Write Calendar".
:::
**Using Feishu as an example (subscription/read-only):**
1. In the settings page of the "Feishu" desktop client, select calendar settings, click CalDAV sync configuration, select Other device, and generate the login username, password, and server address
2. In the calendar configuration page of the LifeOS Pro plugin settings, enable "CalDAV Calendar Subscription", and enter the username and generated password. The server address is `https://caldav.feishu.cn`
:::tip Common CalDAV Server Addresses
| Platform | Server Address |
| --------------- | --------------------------------- |
| Feishu | `https://caldav.feishu.cn` |
| DingTalk | `https://calendar.dingtalk.com` |
| WeCom | `https://caldav.wecom.work` |
| QQ Mail | `https://dav.qq.com` |
| Tencent Meeting | `https://cal.meeting.tencent.com` |
:::
**Adding Multiple CalDAV Configurations**
If you need to subscribe to multiple CalDAV calendars (e.g., both Feishu and DingTalk), click "Add CalDAV Configuration" to add additional CalDAV servers.
## Import from URL (ICS Subscription)
ICS calendar subscription is a universal calendar subscription method, subscribing to calendar events via URL address, in read-only mode.
### Subscribe to TickTick Tasks
1. Open TickTick, click on the avatar in the upper left corner to enter the settings page
2. Select "Connections & Import" from the left sidebar, then select "Subscribe to TickTick" on the right
3. Click "Get URL", select the list you want to subscribe to, and an ICS subscription URL will be generated
4. Go to the calendar configuration page in the LifeOS Pro plugin settings, enable "ICS Calendar Subscription", paste the previously generated URL link to complete the subscription
### Subscribe to iCloud Calendar (ICS Method)
> If you only need one-way viewing of iCloud Calendar, you can use the ICS method for simpler configuration.
1. Open the Mac client of Apple Calendar, select the calendar you want to sync from your iCloud account, right-click to bring up the menu, and select "Share Calendar"
2. Check the box in front of "Public Calendar"
3. Right-click again on the shared calendar, you will see the generated link address, copy the complete link
4. Go to the calendar configuration page in the LifeOS Pro plugin settings, enable "ICS Calendar Subscription", paste the previously generated URL link to complete the subscription
### Subscribe to Google Calendar (ICS Method)
> If you only need one-way viewing of Google Calendar, you can use the ICS method for simpler configuration without creating OAuth credentials.
1. Open Google Calendar, in the calendar list on the left, select the calendar you want to subscribe to, right-click to bring up the menu, and click "Settings and sharing"
2. In the calendar settings, find "Secret address in iCal format" under "Integrate calendar", and copy the complete link
3. Go to the calendar configuration page in the LifeOS Pro plugin settings, enable "ICS Calendar Subscription", paste the previously generated URL link to complete the subscription
### Subscribe to Outlook Calendar
1. Open the settings of your Outlook mailbox, click "Calendar" - "Shared calendars" - "Publish a calendar", select the calendar to share, and select "Can view all details". After selection, click "Publish"
2. After clicking "Publish", you will see the "ICS" link address, copy the complete link address
3. Go to the calendar configuration page in the LifeOS Pro plugin settings, enable "ICS Calendar Subscription", paste the previously generated URL link to complete the subscription
**Adding Multiple ICS Configurations**
If you need to subscribe to multiple ICS calendars, you can:
* Enter multiple addresses in the URL input box by line breaks
* Or click "Add ICS Configuration" to add additional configurations with custom names
---
url: /guide/pro/pomodoro.md
---
# Pomodoro Timer
The Pomodoro Timer is a built-in focus timing tool in LifeOS Pro, helping you better manage your time and improve work efficiency.
## Features
### Dual Timing Modes
* **Pomodoro Mode**: Traditional Pomodoro Technique, default 25 minutes focus + 5 minutes break
* **Stopwatch Mode**: Free timing, manually stop to record duration
### Project Association
You can associate timing with a project or theme. After completion, the time spent is automatically recorded to your daily note's project list, making your time statistics more accurate.
### Automation Options
* **Auto Start Break**: Automatically enter break time after completing a pomodoro
* **Auto Start Next Pomodoro**: Automatically start the next pomodoro after break ends
* **Auto Focus Count**: Set the number of consecutive pomodoros to complete before stopping the auto flow
### Mini Timer
During timing, you can minimize to a floating mini timer, allowing you to view progress while working on other pages. The mini timer supports drag-and-drop positioning.
## How to Use
### Open Pomodoro Timer
Click the tomato icon in the sidebar to open the Pomodoro Timer panel.
### Start Timing
1. Select timing mode (Pomodoro or Stopwatch)
2. Click "Focus >" to select a project to associate (optional)
3. Click the "Start" button to begin timing
### Timer Settings
Click the settings icon on the right side of the Pomodoro Timer panel to customize:
* Pomodoro duration (default 25 minutes)
* Short break duration (default 5 minutes)
* Long break duration (default 15 minutes)
* Long break interval (default after 4 pomodoros)
* Auto options (auto break, auto next pomodoro, auto focus count)
* Sound notification toggle
### Time Recording
After completing a pomodoro, if associated with a project, the time spent is automatically recorded to the project list in your daily note:
```markdown
## Project List
1. [[Work Project.README|Work Project]] 0hr25
2. [[Personal Growth.README|Personal Growth]] 1hr30
1hr55
```
## Statistics
The right side of the Pomodoro Timer panel displays statistics:
* **Today's Pomodoros**: Number of pomodoros completed today
* **Today's Focus Time**: Total focus time today
* **Total Pomodoros**: Historical total completed pomodoros
* **Total Focus Time**: Historical total focus time
Below, a focus record list is displayed, grouped by date showing the time period and duration of each focus session.
## Integration with Time Management
The Pomodoro Timer integrates perfectly with LifeOS's [Time Management](/guide/free/time-management.md) feature:
1. Use the Pomodoro Timer to record time spent on each project
2. Time is automatically aggregated to the project list in your daily notes
3. Weekly, monthly, quarterly, and yearly notes automatically calculate the time proportion for each project
This way, you can clearly understand "where your time went" and more efficiently adjust and plan your time!
---
url: /guide/pro/advanced-list.md
---
# Advanced Lists
Each theme (PARA) has an index file (ending with .README or with the same name as the folder). In this index file, there are three types of advanced lists: "Theme Tasks", "Theme Bullets", and "Theme Files". These are used to index "Theme Tasks", "Theme Bullets", and "Theme Files" that are "tagged with the current theme tag" scattered throughout the entire repository!
## Creation
### Creating "Theme Tasks", "Theme Bullets", "Theme Files" through Advanced Lists
#### Creating "Theme Tasks"
#### Creating "Theme Bullets"
#### Creating "Theme Files"
### Creating "Theme Tasks", "Theme Bullets", "Theme Files" in Notes
In periodic notes "Daily", "Weekly", "Monthly", "Quarterly", "Yearly", you can create them through the following methods:
#### Creating "Theme Tasks"
As long as you tag a task with the corresponding theme tag, that task will be indexed by the "Advanced List" task list
#### Creating "Theme Bullets"
As long as you tag a bullet with the corresponding theme tag, that bullet will be indexed by the "Advanced List" bullet list
#### Creating "Theme Files"
As long as you tag a file with the corresponding theme tag, that file will be indexed by the "Advanced List" file list
## Search
Advanced lists support full-text search, allowing you to quickly locate entries containing keywords.
## Filter
Filter by status, priority, and other conditions. Filter states are automatically saved and restored when you reopen.
## Sort
Click on column headers to sort in ascending or descending order.
## Copy
Advanced lists provide two copy formats:
* **Copy as Table**: Copy current page data as Markdown table format
* **Copy as List**: Copy current page data as Markdown list format
## Column Settings
Click the settings icon to customize displayed columns:
* Check/uncheck to show/hide columns
* The first column (main column) is always visible and cannot be hidden
* Supports select all/deselect all shortcuts
* Column configuration is automatically saved
## Column Width Adjustment
Drag the column header edges to adjust column width. Adjusted widths are automatically saved.
## Pagination
Supports paginated display with options to show 10, 50, or all data per page.
## Remote Task Sync
The task list supports displaying sync status with remote calendars (iCloud/CalDAV), helping you understand whether tasks have been pushed to remote calendars.
---
url: /guide/pro/convenient.md
---
# Convenience Features
## Automatically Insert Timestamps in Daily Records
### Enable the Switch
> This feature is enabled by default
### Trigger Method
## Right-click on Tags to Create Theme Notes
If a tag already has a corresponding theme, right-clicking can also directly jump to the theme note's index!
## Click on Folders to Jump to Theme Index Files
### Enable the Switch
> This feature is enabled by default
Click on the folder name, click on the blank area and click on the folder icon are still expanding the folder!
### Trigger Method
## Right-click on Theme Folders to Quickly Circulate
Right-click on any 'theme folder' can make the folder freely circulate between 'project', 'field', 'resource', and 'archive' directories, they are all themes!
## Click on File Title to Expand and Focus on Sidebar Files
> This feature is enabled by default
## When Opening Today's Daily Note, Automatically Focus on the Last Line of the Daily Record Module
> This feature is enabled by default
---
url: /guide/best-practice/project-life-cycle.md
---
# The Complete Life Cycle of a Project
How to use Obsidian for project management? Here, I'll use the "Writing LifeOS Tutorial" project as an example.
When I decided to write a tutorial about LifeOS, and after evaluation, decided to manage and implement it as a "project";
First, I opened Obsidian and created a "Personal Brand/LifeOS-Tutorial-Writing" project through the "Theme Notes" form in the upper left corner, where "Personal Brand" is the "Area";
Then I set a deadline for the project and described in detail the results I expected. When the expected results are achieved, the project can be checked as completed and moved to the "Archive" folder;
Afterward, in my daily notes, I recorded all ideas and inspirations about this "Personal Brand/LifeOS-Tutorial-Writing" project, while also listing some tasks to be done, and tagging these records with the corresponding "project" tag, i.e., "#Personal Brand/LifeOS-Tutorial-Writing";
When I have a block of time to focus on this project, I sit down and open the "LifeOS-Tutorial-Writing.README" file in the "Projects" folder. Browsing through all the records about the project in the "Tasks" and "Lists" modules not only helps me quickly enter the project context but also assists me in taking the next steps!
---
url: /guide/best-practice/custom-workflow.md
---
# Custom Workflow
Based on the theme note's "Input → Processing → Output" framework, through a unique theme tag system!
You can turn off PARA mode, or start from the [IPO Example Vault](/guide/overview/usage.md#lifeos-pro-ipo-vault) / [GTD Example Vault](/guide/overview/usage.md#lifeos-pro-gtd-vault) and adapt it.
## IPO Knowledge Management Vault
Based on the [IPO Example Vault](/guide/overview/usage.md#lifeos-pro-ipo-vault), create a simplified knowledge management system.
### What is the IPO Model
In knowledge management, IPO typically refers to the process of Input, Processing, and Output. This model describes the entire journey of knowledge from acquisition and processing to application.
In the IPO model:
1. **Input**: This marks the starting point of knowledge management, involving the collection and acquisition of information. Input can include data, documents, research, personal experiences, external information, etc. The quality of input is crucial to the entire knowledge management process.
2. **Processing**: At this stage, the input information is analyzed and refined to make it useful and applicable. Processing activities may include analysis, synthesis, evaluation, interpretation, storage, and sharing of knowledge. The goal of this phase is to transform raw data and information into valuable knowledge.
3. **Output**: This is the final stage of knowledge management, where processed knowledge is applied to real-world problems to create value. Output can include decisions, solutions, new products, improved processes, training materials, etc.
Can be simply understood as a simplified version of the [CODE](/guide/intro/second-brain.md#code-model)/[PARA](/guide/intro/second-brain.md#para-organization) practice, it greatly reduces the entry threshold for beginners. Users only need to focus on input, output, and themes, and easily record, organize, and use notes.
### Core Structure
1. **Input System**:
* Store all collected information, materials, and inspirations in the '1. Input' directory
* Use theme tags to associate related content, such as `#ReadingNotes/BookTitle`, `#LearningMaterials/CourseName`
2. **Processing Flow**:
* Create theme notes in the '2. Themes' directory to deeply process input content
* Build knowledge association networks through theme tags
* Use "Canvas View" or "Advanced Lists" to organize knowledge structures
3. **Output System**:
* Store final results in the '3. Output' directory
* Output can be articles, reports, project deliverables, speeches, etc.
* Quickly find related input and processing content through reverse indexing via theme tags
### Advantages
* **Simple and Easy**: No need to understand complex PARA systems, just focus on three core stages
* **Flexible and Customizable**: Adjust the content and usage of the three directories according to personal needs
* **Theme-Focused**: Organize knowledge around themes, which aligns better with how our brains think
* **Easy to Get Started**: Particularly suitable for knowledge management beginners to quickly build their own note system
## GTD Action Management Vault
Based on the [GTD Example Vault](/guide/overview/usage.md#lifeos-pro-gtd-vault), you can build an execution-first system focused on moving work forward.
### What is the GTD Model
GTD (Getting Things Done) externalizes commitments into a trusted system and keeps the next action visible. It does not require every note to be sorted into PARA on day one. It first makes sure tasks can be captured, clarified, executed, and reviewed.
### Core Structure
1. **Inbox**:
* `1. Inbox` stores unclarified ideas, tasks, and material
* These items usually start with `#gtd/inbox`
2. **Action System**:
* `2. Actions/Next Actions` aggregates `#gtd/next`
* `2. Actions/Waiting For` aggregates `#gtd/waiting`
* `2. Actions/Someday Maybe` keeps possibilities that are not active now
3. **Project System**:
* `3. Projects` stores outcomes that need more than one action
* Every active project should keep at least one `#gtd/next` or `#gtd/waiting` item
4. **Reference, Reviews, and Archive**:
* `4. Reference` stores useful material that is not directly actionable
* `5. Reviews` holds weekly reviews, monthly reviews, and system cleanup
* `6. Archive` stores completed or paused material
### Tag Design
The GTD vault uses two kinds of tags:
* `#gtd/next`, `#gtd/waiting`, `#gtd/someday`, and `#gtd/inbox` describe task state
* `#ctx/deep-work`, `#ctx/computer`, `#ctx/call`, `#ctx/errand`, `#ctx/home`, and `#ctx/mobile` describe execution context
This lets you choose work by state and context first, then return to the project note for full background.
## Media Creator's Vault
### Core Structure
1. **Content Workshop**:
* Topic management uses the `demand pool` theme tag, such as theme #PhoneReview/iPhone16
* Use "Canvas View" to build content script frameworks
2. **Production Pipeline**:
* Each video production is broken down into `storyboard script → shooting list → editing project` sub-themes, such as
* \#PhoneReview/iPhone16/StoryboardScript
* \#PhoneReview/iPhone16/ShootingList
* \#PhoneReview/iPhone16/EditingProject
3. **Content Output**:
* Finally, store the finished products in the output directory
## Academic Vault
### Core Structure
1. **Input System**:
* Literature abstracts use `Literature ID#article` theme tags for automatic association
* Experimental data is dynamically indexed through templates using `Dataset ID#dataset`
2. **Processing Flow**:
* Each research direction serves as an independent theme (e.g., `#QuantumComputing-OpticalQuantumRoute`)
* Use the "Advanced Lists" feature to perform topological sorting of literature citation relationships
3. **Output System**:
* Paper drafts automatically aggregate reference materials (through reverse indexing via theme tags)
* Track submission progress and review cycles through the "Home View"
## Sales Vault
### Core Structure
1. **Customer Management System**:
* Set `#Customer-CompanyA` theme tag for each customer
* Automatically generate "Customer Profile Timeline" to display communication records
2. **Business Process Tracking**:
* Opportunity follow-up uses `Stage:RequirementConfirmation[75%]` progress tags
* "Big Calendar View" plans customer visit schedules
3. **Data Analysis Module**:
* Sales funnel is broken down by region/product line through "Filter View"
* Performance weekly reports automatically extract KPI data from theme notes
---
url: /guide/best-practice/calendar-sub.md
---
# Calendar Subscription
For detailed configuration methods, please refer to the documentation: [Calendar Subscription](/guide/pro/calendar-sub.md#calendar-subscription). Here we mainly recommend some interesting practices!
Besides being used for tasks, with ICS URL subscription, we can also achieve the following functions!
## Holidays
> Original source: https://github.com/lanceliao/china-holiday-calender
Holiday ICS URL: https://www.shuyz.com/githubfiles/china-holiday-calender/master/holidayCal.ics
Work day adjustment ICS URL: webcal://calendars.icloud.com/holidays/cn\_zh.ics
## Weather Forecast
> Original source: https://github.com/Moli-X/Calendar?tab=readme-ov-file
### **City List**
| No. | City Name | Subscription Link |
| --- | ------------ | ---------------------------------------------------------------------------------------------------------------------- |
| 1 | Anqing | [Anqing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/anqing/anqing.ics) |
| 2 | Anshun | [Anshun Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/anshun/anshun.ics) |
| 3 | Anshan | [Anshan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/anshan/anshan.ics) |
| 4 | Anzhou | [Anzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/anzhou/anzhou.ics) |
| 5 | Beijing | [Beijing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/beijing/beijing.ics) |
| 6 | Baoding | [Baoding Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/baoding/baoding.ics) |
| 7 | Baotou | [Baotou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/baotou/baotou.ics) |
| 8 | Bengbu | [Bengbu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/bengbu/bengbu.ics) |
| 9 | Bazhong | [Bazhong Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/bazhong/bazhong.ics) |
| 10 | Bozhou | [Bozhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/bozhou/bozhou.ics) |
| 11 | Chongqing | [Chongqing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/chongqing/chongqing.ics) |
| 12 | Changchun | [Changchun Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/changchun/changchun.ics) |
| 13 | Changsha | [Changsha Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/changsha/changsha.ics) |
| 14 | Chengdu | [Chengdu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/chengdu/chengdu.ics) |
| 15 | Chuzhou | [Chuzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/chuzhou/chuzhou.ics) |
| 16 | Dalian | [Dalian Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/dalian/dalian.ics) |
| 17 | Dongguan | [Dongguan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/dongguan/dongguan.ics) |
| 18 | Dandong | [Dandong Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/dandong/dandong.ics) |
| 19 | Dezhou | [Dezhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/dezhou/dezhou.ics) |
| 20 | Dongying | [Dongying Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/dongying/dongying.ics) |
| 21 | Fuzhou | [Fuzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/fuzhou/fuzhou.ics) |
| 22 | Foshan | [Foshan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/foshan/foshan.ics) |
| 23 | Fuyang | [Fuyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/fuyang/fuyang.ics) |
| 24 | Fujian | [Fujian Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/fujian/fujian.ics) |
| 25 | Fushun | [Fushun Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/fushun/fushun.ics) |
| 26 | Guangzhou | [Guangzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/guangzhou/guangzhou.ics) |
| 27 | Guizhou | [Guizhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/guizhou/guizhou.ics) |
| 28 | Guilin | [Guilin Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/guilin/guilin.ics) |
| 29 | Gansu | [Gansu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/gansu/gansu.ics) |
| 30 | Guangxi | [Guangxi Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/guangxi/guangxi.ics) |
| 31 | Hangzhou | [Hangzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/hangzhou/hangzhou.ics) |
| 32 | Hefei | [Hefei Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/hefei/hefei.ics) |
| 33 | Hebei | [Hebei Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/hebei/hebei.ics) |
| 34 | Hainan | [Hainan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/hainan/hainan.ics) |
| 35 | Hunan | [Hunan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/hunan/hunan.ics) |
| 36 | Jinan | [Jinan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/jinan/jinan.ics) |
| 37 | Jiujiang | [Jiujiang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/jiujiang/jiujiang.ics) |
| 38 | Jiangxi | [Jiangxi Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/jiangxi/jiangxi.ics) |
| 39 | Jiangsu | [Jiangsu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/jiangsu/jiangsu.ics) |
| 40 | Jilin | [Jilin Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/jilin/jilin.ics) |
| 41 | Kunming | [Kunming Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/kunming/kunming.ics) |
| 42 | Kaiyuan | [Kaiyuan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/kaiyuan/kaiyuan.ics) |
| 43 | Kaili | [Kaili Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/kaili/kaili.ics) |
| 44 | Lianyungang | [Lianyungang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/lianyungang/lianyungang.ics) |
| 45 | Lijiang | [Lijiang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/lijiang/lijiang.ics) |
| 46 | Longyan | [Longyan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/longyan/longyan.ics) |
| 47 | Liangping | [Liangping Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/liangping/liangping.ics) |
| 48 | Luzhou | [Luzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/luzhou/luzhou.ics) |
| 49 | Meizhou | [Meizhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/meizhou/meizhou.ics) |
| 50 | Mianyang | [Mianyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/mianyang/mianyang.ics) |
| 51 | Macau | [Macau Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/macau/macau.ics) |
| 52 | Nanjing | [Nanjing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/nanjing/nanjing.ics) |
| 53 | Nanchang | [Nanchang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/nanchang/nanchang.ics) |
| 54 | Nanning | [Nanning Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/nanning/nanning.ics) |
| 55 | Nanyang | [Nanyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/nanyang/nanyang.ics) |
| 56 | Ningbo | [Ningbo Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/ningbo/ningbo.ics) |
| 57 | Pingdingshan | [Pingdingshan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/pingdingshan/pingdingshan.ics) |
| 58 | Pingxiang | [Pingxiang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/pingxiang/pingxiang.ics) |
| 59 | Putian | [Putian Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/putian/putian.ics) |
| 60 | Pingyang | [Pingyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/pingyang/pingyang.ics) |
| 61 | Qingdao | [Qingdao Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/qingdao/qingdao.ics) |
| 62 | Qinghai | [Qinghai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/qinghai/qinghai.ics) |
| 63 | Qinhuangdao | [Qinhuangdao Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/qinhuangdao/qinhuangdao.ics) |
| 64 | Qinzhou | [Qinzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/qinzhou/qinzhou.ics) |
| 65 | Shenzhen | [Shenzhen Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/shenzhen/shenzhen.ics) |
| 66 | Shanghai | [Shanghai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/shanghai/shanghai.ics) |
| 67 | Suzhou | [Suzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/suzhou/suzhou.ics) |
| 68 | Shijiazhuang | [Shijiazhuang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/shijiazhuang/shijiazhuang.ics) |
| 69 | Shaoxing | [Shaoxing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/shaoxing/shaoxing.ics) |
| 70 | Tianjin | [Tianjin Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/tianjin/tianjin.ics) |
| 71 | Taiyuan | [Taiyuan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/taiyuan/taiyuan.ics) |
| 72 | Taizhou | [Taizhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/taizhou/taizhou.ics) |
| 73 | Tonghua | [Tonghua Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/tonghua/tonghua.ics) |
| 74 | Taian | [Taian Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/taian/taian.ics) |
| 75 | Wuhan | [Wuhan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/wuhan/wuhan.ics) |
| 76 | Wenzhou | [Wenzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/wenzhou/wenzhou.ics) |
| 77 | Weifang | [Weifang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/weifang/weifang.ics) |
| 78 | Wuhu | [Wuhu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/wuhu/wuhu.ics) |
| 79 | Wuxu | [Wuxu Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/wuxi/wuxi.ics) |
| 80 | Xi'an | [Xi'an Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xi'an/xi'an.ics) |
| 81 | Xiamen | [Xiamen Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xiamen/xiamen.ics) |
| 82 | Xingtai | [Xingtai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xingtai/xingtai.ics) |
| 83 | Xiangyang | [Xiangyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xiangyang/xiangyang.ics) |
| 84 | Xuzhou | [Xuzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xuzhou/xuzhou.ics) |
| 85 | Yantai | [Yantai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yantai/yantai.ics) |
| 86 | Yichang | [Yichang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yichang/yichang.ics) |
| 87 | Yinchuan | [Yinchuan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yinchuan/yinchuan.ics) |
| 88 | Yuxi | [Yuxi Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yuxi/yuxi.ics) |
| 89 | Yibin | [Yibin Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yibin/yibin.ics) |
| 90 | Yuncheng | [Yuncheng Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yuncheng/yuncheng.ics) |
| 91 | Zhuhai | [Zhuhai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhuhai/zhuhai.ics) |
| 92 | Zhengzhou | [Zhengzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhengzhou/zhengzhou.ics) |
| 93 | Zunyi | [Zunyi Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zunyi/zunyi.ics) |
| 94 | Zhongshan | [Zhongshan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhongshan/zhongshan.ics) |
| 95 | Zibo | [Zibo Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zibo/zibo.ics) |
| 96 | Zhoukou | [Zhoukou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhoukou/zhoukou.ics) |
| 97 | Zhangjiajie | [Zhangjiajie Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhangjiajie/zhangjiajie.ics) |
| 98 | Zhangzhou | [Zhangzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhangzhou/zhangzhou.ics) |
| 99 | Zhenjiang | [Zhenjiang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhenjiang/zhenjiang.ics) |
| 100 | Zhumadian | [Zhumadian Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhumadian/zhumadian.ics) |
| 101 | Zhongwei | [Zhongwei Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhongwei/zhongwei.ics) |
| 102 | Zigong | [Zigong Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zigong/zigong.ics) |
| 103 | Zhanjiang | [Zhanjiang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhanjiang/zhanjiang.ics) |
| 104 | Zhangye | [Zhangye Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhangye/zhangye.ics) |
| 105 | Zhangjiakou | [Zhangjiakou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhangjiakou/zhangjiakou.ics) |
| 106 | Zhoushan | [Zhoushan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhoushan/zhoushan.ics) |
| 107 | Zhuji | [Zhuji Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhuji/zhuji.ics) |
| 108 | Zhanghe | [Zhanghe Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhanghe/zhanghe.ics) |
### **New Areas**
| No. | City Name | Subscription Link |
| --- | --------- | ------------------------------------------------------------------------------------------------------------- |
| 1 | Shantou | [Shantou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/shantou/shantou.ics) |
| 2 | Kaifeng | [Kaifeng Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/kaifeng/kaifeng.ics) |
| 3 | Leshan | [Leshan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/leshan/leshan.ics) |
| 4 | Changzhou | [Changzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/changzhou/changzhou.ics) |
| 5 | Tianmen | [Tianmen Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/tianmen/tianmen.ics) |
| 6 | Nantong | [Nantong Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/nantong/nantong.ics) |
| 7 | Deyang | [Deyang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/deyang/deyang.ics) |
| 8 | Zhaoqing | [Zhaoqing Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/zhaoqing/zhaoqing.ics) |
| 9 | Longquan | [Longquan Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/longquan/longquan.ics) |
| 10 | Xuchang | [Xuchang Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/xuchang/xuchang.ics) |
| 11 | Yancheng | [Yancheng Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/yancheng/yancheng.ics) |
| 12 | Suzhou | [Suzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/suzhoujs/suzhoujs.ics) |
| 13 | Huzhou | [Huzhou Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/huzhou/huzhou.ics) |
| 14 | Weihai | [Weihai Weather Subscription](https://github.com/Moli-X/Calendar/raw/main/Weather/weihai/weihai.ics) |
# 3x3
> App How to obtain: https://www.today3x3.com/
The 3x3 App can write events/tasks directly into the system calendar, so you only need to subscribe to the Apple calendar. Subscription methods:
Method 1: [Import from CalDAV Account](/guide/pro/calendar-sub.md#import-from-caldav-account)
Method 2: [Import from URL](/guide/pro/calendar-sub.md#import-from-url-ics-subscription)
Apple system calendar display effect
LifeOS Pro big calendar display effect
---
url: /guide/best-practice/how-review.md
---
# How I Review
Reviews mainly focus on tasks, projects, or goals within the current period, while simultaneously planning tasks, projects, or goals for the next period!
---
url: /guide/best-practice/usememos-sync.md
---
# Usememos Synchronization
Since Usememos synchronization involves "service deployment," it is considered a very advanced feature. Generally, you need to have a "development background" to complete it!
Assuming you have already deployed the Usememos service, and the service address is www.your-memos.com; then, open that address, log in to the Usememos service via the web interface, and follow the instructions in the image below to generate an Access Token:
Next, open the LifeOS settings page and fill in the API and Token according to the image below:
By default, Usememos will automatically synchronize once when you first enter Obsidian, and then automatically synchronize every half hour afterward. Additionally, you can click the sidebar icon to perform manual synchronization:
---
url: /guide/best-practice/thino.md
---
# Integration with Thino
> Reference document: [Obsidian Knowledge Management | Integrating Thino into the LifeOS System](https://www.xiaohongshu.com/explore/66266aed0000000004019a8a?xsec_token=ABZ6tAKfTHhJA6u25rzihYT30DaUqSjUjixvb565MihRA%3D\&xsec_source=pc_search\&source=web_profile_page)
Use Thino's WeChat recording feature to replace LifeOS's Usememos!
---
url: /guide/ai-integration/deepask.md
---
import { CommercialContent } from '../../../../theme/components/CommercialContent';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
# Pro Features Overview
> Deep Ask Plugin Quick Start Guide
Get link: [Deep Ask](./pricing.mdx)
## 📖 Introduction
Deep Ask is a powerful Obsidian AI chat plugin designed to enhance your knowledge management experience. By integrating multiple AI models and local CLI agents, Deep Ask can understand your note content, support Codex CLI or Claude Code CLI, and provide intelligent question-answering, content generation, and knowledge retrieval.
***
***
## 🌐 Chrome Extension
Deep Ask now offers a Chrome browser extension, allowing you to seamlessly use AI assistant features while browsing the web!
**Download**: [Chrome Web Store - DeepAsk AI](https://chromewebstore.google.com/detail/deepask-ai/abhoenehflglmgbohaibihggedfcpcep) · [Stable Feishu link: Chrome / Edge manual package (ZIP)](https://www.feishu.cn/file/CyLIblv2OowEi4xHDPwcWC9MnNc)
### Manual installation (Chrome / Edge)
1. Download the ZIP and extract it to a folder you will keep.
2. Open `chrome://extensions` in Chrome or `edge://extensions` in Microsoft Edge.
3. Enable **Developer mode**, choose **Load unpacked**, and select the extracted folder.
4. Keep the DeepAsk Obsidian plugin enabled, then open the DeepAsk extension from the browser toolbar.
The Feishu package uses a stable link and is replaced in place when a new version is released.
### Key Features
* **Integration with Obsidian**: Supports linking tags, context, and files from Obsidian to initiate Q\&A on the current webpage
* **Webpage Content Conversation**: Directly chat with the content of the current webpage
* **Codex CLI and Claude Code CLI**: Supports Codex CLI or Claude Code CLI, while the Chrome extension adds webpage context into the same DeepAsk workflow
* **Visible Reply Feedback**: Shows a temporary animated reply placeholder before the first streaming token arrives
* **Cross-platform Collaboration**: Seamlessly switch between browser and Obsidian for a complete knowledge management workflow
***
***
## ✨ Main Features
* 🤖 **Multi-model and SDK Support**：Support OpenAI-compatible providers and Anthropic SDK configuration, including GPT, Gemini, DeepSeek, Qwen, Kimi, Claude, Ollama, etc.
* 🧑💻 **Codex CLI and Claude Code CLI**：Supports Codex CLI or Claude Code CLI, with Chrome extension webpage context available in the same workflow
* 💻 **Real-time Content Conversation**：Automatically understand your note structure and content, support conversation with current notes and webpages
* 🏷️ **Tag Integration**：Context collection based on tags, intelligent content retrieval
* 📎 **File Attachment**：Support adding note files as context
* 🤖 **Professional Prompt Selection**：Built-in professional prompt library to enhance conversation quality
* 🗓 **Time Range Limitation**：Support filtering context content by time range
* 📷 **Creative Poster Generation**：AI generates HTML-formatted posters with preview and download support
* 💡 **Quick Suggestions**：Intelligent recommendation of common conversation templates
* 💬 **Streaming conversation with reply placeholder**：Real-time response, conversation history management, and an animated preparing-reply bubble before content arrives
* 🔄 **Multi-session management**：Support creating multiple conversation topics
* 🌍 **Multi-language support**：Support Chinese and English interfaces
* 🧩 **LifeOS Skill (recommended)**：Install LifeOS Skill first so AI agents can understand and operate your LifeOS vault; the built-in MCP server remains available for MCP-compatible clients
## 🚀 Quick Start
### Step 1: Install Prerequisites
Deep Ask depends on the **Dataview plugin**, please ensure it is installed and enabled:
1. Open Obsidian settings
2. Enter the "Community plugins" section
3. Search and install **Dataview**
4. Enable Dataview plugin
### Step 2: Install Deep Ask Plugin
1. Download the plugin file to the Obsidian plugin directory, usually in your repository's `.obsidian/plugins` directory
2. Restart Obsidian
3. Enable Deep Ask in the plugin list
### Step 3: Activate the Plugin
1. Open the plugin settings page
2. Enter the "Activation" tab
3. Enter your account email and activation code
## ⚙️ Configuration Guide
### AI Model Configuration
In the "AI Model" tab of the settings page, you can configure the supported AI services:
Here is an example of configuring the DeepSeek model:
#### 🔵 DeepSeek Configuration
Fill in the API Key, and then click the AI Model, and select the specific model to enable:
You can also customize the AI model configuration:
#### 🟢 Custom Configuration
You can customize the AI model configuration, supporting the following parameters:
* **Base URL**：The base URL of the AI service
* **API Key**：The API Key of the AI service
* **AI Model**：The supported models of the AI service
### Local CLI safety boundaries
When you select Codex CLI or Claude Code CLI, DeepAsk resolves the execution policy before launching the process. Local CLIs cannot reuse the plugin's per-tool diff, approval, and undo protocol, so their boundary is intentionally stricter than ordinary API models.
| Current mode | Local CLI behavior |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ask | Always runs in a read-only sandbox and can only analyze or answer. |
| Edit | Runs read-only and returns a proposed change; it does not write files directly. |
| Structured workflow | Runs read-only so a workflow cannot bypass the host review protocol. |
| Agent | Can modify files only when both write and delete permissions are enabled and you approve whole-vault access for that turn; otherwise it remains read-only. |
DeepAsk records the selected policy as tool activity. If you reject whole-vault access, the CLI is not launched; rejection and execution failures remain visible in the activity state. Ask, Edit, and structured workflows never become writable just because mutation settings are enabled.
:::warning Whole-vault access
After approval, the local CLI may modify or delete files anywhere in the current vault for that turn. Approve only when the request is well scoped and your data is backed up or recoverable. When uncertain, stay read-only or use a test vault first.
:::
Local CLIs require a desktop Node.js process and are unavailable in Obsidian Mobile. Mobile users can continue using configured API models and the plugin's embedded tools.
### AI Context Configuration
* **Maximum conversation rounds**：Set the number of conversation history to retain
* **Temperature**：Set the randomness of AI replies, the lower the more stable, the higher the more random
* **Exclude files with matching tags**：Generally used to filter periodic notes and template notes. The former has already queried flash notes in periodic notes through tags (duplicate context), and the latter are various template notes (invalid context)
* **Use current opened file only**：Only use the currently opened file as context, ignore all other files opened in the background
* **LifeOS Integration Config**：Configure file search strategy when using LifeOS with AI features
* **Theme Note File Search**：Select how AI searches theme-related files
* **Include index files only**：Only include index files
* **Include entire folder**：Include entire folder
* **Recursive Sub-theme Search**：Enable recursive search for sub-themes within the selected theme tags
### Conversation Settings
* **Maximum conversation rounds**：Set the number of conversation history to retain
* **Temperature**：Set the randomness of AI replies, the lower the more stable, the higher the more random
## 🎯 Usage Guide
### Launching the Chat Interface
There are several ways to open the AI chat:
1. **Toolbar button**：Click the Deep Ask AI icon in the sidebar
2. **Command Palette**：`Ctrl/Cmd + P` search "Deep Ask AI Chat"
3. **Shortcut**：Can be customized in settings
### Basic Conversation
1. Enter your question in the chat interface at the bottom
2. Select the AI model (if multiple are configured)
3. Click Send or press Enter to send
4. AI will reply to your question in real-time
### Advanced Features
#### 💻 Real-time Content Conversation
* Directly chat with the currently opened file and webpage, supporting multiple files and webpages as context, and linking with existing notes
#### 📎 File Attachment
* Trigger file search by typing /, select the file to add to the context
* The opened file will be automatically added to the context
#### 🏷️ Tag Integration
* Trigger tag search by typing #, select the tag to add to the context
* DeepAsk will automatically search for all records in the vault, including tasks, flash notes, and files with the selected tag
#### 🤖 Professional Prompt Selection
* Enter / to trigger prompt search, select the prompt to add to the context
* DeepAsk will display a list of prompt files in the specified directory for selection
#### 🧩 LifeOS Skill And MCP Compatibility For Ordinary Models
DeepAsk ordinary model chat can use agent skills and MCP tools without switching to Claude Code / Codex CLI mode. For LifeOS vault work, use LifeOS Skill first; it carries LifeOS-specific workflows and follows your vault settings. MCP remains available when a client specifically needs protocol-level tool access.
* Recommended: type `!lifeos your request` or `$lifeos your request` to explicitly invoke the installed LifeOS Skill
* If it is not installed yet, install it from [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) or from the AI Connect settings tab
* Models can also call `deepask_list_skills` / `deepask_read_skill` to inspect installed skills
* Read/query embedded MCP tools remain available as the compatibility path, including file reading, task search, tag search, and periodic-note lookup
* On desktop, DeepAsk can still load external MCP servers from `.mcp.json`, `~/.claude/mcp.json`, and `~/.config/claude/mcp.json`
* Write, update, and delete tools are disabled by default and can be enabled from AI Connect
#### 🗓 Time Range Limitation
* Enter /2025-08-22 to trigger time range limitation
* DeepAsk will automatically limit all matching context (files, tags) to the specified time range
#### 📷 Creative Poster Generation
* Require AI to generate HTML-formatted posters
* Click the "eye" preview button below the AI reply to view and download the poster
#### 💬 Session Management
* Click "+" to create a new conversation
* Each conversation manages the context independently
#### ✏️ Message Editing
* Hover to display the edit button
* Support editing the sent message, triggering AI to regenerate the reply
* Support clicking the regenerate button next to the message, triggering AI to regenerate the reply
#### 💾 Download AI Conversation
* Click the plus button next to the message, and the AI reply will be appended to the current note
* Click the download button in the lower right corner of the dialog, and the entire conversation will be downloaded as a Markdown file
### 💡 Quick Suggestions
In the blank conversation, Deep Ask will display commonly used suggestions:
* /2025-08-22 Summarize today's diary?
* \#SwapHouse What are the good and bad things I did?
* \#HistoryCycle Summarize this tag?
## 🔌 MCP Server
Recommended path: use [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) first for Claude Code, Codex, and other skill-aware agents. The skill understands LifeOS-specific folders, templates, daily notes, tasks, and review workflows without requiring manual MCP server configuration.
Deep Ask also includes a built-in MCP (Model Context Protocol) server for tools that require MCP compatibility, allowing clients like Claude Desktop or Cursor to access your Obsidian vault through a local protocol endpoint.
### What is MCP?
MCP (Model Context Protocol) is an open protocol that allows AI applications to securely connect to external data sources and tools. In LifeOS workflows, treat MCP as the compatibility layer; if your AI agent can install skills, LifeOS Skill is the recommended entry point.
### Recommended: LifeOS Skill
For Claude Code, Codex, and other skill-aware agents, install LifeOS Skill:
```bash
npx skills add quanru/lifeos-skill
```
Then ask the agent:
```text
Check my lifeos configuration
```
Continue with MCP configuration only when your client specifically connects through MCP.
### MCP Compatibility Configuration
#### Claude Desktop MCP Compatibility Configuration
1. Make sure the Deep Ask plugin is enabled and running
2. Open the Claude Desktop configuration file:
* **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
3. Add the following configuration:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
4. Restart Claude Desktop
#### Cursor MCP Compatibility Configuration
If Cursor cannot use LifeOS Skill for this workflow, add the MCP server in Cursor settings:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
#### Claude Code MCP Compatibility Configuration
For Claude Code, LifeOS Skill is the recommended path. Create a `.mcp.json` file in your project root only when you need MCP compatibility:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
### Available Tools
When you use LifeOS Skill, ask for these operations in natural language. If you must use MCP compatibility, the server exposes the following underlying tools for AI assistants:
#### File Operations
| Tool Name | Description |
| ------------------ | ----------------------------------- |
| `get_file_content` | Get the content of a specified file |
| `list_files` | List files in the vault |
| `list_tags` | List all tags in the vault |
| `search_by_tag` | Search content by tag |
| `save_chat` | Save conversation to a note file |
#### Task CRUD Operations
| Tool Name | Description |
| ------------- | --------------------------------------------------------------------------- |
| `create_task` | Create a new task with optional due date, time range, and multi-day support |
| `list_tasks` | List tasks with filtering by date, status, tags, folder, and pagination |
| `update_task` | Update task content, date, time, or completion status |
| `delete_task` | Delete a task (including its sub-items) |
#### Bullet (Fleeting Note) CRUD Operations
| Tool Name | Description |
| --------------- | ----------------------------------------------------------------- |
| `create_bullet` | Create a new bullet (fleeting note) with optional tags |
| `list_bullets` | List bullets with filtering by date, tags, folder, and pagination |
| `update_bullet` | Update bullet content |
| `delete_bullet` | Delete a bullet (including its sub-items) |
#### Periodic Notes Query
| Tool Name | Description |
| -------------------- | ------------------------------------------------------------------------------------------- |
| `get_periodic_notes` | Get periodic notes (yearly/quarterly/monthly/weekly/daily) with optional sub-period support |
**Parameters**:
* `year` (required): Year, e.g., 2024
* `quarter`: Quarter (1-4)
* `month`: Month (1-12)
* `week`: ISO week number (1-53)
* `day`: Day of month (1-31, requires month)
* `includeQuarters`: Include quarterly notes (only for yearly)
* `includeMonths`: Include monthly notes (for yearly/quarterly)
* `includeWeeks`: Include weekly notes (for yearly/quarterly/monthly)
* `includeDays`: Include daily notes
* `includeContent`: Include note content (default: true)
* `includeVirtualDocument`: Include virtual document with query results
**Usage Examples**:
```
Get the 2024 yearly note
→ { year: 2024 }
Get June 2024 monthly note with all daily notes
→ { year: 2024, month: 6, includeDays: true }
Get Q2 quarterly note with monthly and weekly notes
→ { year: 2024, quarter: 2, includeMonths: true, includeWeeks: true }
```
### Use Cases
* **Knowledge Retrieval**: Use LifeOS Skill first to search your notes for relevant information; MCP-compatible clients can use the same vault data through the server
* **Content Summarization**: Have AI read and summarize your note content
* **Cross-tool Collaboration**: In IDEs like Cursor, use LifeOS Skill when available and MCP when the IDE requires protocol-level access
* **Automated Organization**: Let AI help organize and archive your notes
* **Task Management**: Create, query, update, and delete tasks directly through AI assistants
* **Quick Capture**: Record fleeting thoughts and ideas as bullets through AI without opening Obsidian
### Important Notes
* Make sure Obsidian is open and Deep Ask plugin is running
* The MCP server default port is `51377`; LifeOS Skill does not require configuring this port manually
* Authorization uses your Deep Ask activation code
* Only supports local access (127.0.0.1) for security
## 🛠️ Troubleshooting
### Common Issues
**Q: AI does not reply or reply incorrectly?**
A: Check if the API Key is correct, and the network connection is normal
**Q: Unable to find related note content?**\
A: Check if the path filtering is set correctly, and check if the Dataview plugin is working properly
**Q: Plugin startup failed?**
A: Check if the Obsidian version meets the requirements, and the Dataview plugin is installed
**Q: Activation code invalid?**
A: Check if the email and activation code are correct, and contact the developer for support
### Log Debugging
1. Open the developer tools (`Ctrl/Cmd + Shift + I`)
2. View the error information in the Console tab
3. Troubleshoot based on the error information
## 📚 Best Practices
1. **Organize knowledge structure**：Establish a clear folder and tag system to facilitate AI retrieval
2. **Use context reasonably**：Select related files and tags to improve answer quality
3. **Classify conversation**：Create independent conversations for different topics
## 🚀 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/deep-ask-changelog.md).
---
url: /guide/ai-integration/ai-coach.md
---
# AI Coach 🤖
## Coze Bot
* [Click me](https://www.coze.com/store/bot/7332330627976462344?bid=6ca5v9a74200i\&panel=1)
## Discord Bot
* [Click me](https://discord.gg/HZGanKEkuZ)
---
url: /guide/ai-integration/lifeos-skill.md
---
# LifeOS Skill: AI Can Manage My Notes
I wrote a skill for LifeOS, and now AI can help manage my notes.
I have used LifeOS for more than a year, and I still love the PARA + periodic notes system.
But one problem kept getting in the way: the friction of recording was too high.
An idea appears → open Obsidian → go to today's daily note → scroll to "Daily Record" → type → close it. Those few steps are enough for countless ideas to disappear into "I'll skip it this time."
So last month I built an AI skill for LifeOS.
:::tip The same Skill also supports the Aino path
LifeOS Skill helps AI understand and maintain a Markdown Vault. It works with the Obsidian + LifeOS Pro plugin path and also runs directly in Aino Desktop and Aino Mobile. See [Obsidian vs Aino](/guide/pro/aino-desktop.md), or follow the [Aino LifeOS Skill guide](https://aino.md/zh/guide/ai/lifeos-skill.html).
:::
## What is it?
In one sentence: after installing the LifeOS Skill Bundle, agents such as Claude Code and Codex learn how to operate your LifeOS vault.
The bundle contains five independently triggered Skills. `lifeos` owns shared configuration and safety rules; `lifeos-today` handles today and periodic reviews; `lifeos-board` handles Workflow/PARA boards; `lifeos-onboarding` handles setup and migration; and `lifeos-content` handles notes, attachments, AI Wiki, and dashboards. The agent loads only the domain rules needed for the current request.
It knows what your PARA folders are called, how your daily-note paths are formatted, where your templates live, and what section headings you use. It also honors the folder, date format, and template configured in Obsidian's core Daily Notes plugin. It reads all of that from your real configuration automatically, so you do not have to explain it manually.
You describe what you want in natural language, and the AI executes it.
The Skill is not limited to an Obsidian vault. It can also initialize or take
over any local Markdown folder while preserving images, PDF, DOC, PPT, audio,
video, and other attachments.
## What can it do?
### Quick capture in one sentence
"Log to today's journal: 2:30pm product requirements review."
The AI locates today's note, finds the "Daily Record" section, inserts the line, and finishes. You do not even need to open Obsidian.
### Query and complete tasks
"What are my tasks today?"
"Mark the quarterly report task as done."
The AI can return the task list or directly change `- [ ]` to `- [x]`.
### Create project notes with templates
"Create a project called Q3 Product Redesign."
The AI finds your project template, renders `{{snapshot:Project}}`, injects the theme tag, and creates the index file. The result matches what you would create manually.
### Generate AI Wiki pages for topics
"Organize the AI Wiki for all projects."
The AI can generate or update `.AI.md` files for topic-level notes such as projects, areas, and resources. It turns the theme note and its direct materials into an AI-readable summary with a one-sentence overview, core judgments, a material map, and next ingestion priorities.
These `.AI.md` files are topic guides for AI. They are not created for ordinary daily notes, captures, meeting notes, imported articles, or one-off source documents.
### Full-text search
"Where did I write about superlinear returns?"
The AI scans the vault and returns the file and line number.
### Weekly and monthly reviews
"Add a review paragraph to this week's weekly note."
The AI locates the correct file and writes the content in the right place.
You can also ask:
"Review this week using tasks actually completed this week, open work, the weekly note, and recently changed files."
The Skill uses task completion time rather than confusing “due this week” with “completed this week.” Recent files include durable change evidence; when the filesystem can prove only a modification time, the Skill reports the change as unknown instead of guessing that the file was newly created.
### Add tags and properties to PDF, image, and Office files
"Add `#contract` and status `signed` to `Assets/Agreement.pdf`."
The Skill leaves the binary attachment untouched and maintains a hidden sibling Markdown metadata file. It reads and merges existing properties first, and treats the attachment and its metadata as one pair during moves or renames.
### Generate an HTML dashboard for a topic
"Generate an HTML dashboard beside my quarterly-planning project note."
The Skill reads the topic note, its `.AI.md` page, and high-signal materials, then writes a same-name `.html` file in the same directory. The standalone dashboard organizes status, key judgments, next actions, risks, a material map, and source links. It is a decision surface, not a Markdown export or a replacement for the source note.
### Give a new knowledge base an agent workspace
When initializing Memos, IPO, GTD, or PARA, the Skill also prepares root-level `AGENTS.md`, `SOUL.md`, and `STYLE.md` files for working rules, agent identity, and communication style. Existing files are reported as conflicts and are never overwritten automatically.
`MEMORY.md` is no longer generated or upgraded by a template. An agent creates or edits it only after an explicit request to remember something, and a template migration leaves existing durable memory untouched.
### Initialize or migrate a local folder
"Help me set up this folder as a PARA knowledge base."
The Skill inventories the folder, recommends Memos, IPO, GTD, PARA, or OPC from
easiest to hardest, previews
the exact structure, and writes only after confirmation. Existing scattered
files are classified in bounded batches with a destination, reason, and
confidence for each suggestion.
Memos is the capture-first choice for daily bullets and tasks. It has no
classification destinations, so historical material is not moved into daily
notes; choose IPO, GTD, or PARA when existing material needs organization.
PARA keeps Capture and Express separate, and uses Archive as the fallback for
old material that cannot be classified reliably. GTD Inbox remains a method
stage for new unclarified items. Link, path, and collision checks run before a
confirmed migration batch moves files.
The inventory sees attachment paths and media types but does not automatically
extract binary DOC, PPT, audio, or video contents.
An existing Memos, IPO, GTD, or PARA vault can also be migrated to another
template. The agent first records whether the scope is new content only,
selected history, or full history, then tracks the settings-field diff and each
move batch. Periodic notes, custom templates, activation, AI, calendar, and sync
settings remain unchanged by default. Template files, query pages, `.AI.md`
files, and dashboards are not bulk-classified as ordinary material.
Files remain in place when Markdown links, Wikilinks, shared attachments, name
collisions, or meaning are unsafe. The profile manifest changes only after the
target entry point, task queries, links, and selected migration scope are
verified. OPC migrations use the separate OPC Skill.
## Why is it useful?
Because it does not think for you. It executes for you.
Tone, tag choice, and whether something is worth recording are still your decisions. The skill removes the operational friction: opening Obsidian, finding the folder, finding the right section, and writing the content.
Recording changes from an interruption into a side path: keep doing your work, say one sentence, and let AI write it down.
## How to start
Install the complete LifeOS Skill Bundle into the current vault:
```bash
npx -y @life-os/cli@latest skill install
```
You can also install from GitHub and select all five Skills discovered in the repository:
```bash
npx skills add quanru/lifeos-skill
```
Then tell your agent:
```text
Check my lifeos configuration
```
It will understand the shape of your note system, and you can manage your notes conversationally from there.
To begin onboarding, say:
```text
Help me set up or take over this knowledge base.
```
### Check and update an installed Skill Bundle
When the Skill is already installed inside the current vault, inspect its version and local changes first:
```bash
npx -y @life-os/cli skill status
```
After reviewing the result, update it with:
```bash
npx -y @life-os/cli skill install
```
The CLI updates all five Skills together, backs up locally modified managed files by domain, migrates the former single-Skill layout, and removes obsolete managed files after backup. It never downgrades a newer installed bundle.
### What happens if installation fails?
You can also inspect, install, or update the complete bundle from **Skills management** in DeepAsk settings.
The installer treats each installation or update as one transaction:
* Before writing, it reads and records the exact previous state of every managed target, including bundle files, the manifest, and obsolete files scheduled for removal.
* If writing a Skill, creating a backup, removing an obsolete file, or writing the final manifest fails, it restores previous contents in reverse order and removes files created by the failed attempt.
* Legacy, invalid, or locally modified installations are backed up under `.agents/skills/lifeos/.backup//` before replacement.
* Stale cleanup is limited to installer-owned Skill names proven by an unmodified valid manifest. Arbitrary names and unsafe traversal paths from a manifest are never trusted.
* Custom files inside a Skill directory, unrelated Skills, and extra files referenced only by a modified manifest are preserved.
* If rollback itself fails, the reported error includes both the original failure and the rollback failure instead of presenting an incomplete install as successful.
After a successful update, run `skill status` again and verify the bundle version and each domain Skill. When local modifications existed before the update, review the backup before merging custom content into the new version.
## Links
* [LifeOS Skill on GitHub](https://github.com/quanru/lifeos-skill)
* [Use LifeOS Skill in Aino](https://aino.md/zh/guide/ai/lifeos-skill.html)
\#RedSkill #LifeOS #Obsidian #PARA #ClaudeCode #AINotes #AgentSkill #KnowledgeManagement #Productivity
---
url: /guide/ai-integration/LLMs.txt.md
---
# LLMs.txt Document
We support LLMs.txt files, making the LifeOS documentation available to large language models.
The following files are available for use, please add them to your large language model to chat with them:
* [llms.txt](https://lifeos.vip/llms.txt)：The main LLMs.txt file
* [llms-full.txt](https://lifeos.vip/llms-full.txt)：The complete LifeOS documentation
---
url: /guide/migrate/index.md
---
# How to Migrate from LifeOS to LifeOS Pro
Reference: [Upgrade from LifeOS to LifeOS Pro](/guide/overview/usage.md#scenario-1-upgrade-from-lifeos-to-lifeos-pro)
# How to Migrate from Existing Repository to LifeOS
Reference: [Use LifeOS Pro in an Existing Repository](/guide/overview/usage.md#scenario-2-use-lifeos-pro-in-an-existing-repository)
# How to Migrate Existing Knowledge Management to PARA?
Reference: [How to Migrate Existing Knowledge Management to PARA?](https://every.to/forte-labs/para-part-4-a-full-setup-guide-1275183)
# Obsidian Newbie?
Reference: [Use Existing Example Repository](/guide/overview/usage.md#scenario-3-use-existing-example-repository)
# Import Notes from Other Note-Taking Software
Reference: [Import Notes](https://help.obsidian.md/import)
---
url: /guide/basic/connection.md
---
# Connections
So, how are the systems interconnected?
## Connecting Through Tags
Treat the first-level folders under PARA as special tags (It is not necessary to match the file name exactly, as long as the "tags" property in the \*.README.md file is unique.), and use them in "Periodic Notes." This allows for a uniform index across all the first-level folders in the same manner. This ensures that the README.md index under each PARA folder has all the context of the current topic:
## Connecting Through Projects
Projects are created within "Knowledge Management," and to increase focus on these projects, each type of "Periodic Notes" has a "Priority First Dimension" or "Projects List," such as:
* The "Projects List" in daily notes is a snapshot of the current project list, which is used to summarize the time spent on different projects on that day and their respective proportions to ensure enough time is dedicated to the projects.
* The "Priority First Dimension" in weekly and monthly notes is a list automatically merged and deduplicated from the dailynotesof the week or month, which is used to arrange tasks at the project dimension and for subsequent reviews.
* The "Priority First Dimension" in quarterly notes is a snapshot of the current domain list, used to set goals within the priority first dimension and for subsequent reviews.
* The "Priority First Dimension" in annual notes is a list automatically merged and deduplicated from the quarter'snotesof the year, which is used to set goals at the domain dimension and for subsequent reviews.
---
url: /guide/basic/retrieval.md
---
# Retrieval
So, how can we quickly retrieve notes?
## Retrieving Through Tags
For example, festival tags in daily notes:
## Retrieving Through Index Files
For example, each project's README.md index tasks and records of the project for quick access to the project's context:
## Retrieving Through Folders
For example, each PARA directory uses a consistent directory structure:
---
url: /guide/basic/review.md
---
# Review
* The review mainly focuses on the projects within this cycle, planning the tasks for the next cycle while reviewing.
* Weekly reviews cover this week's daily notes, monthly reviews summarize the weekly reviews, and quarterly reviews reflect on the monthly reviews.
---
url: /guide/core/main-system.md
---
# Main System
LifeOS core adopts two systems: a knowledge management system and a periodic notes system. The former uses the [PARA](https://fortelabs.com/blog/para/) method, managing knowledge along the dimensions of "Projects," "Areas," and "Resources," while the latter uses time as a dimension, managing tasks/goals/time through logging "Daily notes," "Weekly Notes," "Monthly Notes," "Quarterly Notes," and "Annual Notes."
Figure 1
## Knowledge Management System
From Figure 1, we can see that within the knowledge management system, from "Archives" to "Resources" to "Areas" and finally to "Projects," the operability of "knowledge notes" increases. What does operability mean? For example, compared to what's next in the "Parenting" area, the next steps for the "parenting-first-birthday-banquet" project are clearly more actionable!
**PARA Notes System Example**
Figure 2
Let's browse through the PARA notes system in the example template while referring to the official definition!
### Projects
* Definition: A project is a series of tasks with specific outcomes and deadlines.
* Explanation: The two projects below have specific outcomes and deadlines, and they belong to the "Parenting" and "Personal Brand" areas respectively.
* parenting-first-birthday-banquet
* personal-brand-wot-sharing-meeting
### Areas
* Definition: An area is something in your life that requires ongoing maintenance and for which you are responsible.
* Explanation: For "Areas," the emphasis is on "ongoing maintenance" and "responsibility." In other words, you can't mess up any of the areas below, and they require "deliberate cultivation."
* marriage-relationship
* parental-relationship
* parenting
* personal-brand
* work
### Resources
* Definition: Resources are collections of information and knowledge about a specific topic or interest.
* Explanation: For "Resources," simply put, it's a collection of information and knowledge that you're interested in, but it's okay if you mess it up, though you might need it in the future. At a certain point, it may turn into an "Area."
* photography
* knowledge-management
### Archives
* Definition: Archives are no longer active or currently unnecessary projects, areas, and resources.
* Explanation: For "Archives," anything that is not active can be put away, whether it's a "Project" that's completed, an "Area" that's no longer needed, or a "Resource" that's lost interest.
* parenting-take-a-name
For more, refer to [PARA Organization Method](/guide/intro/second-brain.md#para-组织法)
## Periodic Notes System
### Long-term Notes
From Figure 1, we can also discern that within the periodic notes system, from "Long-term Notes" to "Short-term Notes" to "Daily Notes," the predictability of "periodic notes" increases. What does predictability mean? For example, compared to planning a year in "Annual Notes," what needs to be done in the coming week in "Weekly Notes" is clearly more predictable!
Therefore, in "Long-term Notes," due to low predictability, it is more suitable to carry out "Goal Management"!
Although we do not know the specific tasks for "this year" or "this quarter," we can set goals for the "time period" from the top-down in "Annual Notes" and "Quarterly Notes," helping us maintain a sense of direction!
**Long-term Notes Example**
Annual Notes
Quarterly Notes
### Short-term Notes
With clear goals, in "Monthly Notes" and "Weekly Notes," we can naturally decompose the goals set in "Annual Notes" and "Quarterly Notes," focusing on short-term "Task Management" from the bottom-up!
The practice is to open "Annual Notes" and "Quarterly Notes" at the start of each week and month and plan tasks for "this week" and "this month" against your set goals.
**Short-term Notes Example**
Monthly Notes
Weekly Notes
### Daily Notes
Daily notes, also known as "Diary," is what I usually use to:
1. Record anytime, anywhere, so it can be indexed by "tags" in "Knowledge Management" \*README.md files.
2. Capture thoughts and insights for self-awareness.
3. Track project time to ensure focus on projects.
**Daily Notes Example**
Diary
## Summary
These two systems create two contexts which help me to stay focused:
* The time-based periodic notes system, where upon reaching a certain time point, you work based on the corresponding periodic notes, with sufficient context in the notes to manage "tasks," "goals," and "time" in relation to the time dimension;
* The topic-based PARA notes system, where when I want to research a topic, I work based on the corresponding topic's index
---
url: /guide/core/sub-system.md
---
# Sub System
> [Aspect-oriented programming - Wikiwand](https://www.wikiwand.com/zh-hans/%E9%9D%A2%E5%90%91%E5%88%87%E9%9D%A2%E7%9A%84%E7%A8%8B%E5%BA%8F%E8%AE%BE%E8%AE%A1)
Beneath the two main systems mentioned above, there are "Task Management," "Goal Management," and "Time Management" subsystems, which I mainly operate through "Periodic Notes":
## Task Management
**Task Management Example**
Task collection and indexing
Task organization
### Task Collection
Usually, whether in "Daily notes," "Weekly Notes," "Monthly Notes," or "PARA Notes," I create tasks quickly using the Markdown syntax `- [ ] Task 1`, thus collecting tasks. You don't need to be particularly concerned about which notes you record tasks in; what you need to focus on is tagging each record. If there's a definite due date, you can also trigger due date input by typing `due`.
Why shouldn't you worry about where to collect? Because you can review a task in multiple places, such as the task index at the root directory, task collection modules in weekly, monthly, quarterly, and annual logs, and the `*.README.md` index files of PARA notes.
### Task Organization
Since tasks collected are easily accessible in various modules, you can plan "Weekly Notes" and "Monthly Notes" by placing tasks as ["Block Links and Block References"](https://publish.obsidian.md/help-zh/%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97/%E5%9D%97%E9%93%BE%E6%8E%A5%E4%B8%8E%E5%9D%97%E5%BC%95%E7%94%A8) into corresponding modules as "this week's" or "this month's" to-do items!
## Goal Management
**Goal Management Example**
Annual goal setting to implementation
### Goal Setting
At the beginning of each year, plan annual goals through "Annual Notes." You can do this from the perspective of key events (i.e., "Areas") or through role dimensions, making it easy to maintain a sense of purpose in each "Area" and "Role."
### Goal Breakdown
At the start of each quarter, break down the annual goals set in "Annual Notes" in the "Quarterly Notes." After all, annual goals are quite significant and cannot be accomplished overnight. The breakdown in "Quarterly Notes" serves as a roadmap for achieving the "Annual Goals."
### Goal Decomposition
The above two steps merely set and breakdown the goals. To realize goals, they need to be transformed into individual "Tasks." How? Simple. At the start of each month, refer to "Quarterly Notes" to decompose and sort through this month's "Tasks." At the beginning of each week, just pick tasks from "Monthly Notes" and place them in "Weekly Notes."
:::tip
Note that the above three steps are not mandatory, and you can make some adjustments. Also, "Weekly Notes" can completely skip "Monthly Notes" and directly decompose goals from "Quarterly Notes" without any problems!
:::
## Time Management
**Time Management Example**
Project time tracking and review
### Project Time Tracking
First, manually tally each project's time spent and total time in "Daily notes," providing raw data for the project time tracking in "Weekly Notes," "Monthly Notes," "Quarterly Notes," and "Annual Notes."
### Project Time Review
Having obtained raw data from "Daily notes," the "Projects List" module in "Weekly Notes," "Monthly Notes," "Quarterly Notes," and "Annual Notes" allows LifeOS to calculate the time spent on each "Project" per "Week," "Month," "Quarter," and "Year." This is highly beneficial for reviewing time expenses and making you truly understand "Where did the time go?"
***
You might be curious that the subsystems mentioned above seem only to use "Periodic Notes." In fact, the two parent systems connect the various subsystems through [several methods](/guide/basic/connection.md).
---
url: /guide/readme/free.md
---
import { FreeDownloadButton } from '../../../../theme/components/FreeDownloadButton';
# FREE
> Visit Youtube for more information: https://www.youtube.com/watch?v=m-hD48UYRts
## Create Notes Visually
> See details in [Guide](/guide/free/create-note.md)
It is recommended to work with [Templater](https://silentvoid13.github.io/Templater/), Be sure to enable the "Trigger Templater on new file creation" option of the Templater plugin, so that you can use the template variables and functions provided by [Templater](https://silentvoid13.github.io/Templater/).
***
## Main System
### Periodic Notes System
> See details in [Guide](/guide/core/main-system.md#periodic-notes-system)
### Knowledge Management System
> See details in [Guide](/guide/core/main-system.md#knowledge-management-system)
## Daily Record and usememos
> Capture daily inspiration quickly by [usememos](https://www.usememos.com/)
> See details in [Usage](/plugin/life-os.md#daily-record-1)
### Manner 1: Through Memos Web App
### Manner 2: Through MoeMemos App
[MoeMemos App](https://memos.moe/)
### Manner 3: Through iOS Shortcut
[iOS Shortcut](https://www.icloud.com/shortcuts/1eaef307112843ed9f91d256f5ee7ad9)
## Installation
> [Dataview](https://github.com/blacksmithgu/obsidian-dataview) is required, please install it first.
### Recommended
LifeOS is available in the Obsidian community plugin browser!
1. Search for "LifeOS" in Obsidian's community plugins browser.
2. Enable the plugin in your Obsidian settings (find "LifeOS" under "Community plugins").
3. Check the settings. You can customize the directory of periodic notes and PARA notes.
## Settings
| Periodic Notes Settings | Description |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable | Whether to turn on Periodic Notes |
| Periodic Notes Folder | Default is 'PeriodicNotes', Set a folder for periodic notes. The format of daily, weekly, monthly, quarterly, and yearly notes in the directory must meet the following requirements: YYYY-MM-DD、YYYY-Www、YYYY-MM、YYYY-Qq |
| Date Format | Customize the date format for each periodic note type when Advanced Settings is enabled ([dayjs format](https://momentjs.com/docs/#/displaying/format/)), e.g. `YYYY-MM-DD ddd`. Format must start with the default format. A live preview is shown in the settings UI |
| Project List Header | Default is 'Project List', Set the title of the module in which the project snapshots are located in daily notes to collect the projects experienced in the current period in the weekly, monthly, quarterly, and yearly notes |
| Area List Header | Default is 'First Things Dimension', Set the title of the module in which the area snapshots are located in quarterly notes to collect the areas experienced in the current period in the yearly notes |
| Habit List Header | Default is 'Habit', Set the title of the module in daily notes where the habit is located, and the task query view will ignore tasks under that title |
| Daily Record Settings([usememos](https://www.usememos.com/)) | Description |
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| Enable | Sync daily record by remote [usememos](https://www.usememos.com/) API |
| Header | Where the Daily Record module is in a daily note |
| API | The daily record API, usememos server + API(https://your-use-memos.com/api/v1/memo) |
| Token | The token of your API, find token in https://your-use-memos.com/setting |
| P.A.R.A Notes Settings | Description |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable | Whether to turn on PARA Notes |
| Projects Folder | Default is '1. Projects', Set a folder where the PARA project is located, each subdirectory is a project, and each project must have a \[XXX.]README.md or a file with the same name as the folder as the project index |
| Areas Folder | Default is '2. Areas', Set a folder where the PARA area is located, each subdirectory is a area, and each area must have a \[XXX.]README.md or a file with the same name as the folder as the area index |
| Resources Folder | Default is '3. Resources', Set a folder where the PARA resource is located, each subdirectory is a resource, and each resource must have a \[XXX.]README.md or a file with the same name as the folder as the resource index |
| Archives Folder | Default is '4. Archives', Set a folder where the PARA archive is located, each subdirectory is a archive, and each archive must have a \[XXX.]README.md or a file with the same name as the folder as the archive index |
## Move between PARA categories
**Right-click** on a subfolder within any PARA directory (Projects, Areas, Resources, Archives) to see "Move to" menu items, allowing you to quickly move folders between the four PARA categories. For example, move a completed project from "Projects" to "Archives".
> Requires PARA Notes to be enabled in settings.
## Usage
### Daily record
> [usememos](https://www.usememos.com/)
Integration with [usememos](https://www.usememos.com/), you need to [deploy](https://www.usememos.com/docs/install/self-hosting) your own usememos.
Or use the [demo](https://demo.usememos.com/auth/signup) to experience.
### Query code block
LifeOS works by writing markdown code block, which query project, area, task list according to the date parsed from current filename, and query task, bullet, file, project, area, resource, archive list according to the tags parsed from [Properties](https://help.obsidian.md/Editing+and+formatting/Properties).
#### Query by time
Time scope is parsed from current file name, for example:
* 2023-01-01.md // Only 1 January is included
* 2023-W21.md // Every day of week 21
* 2023-06.md // Every day and every week of June
* 2023-Q3.md // Every day, every week, every month of Quarter 3
* 2023.md // Every day, every week, every month, every quarter of 2023
````markdown
```LifeOS
TaskDoneListByTime
```
````
````markdown
```LifeOS
TaskRecordListByTime
```
````
````markdown
```LifeOS
ProjectListByTime
```
````
````markdown
```LifeOS
AreaListByTime
```
````
````markdown
```LifeOS
BulletRecordListByTime
```
````
> `BulletRecordListByTime` collects non-task bullet items from daily notes within the date range, specifically from the "Daily Record" header section. Requires the "Daily Record Header" setting to match the actual header name in your daily notes.
#### Query by tag
Tags is parsed from the [Properties](https://help.obsidian.md/Editing+and+formatting/Properties) of current file, for example:
```markdown
---
tags: project-1
---
```
The following code block would use project-1 as the tag for the query.
````markdown
```LifeOS
TaskListByTag
```
````
````markdown
```LifeOS
BulletListByTag
```
````
````markdown
```LifeOS
FileListByTag
```
````
````markdown
```LifeOS
ProjectListByTag
```
````
````markdown
```LifeOS
AreaListByTag
```
````
````markdown
```LifeOS
ResourceListByTag
```
````
````markdown
```LifeOS
ArchiveListByTag
```
````
#### Query para by folder
````markdown
```LifeOS
ProjectListByFolder
```
````
````markdown
```LifeOS
AreaListByFolder
```
````
````markdown
```LifeOS
ResourceListByFolder
```
````
````markdown
```LifeOS
ArchiveListByFolder
```
````
### Templater helper functions
:::tip
This section documents the legacy community / open-source LifeOS syntax, which depends on [Templater](https://github.com/SilentVoid13/Templater). For the new LifeOS Pro built-in template syntax, see [Template Syntax](/guide/beginner-guide/template-syntax.md).
:::
#### Generate list
Generate a list of README.md snapshots in the specified directory.
```markdown
<% LifeOS.Project.snapshot() %>
<% LifeOS.Area.snapshot() %>
<% LifeOS.Resource.snapshot() %>
<% LifeOS.Archive.snapshot() %>
```
For example:
```markdown
<% LifeOS.Project.snapshot() %>
```
to
```markdown
1. [[1. Projects/project-1/README|project-1]]
2. [[1. Projects/y-project/README|y-project]]
```
## Acknowledgements
Also, I relied on the code from these excellent plugins, vault, and inspirations:
* [PARA](https://fortelabs.com/blog/para/). Thanks to Tiago Forte for inventing such a great organizational method.
* [PARA Starter Kit](https://forum.obsidian.md/t/para-starter-kit/223). Thanks to cotemaxime for creating such a great starter vault.
* [obsidian-periodic-notes](https://github.com/liamcain/obsidian-periodic-notes). Gave me the inspiration to develop this plugin.
* [obsidian-dataview](https://github.com/blacksmithgu/obsidian-dataview). The underlying plugin uses dataview's query interface.
* [Templater](https://github.com/SilentVoid13/Templater). Provides decoupled template creation, allowing a very large number of plugins to create files with the help of it.
---
url: /guide/readme/pro.md
---
# PRO
# Pro Features
import { CommercialContent } from '../../../../theme/components/CommercialContent';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
# Pro Features
Get link: [LifeOS Pro](./pricing.mdx)
> Visit Youtube for more information: https://www.youtube.com/watch?v=C1Ph\_j00\_Sc
Discover the transformative features of LifeOS Pro！
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
## 📝 Advanced List
> [Advanced List](/guide/pro/advanced-list.md)
Are you troubled by long tasks, bullet notes, and file lists? This time, we bring you the ultimate solution!🔍
👉 New Features
1️⃣ Page Turning: Even long lists can be easily browsed!📖
2️⃣ Sorting: Sort by date, status at will!📅
3️⃣ Search: Text and date search with one click, everything is under control!🔍
Not only that, the task collection and task completion list in the periodic notes also fully support these new features! Want to find a specific task or record? Just a few seconds!⏱️
### Search
### Sort
### Filter
## 🏡 Home Page View
> [Home Page View](/guide/pro/home-view.md)
Your central command center for life and work. Our sleek, user-friendly dashboard provides an at-a-glance overview of your inputs, projects, tasks, and outputs, enabling seamless coordination of all aspects of your life.
## Workflow
One-stop project management, from input to delivery, forming a closed loop, linking each step, driving the project forward steadily.
## Habit statistics
Not just recording, but also analyzing, statistics on the overall completion of the habit module in the diary, scientifically understanding your habit formation cycle.
## Flash random
Activate your historical notes, sparking endless creativity and allowing old thoughts to grow new branches.
## 📒 Theme Notes
> [Theme Notes](/guide/pro/theme-note.md)
Experience our upgraded note-taking system, evolved from the PARA method. With customizable options and an intuitive interface, Theme Notes simplifies the process of capturing, organizing, and utilizing information, making it accessible for users at all levels.
## 📱 Convenient Features
> [Convenient Features](/guide/pro/convenient.md)
1. Automatically insert timestamps in daily records
2. Right-click tags to create theme notes
3. Right-click on theme folders to quickly circulate
4. Click on folders to jump to theme index files
5. Click on file titles to expand and focus on sidebar files
6. When opening today's daily note, automatically focus on the last line of the daily record module
## 🔥 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/lifeos-pro-changelog.md).
---
url: /case/daily-workflow.md
---
# A Day with Obsidian LifeOS
This article shows a practical day-to-day workflow with Obsidian, LifeOS Pro, Calendar Pro, and DeepAsk. It is written as a routine you can copy, not as a feature catalog.
## Morning: open today first
After opening Obsidian, start from today's daily note or the LifeOS Pro home view. If you have not prepared a vault yet, follow the [quick start](/guide/quick-start/getting-started.md) first.
Write only three sections at the beginning:
```markdown
## Today's Focus
- [ ] Finish the user feedback report #project/user-feedback
- [ ] Prepare the product review material #project/product-review
- [ ] Reply to customer emails
## Quick Notes
## End-of-day Review
```
Do not over-plan in the morning. Capture the real work first, then use the [task view](/guide/pro/task-view.md) to organize it.
## Before work: put key tasks on the calendar
Open [Calendar Pro](/guide/pro/calendar.md) and place the most important tasks into time blocks.
Schedule only three kinds of work:
1. Deep work that must move forward today.
2. Meetings or conversations with a fixed time.
3. Small tasks that need a clear buffer.
If something is still just an idea, keep it in Quick Notes. Turn it into a task only when the next action is clear.
## During work: keep context with theme tags
LifeOS is not about storing everything in one large file. It is about making related notes, tasks, and files flow back to the same theme.
For example:
```markdown
## User feedback analysis
- [ ] Summarize the latest 30 feedback items #project/user-feedback
- Most performance complaints come from the mobile first screen.
- In the next interview, ask whether first-time setup felt confusing.
```
You can write this in a daily note or a project note. As long as the same theme tag is present, the content can be indexed in the related [theme note](/guide/pro/theme-note.md).
## Afternoon: focus with Pomodoro
When you start deep work, open [Pomodoro](/guide/pro/pomodoro.md) and bind it to one task only.
A simple rhythm:
1. Work on one task for 25 minutes.
2. Rest for 5 minutes.
3. Decide whether to continue, pause, or split the task.
The timer is not the point. The point is forcing a small decision after each focus cycle.
## Evening: close the loop
At the end of the day, return to the daily note and do three things:
1. Check off completed tasks.
2. Move unfinished but important tasks to tomorrow or to their project theme.
3. Write one clear judgment about the day.
```markdown
## End-of-day Review
- The feedback report has a first draft. Mobile data still needs to be added tomorrow.
- The product review material did not start. Moved to 10:00 tomorrow.
- The real blocker was an unclear metric definition.
```
This turns your daily note into a reviewable work record instead of a pile of fragments.
## What this workflow uses
| Scenario | LifeOS feature |
| ----------------------- | ---------------------------------------------------------------------------------------------- |
| Morning planning | [Daily note](/guide/quick-start/how-start.md) + [task creation](/guide/pro/task-create.md) |
| Central task management | [Task view](/guide/pro/task-view.md) |
| Time blocking | [Calendar Pro](/guide/pro/calendar.md) |
| Focus work | [Pomodoro](/guide/pro/pomodoro.md) |
| Project context | [Theme notes](/guide/pro/theme-note.md) + [advanced lists](/guide/pro/advanced-list.md) |
:::tip
If you are new to LifeOS, do not start with a complex template. Build the habit first: write tasks, schedule time, check off work, and close the day.
:::
---
url: /case/project-management.md
---
# Manage a Full Project with LifeOS Pro
Project management is not about creating more folders. It is about keeping goals, tasks, references, and reviews connected under the same theme. In LifeOS Pro, that starts with a [theme note](/guide/pro/theme-note.md).
## Step 1: create a theme from the top-left form
In the LifeOS form at the top left of Obsidian, switch to the theme note form and enter a project theme tag, for example:
```text
project/user-feedback-report
```
If the form is not visible, click the LifeOS icon with a `+` in the left sidebar. After creation, LifeOS opens the project theme index.
## Step 2: make the project index clear
Do not start with a long document. Fill in four blocks first:
```markdown
# User Feedback Report
## Goal
Deliver a feedback analysis report before Friday's product review.
## Deliverables
- A feedback classification table
- One page of key findings
- Three product recommendations
## Milestones
- [ ] Collect feedback #project/user-feedback-report
- [ ] Categorize and count issues #project/user-feedback-report
- [ ] Write findings #project/user-feedback-report
- [ ] Share in product review #project/user-feedback-report
## Key references
```
The project index defines the project. Daily notes, meeting notes, and references can stay where they are and return through the same theme tag.
## Step 3: move work through the task view
Open the [task view](/guide/pro/task-view.md) and filter by the project tag. You will see project tasks even when they are scattered across different notes.
Use three decisions:
1. Do today: schedule it today or place it on the calendar.
2. Waiting: keep the task, but write who or what it is waiting for.
3. Not now: remove it from the active project list.
## Step 4: tag meetings and references too
Project context usually gets lost in meetings, quick notes, and references. Do not copy everything into the project index. Keep the same theme tag instead.
```markdown
## Product review notes
- Mobile feedback is more concentrated than desktop feedback. #project/user-feedback-report
- We need the latest one-week sample for new users. #project/user-feedback-report
- [ ] Ask ops for the latest two weeks of feedback #project/user-feedback-report
```
The project index stays clean while [advanced lists](/guide/pro/advanced-list.md) keep the related content visible.
## Step 5: protect delivery time on the calendar
As the deadline gets closer, turn project tasks into time blocks. Open [Calendar Pro](/guide/pro/calendar.md) and schedule the critical work.
Avoid large tasks like "write report". Split them into 60-90 minute units:
* Clean the raw feedback table
* Merge duplicate issues
* Write three findings
* Prepare the product review version
## Step 6: close with a short review
After the project ships, add a short review to the theme note:
```markdown
## Review
- Result: the report shipped on time and two recommendations were accepted.
- Worked well: theme tags made source review fast.
- Blocker: metric definitions were unclear, causing one round of rework.
- Next time: add a "confirm metric definitions" task on day one.
```
This turns the project note into reusable experience, not just an archive.
## Read next
* [Theme notes](/guide/pro/theme-note.md)
* [Task creation](/guide/pro/task-create.md)
* [Task view](/guide/pro/task-view.md)
* [Project lifecycle practice](/guide/best-practice/project-life-cycle.md)
---
url: /case/weekly-review.md
---
# Run a Useful Weekly Review with LifeOS
Weekly reviews often fail because you try to remember the whole week from scratch. LifeOS works better when tasks, daily notes, and theme tags have already captured the evidence.
## Start with completed work
Open your weekly note or weekly review note. Pull up completed tasks from the [task view](/guide/pro/task-view.md) or review them from daily notes.
Do not only count tasks. Look for three things:
1. Which tasks actually moved goals forward?
2. Which tasks were reactive or administrative?
3. Which tasks repeated, suggesting a system problem?
## Review active projects
Open this week's active [theme notes](/guide/pro/theme-note.md) and check whether each project moved forward.
Use a compact format:
```markdown
## Project Progress
### User Feedback Report
- Progress: finished classification and first findings.
- Risk: mobile data is missing the latest one-week sample.
- Next week: add data on Monday, send review version on Tuesday.
### Website Update
- Progress: completed the feature overview on the homepage.
- Risk: English illustrations need another text review.
- Next week: run one mobile screenshot pass.
```
This keeps the review grounded in projects instead of feelings.
## Check the calendar
If you use [Calendar Pro](/guide/pro/calendar.md), review the week view. It is usually more honest than memory.
Look for:
* Whether deep work had real blocks of time.
* Whether meetings took your best hours.
* Whether urgent tasks kept leaking into evenings.
* Which tasks were repeatedly postponed.
## Re-decide unfinished tasks
Do not move every unfinished task to next week. Decide again:
| Type | Action |
| ------------------- | ------------------------------------------------- |
| Still important | Schedule it on a date or time block |
| Unclear goal | Move it back to the project theme and clarify it |
| No longer important | Delete or archive it |
| Waiting on someone | Write who it is waiting for and when to follow up |
A clean task system makes next week easier to start.
## Write next week's plan
End with three sections:
```markdown
## Next Week Focus
1. Finish the review version of the user feedback report.
2. Publish the updated documentation entry.
3. Close the LifeOS plugin feedback loop.
## Not Doing Next Week
- No large refactors.
- No new documentation pages until the beginner path is fixed.
## Confirm Early
- Confirm feedback metric definitions on Monday.
- Schedule an English site copy review on Wednesday.
```
The most useful part is often "not doing". It protects attention.
:::tip
If you are new to LifeOS, keep the weekly review under 20 minutes: review completed tasks, review projects, handle unfinished tasks, and write three priorities for next week.
:::
---
url: /case/research-workflow.md
---
# A Research Workflow with Obsidian LifeOS
Research work often breaks in two places: you save more and more references, but no conclusion emerges; or you write long notes, but nothing turns into action. LifeOS theme notes help keep sources, questions, conclusions, and tasks in one context.
## Create a research theme
Use the LifeOS form at the top left to create a theme note, for example:
```text
research/ai-note-taking
```
This does not have to be a project. A research theme can be a long-running area of interest. Projects have deliverables; research themes can keep accumulating context.
## Capture references lightly
Do not summarize every source immediately. Capture the source, the useful points, and your own judgment.
```markdown
## AI note-taking tools
Source: https://example.com/report
### Useful points
- Users care more about getting back to source material than about one-off summaries. #research/ai-note-taking
- Team workflows need shared context, while personal workflows depend on the local knowledge base. #research/ai-note-taking
### My judgment
- DeepAsk should be explained as "ask questions inside your Obsidian knowledge base", not as generic AI chat.
```
The same theme tag connects reference notes, daily thoughts, and tasks.
## Turn questions into tasks
Research is not collecting. It is reducing uncertainty. When you see a question, turn it into an executable task.
```markdown
- [ ] Compare local-context features in 3 Obsidian AI plugins #research/ai-note-taking
- [ ] List 5 beginner-friendly DeepAsk scenarios #research/ai-note-taking
- [ ] Draft a website article #research/ai-note-taking
```
Then filter this theme in the [task view](/guide/pro/task-view.md) and move the research forward.
## Use DeepAsk for the second pass
If you use [DeepAsk](/guide/ai-integration/deepask.md), ask questions against the relevant notes instead of a blank chat.
Useful prompts:
* "What user pains repeat across this theme?"
* "Group these references by usage scenario, not by source."
* "Which conclusions are supported by notes, and which are still assumptions?"
Treat AI output as a second index, not as the final conclusion. Go back to the original notes before making decisions.
## Turn research into output
At some point, research should become an output:
| Output | Best for |
| --------------- | ------------------------------------------------ |
| Project | There is a deliverable and deadline |
| Case study | You need to explain the workflow publicly |
| Decision record | You need to record why a choice was made |
| Long-term area | No deliverable yet, but the topic stays relevant |
If it becomes a project, create a `project/...` theme and link the key findings from the research theme.
## Read next
* [Theme notes](/guide/pro/theme-note.md)
* [Advanced lists](/guide/pro/advanced-list.md)
* [DeepAsk AI plugin](/guide/ai-integration/deepask.md)
* [Custom workflow](/guide/best-practice/custom-workflow.md)
---
url: /case/ai-powered-notes.md
---
# Make Obsidian Notes Askable with DeepAsk
Many people connect AI to a note app and only use it to summarize one article. That is useful, but it is not the strongest Obsidian + DeepAsk workflow. The better pattern is asking questions against your own knowledge base to find links, conflicts, and next actions.
## Give AI a clear context first
DeepAsk can work with files, tags, time ranges, and other contexts. Before asking, decide what you want it to read.
Common contexts:
1. The current note.
2. Notes under a theme tag.
3. Daily notes from the last week or month.
4. Meeting notes and tasks related to one project.
## Scenario 1: turn meeting notes into actions
Write the meeting note in Obsidian as usual:
```markdown
## Beginner path discussion
- Users do not know whether to download the example vault or install the plugin first.
- The example vault download page should link clearly to the quick-start guide.
- The onboarding email needs the example vault download link and quick-start link.
- [ ] Update the onboarding email template #project/lifeos-onboarding
```
Then ask DeepAsk:
```text
Based on this meeting note, extract all actions.
Output owner / next step / questions to confirm.
Do not invent information that is not in the note.
```
Paste the useful result back into the meeting note, then convert real actions into LifeOS tasks.
## Scenario 2: find patterns in daily notes
Daily notes capture reality, but reviewing them manually is slow. Select the last 30 days and ask:
```text
Find recurring blockers in my daily notes from the last 30 days.
Group them into workflow, communication, energy, and tooling.
Give one executable improvement for each group.
```
This is more useful than "summarize my notes" because it asks AI to find patterns.
## Scenario 3: check whether a project is drifting
Select a project theme tag and ask:
```text
What was the original goal of this project?
Do the tasks added in the last 7 days still support that goal?
List tasks that may be drifting away from the goal and explain why.
```
This helps when a project starts spreading in too many directions. DeepAsk can surface drift; you still make the final call.
## Scenario 4: turn references into an article outline
Select a research theme or a group of reference notes and ask:
```text
Create an article outline for beginners based on these notes.
Requirements:
1. Start with why the feature matters.
2. Give the smallest usable workflow.
3. End with common mistakes and next links.
```
This works well when you want to turn accumulated notes into publishable material.
## Three boundaries for AI notes
| Boundary | Why it matters |
| ----------------------------------- | -------------------------------------------------------- |
| Do not let AI choose your goals | AI can organize information, but it cannot own tradeoffs |
| Do not allow unsourced claims | Key conclusions must lead back to original notes |
| Do not keep tasks only in AI output | Real tasks should enter LifeOS task view or theme notes |
## Read next
* [DeepAsk guide](/guide/ai-integration/deepask.md)
* [Use LifeOS with AI](/guide/ai-integration/lifeos-skill.md)
* [AI Coach](/guide/ai-integration/ai-coach.md)
---
url: /plugin/lifeos/pricing.md
---
# Plans
import { PricingTitle } from '../../../../theme/components/PricingTitle';
import { Pricing } from '../../../../theme/components/Pricing';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
:::tip TL;DR
If Obsidian is your primary workspace, choose LifeOS Pro and purchase DeepAsk separately only when you need AI. Their licenses are independent.
:::
The LifeOS Pro license does not include Calendar Pro, DeepAsk, Aino Desktop Pro, or Aino Mobile Pro.
---
url: /plugin/lifeos/life-os.md
---
# Basic
> Visit Youtube for more information: https://www.youtube.com/watch?v=m-hD48UYRts
## Create Notes Visually
> See details in [Guide](/guide/free/create-note.md)
It is recommended to work with [Templater](https://silentvoid13.github.io/Templater/), Be sure to enable the "Trigger Templater on new file creation" option of the Templater plugin, so that you can use the template variables and functions provided by [Templater](https://silentvoid13.github.io/Templater/).
### Create Periodic Notes
### Create Theme Notes
## Main System
### Knowledge Management System
> See details in [Guide](/guide/core/main-system.md#knowledge-management-system)
### Periodic Notes System
> See details in [Guide](/guide/core/main-system.md#periodic-notes-system)
## Sub System
> See details in [Guide](/guide/core/sub-system.md)
### Task Management
### Time Management
Project time tracking and review
## Usememos Sync
> Capture daily inspiration quickly by [usememos](https://www.usememos.com/)
> See details in [Usage](/guide/readme/free.md#daily-record)
---
url: /plugin/lifeos/life-os-pro.md
---
# Pro Features
import { CommercialContent } from '../../../../theme/components/CommercialContent';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
# Pro Features
Get link: [LifeOS Pro](/plugin/lifeos/pricing.md)
> Visit Youtube for more information: https://www.youtube.com/watch?v=C1Ph\_j00\_Sc
Discover the transformative features of LifeOS Pro！
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
## 📝 Advanced List
> [Advanced List](/guide/pro/advanced-list.md)
Are you troubled by long tasks, bullet notes, and file lists? This time, we bring you the ultimate solution!🔍
👉 New Features
1️⃣ Page Turning: Even long lists can be easily browsed!📖
2️⃣ Sorting: Sort by date, status at will!📅
3️⃣ Search: Text and date search with one click, everything is under control!🔍
Not only that, the task collection and task completion list in the periodic notes also fully support these new features! Want to find a specific task or record? Just a few seconds!⏱️
### Search
### Sort
### Filter
## 🏡 Home Page View
> [Home Page View](/guide/pro/home-view.md)
Your central command center for life and work. Our sleek, user-friendly dashboard provides an at-a-glance overview of your inputs, projects, tasks, and outputs, enabling seamless coordination of all aspects of your life.
## Workflow
One-stop project management, from input to delivery, forming a closed loop, linking each step, driving the project forward steadily.
## Habit statistics
Not just recording, but also analyzing, statistics on the overall completion of the habit module in the diary, scientifically understanding your habit formation cycle.
## Flash random
Activate your historical notes, sparking endless creativity and allowing old thoughts to grow new branches.
## 📒 Theme Notes
> [Theme Notes](/guide/pro/theme-note.md)
Experience our upgraded note-taking system, evolved from the PARA method. With customizable options and an intuitive interface, Theme Notes simplifies the process of capturing, organizing, and utilizing information, making it accessible for users at all levels.
## 📱 Convenient Features
> [Convenient Features](/guide/pro/convenient.md)
1. Automatically insert timestamps in daily records
2. Right-click tags to create theme notes
3. Right-click on theme folders to quickly circulate
4. Click on folders to jump to theme index files
5. Click on file titles to expand and focus on sidebar files
6. When opening today's daily note, automatically focus on the last line of the daily record module
## 🔥 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/lifeos-pro-changelog.md).
---
url: /plugin/lifeos/privacy.md
---
# Data Privacy
Your data security and privacy are our top priorities.
## LifeOS Data Privacy Policy
### Local-First Philosophy
LifeOS is designed with a local-first approach. All your notes, tasks, and personal data are stored locally in your Obsidian vault. We do not have access to your vault contents.
### No Data Collection
LifeOS does not collect, transmit, or store any of your personal data on external servers. Your productivity data, notes, and configurations remain entirely on your device.
### Optional Cloud Sync
If you choose to use Obsidian Sync or third-party sync services, please review their respective privacy policies. LifeOS itself does not facilitate or manage any cloud synchronization.
### Calendar Sync (Pro Feature)
LifeOS Pro includes calendar functionality. If you choose to sync with external calendars (CalDAV or Google Calendar), your calendar data will be transmitted to those services. Please review their respective privacy policies:
* For Google Calendar, refer to [Google's Privacy Policy](https://policies.google.com/privacy)
* For CalDAV services, refer to your provider's privacy policy
LifeOS Pro only transmits the minimum necessary data required for calendar synchronization.
### License Verification
For Pro version users, license verification requires minimal data exchange (license key validation only). No vault contents or personal information is transmitted during this process.
## Our Commitment
:::tip
LifeOS respects your privacy. Your data stays on your device, and we never access, collect, or monetize your personal information.
:::
---
url: /plugin/calendar/pricing.md
---
# Plans
import { PricingTitle } from '../../../../theme/components/PricingTitle';
import { Pricing } from '../../../../theme/components/Pricing';
import { calendarProFeatures, getFeatures } from '../../../../theme/data/pricingFeatures';
---
url: /plugin/calendar/calendar-pro.md
---
import { CommercialContent } from '../../../../theme/components/CommercialContent';
# Pro Features
Get link: [Calendar Pro](/plugin/calendar/pricing.md)
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
## 🔥 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/calendar-pro-changelog.md).
---
url: /plugin/calendar/privacy.md
---
# Data Privacy
Your data security and privacy are our top priorities.
## Calendar Pro Data Privacy Policy
### Local Storage
All calendar events, tasks, and configurations are stored locally in your Obsidian vault. Your scheduling data never leaves your device unless you explicitly configure external calendar sync.
### CalDAV & Google Calendar Sync
If you choose to sync with external calendars (CalDAV or Google Calendar), your calendar data will be transmitted to those services. Please review their respective privacy policies:
* For Google Calendar, refer to [Google's Privacy Policy](https://policies.google.com/privacy)
* For CalDAV services, refer to your provider's privacy policy
Calendar Pro only transmits the minimum necessary data required for synchronization.
### No Third-Party Analytics
Calendar Pro does not include any third-party analytics or tracking. We do not monitor your calendar usage patterns or event contents.
### License Verification
For Pro version users, license verification requires minimal data exchange (license key validation only). No calendar data or personal information is transmitted during this process.
## Our Commitment
:::tip
Calendar Pro respects your privacy. Your calendar data is yours alone, and we only facilitate synchronization with services you explicitly configure.
:::
---
url: /plugin/deepask/pricing.md
---
# Plans
import { PricingTitle } from '../../../../theme/components/PricingTitle';
import { Pricing } from '../../../../theme/components/Pricing';
import { deepaskFeatures, getFeatures } from '../../../../theme/data/pricingFeatures';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
The DeepAsk license does not include model API usage, LifeOS Pro, Calendar Pro, Aino Desktop Pro, or Aino Mobile Pro.
---
url: /plugin/deepask/deepask.md
---
import { CommercialContent } from '../../../../theme/components/CommercialContent';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
# Pro Features Overview
> Deep Ask Plugin Quick Start Guide
Get link: [Deep Ask](/plugin/deepask/pricing.md)
## 📖 Introduction
Deep Ask is a powerful Obsidian AI chat plugin designed to enhance your knowledge management experience. By integrating multiple AI models and local CLI agents, Deep Ask can understand your note content, support Codex CLI or Claude Code CLI, and provide intelligent question-answering, content generation, and knowledge retrieval.
***
***
## 🌐 Chrome Extension
Deep Ask now offers a Chrome browser extension, allowing you to seamlessly use AI assistant features while browsing the web!
**Download**: [Chrome Web Store - DeepAsk AI](https://chromewebstore.google.com/detail/deepask-ai/abhoenehflglmgbohaibihggedfcpcep) · [Stable Feishu link: Chrome / Edge manual package (ZIP)](https://www.feishu.cn/file/CyLIblv2OowEi4xHDPwcWC9MnNc)
### Manual installation (Chrome / Edge)
1. Download the ZIP and extract it to a folder you will keep.
2. Open `chrome://extensions` in Chrome or `edge://extensions` in Microsoft Edge.
3. Enable **Developer mode**, choose **Load unpacked**, and select the extracted folder.
4. Keep the DeepAsk Obsidian plugin enabled, then open the DeepAsk extension from the browser toolbar.
The Feishu package uses a stable link and is replaced in place when a new version is released.
### Key Features
* **Integration with Obsidian**: Supports linking tags, context, and files from Obsidian to initiate Q\&A on the current webpage
* **Webpage Content Conversation**: Directly chat with the content of the current webpage
* **Codex CLI and Claude Code CLI**: Supports Codex CLI or Claude Code CLI, while the Chrome extension adds webpage context into the same DeepAsk workflow
* **Visible Reply Feedback**: Shows a temporary animated reply placeholder before the first streaming token arrives
* **Cross-platform Collaboration**: Seamlessly switch between browser and Obsidian for a complete knowledge management workflow
***
***
## ✨ Main Features
* 🤖 **Multi-model and SDK Support**：Support OpenAI-compatible providers and Anthropic SDK configuration, including GPT, Gemini, DeepSeek, Qwen, Kimi, Claude, Ollama, etc.
* 🧑💻 **Codex CLI and Claude Code CLI**：Supports Codex CLI or Claude Code CLI, with Chrome extension webpage context available in the same workflow
* 💻 **Real-time Content Conversation**：Automatically understand your note structure and content, support conversation with current notes and webpages
* 🏷️ **Tag Integration**：Context collection based on tags, intelligent content retrieval
* 📎 **File Attachment**：Support adding note files as context
* 🤖 **Professional Prompt Selection**：Built-in professional prompt library to enhance conversation quality
* 🗓 **Time Range Limitation**：Support filtering context content by time range
* 📷 **Creative Poster Generation**：AI generates HTML-formatted posters with preview and download support
* 💡 **Quick Suggestions**：Intelligent recommendation of common conversation templates
* 💬 **Streaming conversation with reply placeholder**：Real-time response, conversation history management, and an animated preparing-reply bubble before content arrives
* 🔄 **Multi-session management**：Support creating multiple conversation topics
* 🌍 **Multi-language support**：Support Chinese and English interfaces
* 🧩 **LifeOS Skill (recommended)**：Install LifeOS Skill first so AI agents can understand and operate your LifeOS vault; the built-in MCP server remains available for MCP-compatible clients
## 🚀 Quick Start
### Step 1: Install Prerequisites
Deep Ask depends on the **Dataview plugin**, please ensure it is installed and enabled:
1. Open Obsidian settings
2. Enter the "Community plugins" section
3. Search and install **Dataview**
4. Enable Dataview plugin
### Step 2: Install Deep Ask Plugin
1. Download the plugin file to the Obsidian plugin directory, usually in your repository's `.obsidian/plugins` directory
2. Restart Obsidian
3. Enable Deep Ask in the plugin list
### Step 3: Activate the Plugin
1. Open the plugin settings page
2. Enter the "Activation" tab
3. Enter your account email and activation code
## ⚙️ Configuration Guide
### AI Model Configuration
In the "AI Model" tab of the settings page, you can configure the supported AI services:
Here is an example of configuring the DeepSeek model:
#### 🔵 DeepSeek Configuration
Fill in the API Key, and then click the AI Model, and select the specific model to enable:
You can also customize the AI model configuration:
#### 🟢 Custom Configuration
You can customize the AI model configuration, supporting the following parameters:
* **Base URL**：The base URL of the AI service
* **API Key**：The API Key of the AI service
* **AI Model**：The supported models of the AI service
### Local CLI safety boundaries
When you select Codex CLI or Claude Code CLI, DeepAsk resolves the execution policy before launching the process. Local CLIs cannot reuse the plugin's per-tool diff, approval, and undo protocol, so their boundary is intentionally stricter than ordinary API models.
| Current mode | Local CLI behavior |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ask | Always runs in a read-only sandbox and can only analyze or answer. |
| Edit | Runs read-only and returns a proposed change; it does not write files directly. |
| Structured workflow | Runs read-only so a workflow cannot bypass the host review protocol. |
| Agent | Can modify files only when both write and delete permissions are enabled and you approve whole-vault access for that turn; otherwise it remains read-only. |
DeepAsk records the selected policy as tool activity. If you reject whole-vault access, the CLI is not launched; rejection and execution failures remain visible in the activity state. Ask, Edit, and structured workflows never become writable just because mutation settings are enabled.
:::warning Whole-vault access
After approval, the local CLI may modify or delete files anywhere in the current vault for that turn. Approve only when the request is well scoped and your data is backed up or recoverable. When uncertain, stay read-only or use a test vault first.
:::
Local CLIs require a desktop Node.js process and are unavailable in Obsidian Mobile. Mobile users can continue using configured API models and the plugin's embedded tools.
### AI Context Configuration
* **Maximum conversation rounds**：Set the number of conversation history to retain
* **Temperature**：Set the randomness of AI replies, the lower the more stable, the higher the more random
* **Exclude files with matching tags**：Generally used to filter periodic notes and template notes. The former has already queried flash notes in periodic notes through tags (duplicate context), and the latter are various template notes (invalid context)
* **Use current opened file only**：Only use the currently opened file as context, ignore all other files opened in the background
* **LifeOS Integration Config**：Configure file search strategy when using LifeOS with AI features
* **Theme Note File Search**：Select how AI searches theme-related files
* **Include index files only**：Only include index files
* **Include entire folder**：Include entire folder
* **Recursive Sub-theme Search**：Enable recursive search for sub-themes within the selected theme tags
### Conversation Settings
* **Maximum conversation rounds**：Set the number of conversation history to retain
* **Temperature**：Set the randomness of AI replies, the lower the more stable, the higher the more random
## 🎯 Usage Guide
### Launching the Chat Interface
There are several ways to open the AI chat:
1. **Toolbar button**：Click the Deep Ask AI icon in the sidebar
2. **Command Palette**：`Ctrl/Cmd + P` search "Deep Ask AI Chat"
3. **Shortcut**：Can be customized in settings
### Basic Conversation
1. Enter your question in the chat interface at the bottom
2. Select the AI model (if multiple are configured)
3. Click Send or press Enter to send
4. AI will reply to your question in real-time
### Advanced Features
#### 💻 Real-time Content Conversation
* Directly chat with the currently opened file and webpage, supporting multiple files and webpages as context, and linking with existing notes
#### 📎 File Attachment
* Trigger file search by typing /, select the file to add to the context
* The opened file will be automatically added to the context
#### 🏷️ Tag Integration
* Trigger tag search by typing #, select the tag to add to the context
* DeepAsk will automatically search for all records in the vault, including tasks, flash notes, and files with the selected tag
#### 🤖 Professional Prompt Selection
* Enter / to trigger prompt search, select the prompt to add to the context
* DeepAsk will display a list of prompt files in the specified directory for selection
#### 🧩 LifeOS Skill And MCP Compatibility For Ordinary Models
DeepAsk ordinary model chat can use agent skills and MCP tools without switching to Claude Code / Codex CLI mode. For LifeOS vault work, use LifeOS Skill first; it carries LifeOS-specific workflows and follows your vault settings. MCP remains available when a client specifically needs protocol-level tool access.
* Recommended: type `!lifeos your request` or `$lifeos your request` to explicitly invoke the installed LifeOS Skill
* If it is not installed yet, install it from [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) or from the AI Connect settings tab
* Models can also call `deepask_list_skills` / `deepask_read_skill` to inspect installed skills
* Read/query embedded MCP tools remain available as the compatibility path, including file reading, task search, tag search, and periodic-note lookup
* On desktop, DeepAsk can still load external MCP servers from `.mcp.json`, `~/.claude/mcp.json`, and `~/.config/claude/mcp.json`
* Write, update, and delete tools are disabled by default and can be enabled from AI Connect
#### 🗓 Time Range Limitation
* Enter /2025-08-22 to trigger time range limitation
* DeepAsk will automatically limit all matching context (files, tags) to the specified time range
#### 📷 Creative Poster Generation
* Require AI to generate HTML-formatted posters
* Click the "eye" preview button below the AI reply to view and download the poster
#### 💬 Session Management
* Click "+" to create a new conversation
* Each conversation manages the context independently
#### ✏️ Message Editing
* Hover to display the edit button
* Support editing the sent message, triggering AI to regenerate the reply
* Support clicking the regenerate button next to the message, triggering AI to regenerate the reply
#### 💾 Download AI Conversation
* Click the plus button next to the message, and the AI reply will be appended to the current note
* Click the download button in the lower right corner of the dialog, and the entire conversation will be downloaded as a Markdown file
### 💡 Quick Suggestions
In the blank conversation, Deep Ask will display commonly used suggestions:
* /2025-08-22 Summarize today's diary?
* \#SwapHouse What are the good and bad things I did?
* \#HistoryCycle Summarize this tag?
## 🔌 MCP Server
Recommended path: use [LifeOS Skill](/guide/ai-integration/lifeos-skill.md) first for Claude Code, Codex, and other skill-aware agents. The skill understands LifeOS-specific folders, templates, daily notes, tasks, and review workflows without requiring manual MCP server configuration.
Deep Ask also includes a built-in MCP (Model Context Protocol) server for tools that require MCP compatibility, allowing clients like Claude Desktop or Cursor to access your Obsidian vault through a local protocol endpoint.
### What is MCP?
MCP (Model Context Protocol) is an open protocol that allows AI applications to securely connect to external data sources and tools. In LifeOS workflows, treat MCP as the compatibility layer; if your AI agent can install skills, LifeOS Skill is the recommended entry point.
### Recommended: LifeOS Skill
For Claude Code, Codex, and other skill-aware agents, install LifeOS Skill:
```bash
npx skills add quanru/lifeos-skill
```
Then ask the agent:
```text
Check my lifeos configuration
```
Continue with MCP configuration only when your client specifically connects through MCP.
### MCP Compatibility Configuration
#### Claude Desktop MCP Compatibility Configuration
1. Make sure the Deep Ask plugin is enabled and running
2. Open the Claude Desktop configuration file:
* **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
3. Add the following configuration:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
4. Restart Claude Desktop
#### Cursor MCP Compatibility Configuration
If Cursor cannot use LifeOS Skill for this workflow, add the MCP server in Cursor settings:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
#### Claude Code MCP Compatibility Configuration
For Claude Code, LifeOS Skill is the recommended path. Create a `.mcp.json` file in your project root only when you need MCP compatibility:
```json
{
"mcpServers": {
"obsidian-lifeos": {
"url": "http://127.0.0.1:51377/mcp",
"headers": {
"Authorization": "Bearer YOUR_ACTIVATION_CODE"
}
}
}
}
```
### Available Tools
When you use LifeOS Skill, ask for these operations in natural language. If you must use MCP compatibility, the server exposes the following underlying tools for AI assistants:
#### File Operations
| Tool Name | Description |
| ------------------ | ----------------------------------- |
| `get_file_content` | Get the content of a specified file |
| `list_files` | List files in the vault |
| `list_tags` | List all tags in the vault |
| `search_by_tag` | Search content by tag |
| `save_chat` | Save conversation to a note file |
#### Task CRUD Operations
| Tool Name | Description |
| ------------- | --------------------------------------------------------------------------- |
| `create_task` | Create a new task with optional due date, time range, and multi-day support |
| `list_tasks` | List tasks with filtering by date, status, tags, folder, and pagination |
| `update_task` | Update task content, date, time, or completion status |
| `delete_task` | Delete a task (including its sub-items) |
#### Bullet (Fleeting Note) CRUD Operations
| Tool Name | Description |
| --------------- | ----------------------------------------------------------------- |
| `create_bullet` | Create a new bullet (fleeting note) with optional tags |
| `list_bullets` | List bullets with filtering by date, tags, folder, and pagination |
| `update_bullet` | Update bullet content |
| `delete_bullet` | Delete a bullet (including its sub-items) |
#### Periodic Notes Query
| Tool Name | Description |
| -------------------- | ------------------------------------------------------------------------------------------- |
| `get_periodic_notes` | Get periodic notes (yearly/quarterly/monthly/weekly/daily) with optional sub-period support |
**Parameters**:
* `year` (required): Year, e.g., 2024
* `quarter`: Quarter (1-4)
* `month`: Month (1-12)
* `week`: ISO week number (1-53)
* `day`: Day of month (1-31, requires month)
* `includeQuarters`: Include quarterly notes (only for yearly)
* `includeMonths`: Include monthly notes (for yearly/quarterly)
* `includeWeeks`: Include weekly notes (for yearly/quarterly/monthly)
* `includeDays`: Include daily notes
* `includeContent`: Include note content (default: true)
* `includeVirtualDocument`: Include virtual document with query results
**Usage Examples**:
```
Get the 2024 yearly note
→ { year: 2024 }
Get June 2024 monthly note with all daily notes
→ { year: 2024, month: 6, includeDays: true }
Get Q2 quarterly note with monthly and weekly notes
→ { year: 2024, quarter: 2, includeMonths: true, includeWeeks: true }
```
### Use Cases
* **Knowledge Retrieval**: Use LifeOS Skill first to search your notes for relevant information; MCP-compatible clients can use the same vault data through the server
* **Content Summarization**: Have AI read and summarize your note content
* **Cross-tool Collaboration**: In IDEs like Cursor, use LifeOS Skill when available and MCP when the IDE requires protocol-level access
* **Automated Organization**: Let AI help organize and archive your notes
* **Task Management**: Create, query, update, and delete tasks directly through AI assistants
* **Quick Capture**: Record fleeting thoughts and ideas as bullets through AI without opening Obsidian
### Important Notes
* Make sure Obsidian is open and Deep Ask plugin is running
* The MCP server default port is `51377`; LifeOS Skill does not require configuring this port manually
* Authorization uses your Deep Ask activation code
* Only supports local access (127.0.0.1) for security
## 🛠️ Troubleshooting
### Common Issues
**Q: AI does not reply or reply incorrectly?**
A: Check if the API Key is correct, and the network connection is normal
**Q: Unable to find related note content?**\
A: Check if the path filtering is set correctly, and check if the Dataview plugin is working properly
**Q: Plugin startup failed?**
A: Check if the Obsidian version meets the requirements, and the Dataview plugin is installed
**Q: Activation code invalid?**
A: Check if the email and activation code are correct, and contact the developer for support
### Log Debugging
1. Open the developer tools (`Ctrl/Cmd + Shift + I`)
2. View the error information in the Console tab
3. Troubleshoot based on the error information
## 📚 Best Practices
1. **Organize knowledge structure**：Establish a clear folder and tag system to facilitate AI retrieval
2. **Use context reasonably**：Select related files and tags to improve answer quality
3. **Classify conversation**：Create independent conversations for different topics
## 🚀 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/deep-ask-changelog.md).
---
url: /plugin/deepask/privacy.md
---
# Data Privacy
Your data security and privacy are our top priorities.
## DeepAsk AI Data Privacy Policy
### Local Storage
All preferences and conversations are stored locally in your browser. Access credentials remain on your device and are never transmitted to our servers.
### Data Transmission
When using the DeepAsk extension, your page data will be sent directly to your configured AI model provider. No third-party platforms will access this data.
### Privacy Considerations
What you need to focus on is the data privacy policy of the AI model provider you choose. We recommend that you carefully read and understand how they handle your data.
## Our Commitment
:::tip
DeepAsk AI does not collect, store, or access your personal data. Your data security is entirely in your own hands.
:::
---
url: /plugin/remosidian/pricing.md
---
# Plans
import { PricingTitle } from '../../../../theme/components/PricingTitle';
import { Pricing } from '../../../../theme/components/Pricing';
import { getFeatures, remosidianFeatures } from '../../../../theme/data/pricingFeatures';
---
url: /plugin/remosidian/remosidian.md
---
import { CommercialContent } from '../../../../theme/components/CommercialContent';
# Remosidian Overview
> Search and ask your Obsidian vault from your phone, without moving it to the cloud. **Free to use.**
Get it for free: [Remosidian official site](https://remosidian.pages.dev/)
## 📖 Introduction
[Remosidian](https://remosidian.pages.dev/) is for people who already trust Obsidian with their notes but still need files, search, and local AI when they step away from their computer. It consists of two parts:
* **Remosidian Host plugin** (`remosidian-host`): an Obsidian desktop plugin that turns your computer into a private, local-first host for your vault
* **Remosidian mobile app**: pair your phone with the host via a QR code, then browse, search, edit, and ask AI about your vault remotely
Your vault never leaves your machine — the phone gets a paired doorway, not a cloud clone.
***
## ✨ Main Features
* 📂 **Browse Obsidian files**: open folders, read Markdown, and follow wikilinks on the go
* 🔍 **Search your vault**: full-text search from your phone
* ✦ **Ask with vault context**: forgot what a note said? Ask from your phone while Claude or Codex reads context on the paired host
* 🏠 **Local-first host**: your vault stays on your computer; nothing is synced to a third-party cloud
* ⧉ **QR pairing**: bind the phone to the host with a short-lived QR code, no account required
* ↗ **Remote ready**: start with local access, then add a relay only when you need away-from-desk access
## 🚀 Quick Start
1. Install the **Remosidian Host** plugin in desktop Obsidian and enable it
2. Install the **Remosidian mobile app** on your phone — see the [official site](https://remosidian.pages.dev/) for download options
3. In Obsidian, open the Remosidian Host settings and show the pairing QR code
4. Scan the QR code with the Remosidian app — you are connected
For detailed installation and pairing steps, read the [Remosidian guide](https://remosidian.pages.dev/guide/).
## 💎 Free vs Pro
The Remosidian Host plugin and the core mobile experience (browse, search, ask, pairing, raw Markdown reading, and basic editing) are **free**. A [Remosidian Pro](/plugin/remosidian/pricing.md) in-app subscription unlocks advanced previews and editor blocks such as Excalidraw, embeds, and other enhanced Markdown rendering. You can still read and edit raw Markdown without a subscription.
---
url: /plugin/calendar/common.md
---
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
---
url: /plugin/life-os-pro.md
---
# Pro Features
import { CommercialContent } from '../../../../theme/components/CommercialContent';
import { ProductBoundaryNotice } from '../../../../../shared-site-theme/ProductComparison';
# Pro Features
Get link: [LifeOS Pro](/plugin/pricing.md)
> Visit Youtube for more information: https://www.youtube.com/watch?v=C1Ph\_j00\_Sc
Discover the transformative features of LifeOS Pro！
## 📑 Sidebar Task Management
> User Guide: [Sidebar Task Management](/guide/pro/task-view.md)
Sidebar task management also supports dragging tasks to the big calendar to plan your schedule!
## 📅 Schedule Planning (Big Calendar View)
> User Guide: [Calendar View](/guide/pro/calendar.md)
Effortlessly plan due dates for each task with simple drag-and-drop. Supports day view, week view, and month view to easily manage your time and boost efficiency every day!
### Month View
Month view displays the entire month's tasks in traditional calendar format, suitable for viewing and planning monthly schedules from a macro perspective.
* **Full Month Overview**: View the entire month's task distribution at a glance
* **Drag-and-Drop Scheduling**: Drag tasks from the sidebar to date cells to quickly set due dates
* **Quick Navigation**: Click on date numbers to quickly jump to the corresponding day view
### Week View
Week view displays a week's tasks and schedules in timeline format, precise to the hour, suitable for detailed time block planning.
* **Timeline Layout**: Horizontal axis shows seven days of the week, vertical axis shows 24-hour time scale
* **Time Block Drag-and-Drop**: Drag tasks to specific time slots, or drag to adjust task duration
* **Multi-day Tasks**: Tasks spanning multiple days are displayed as horizontal bars
### Schedule View
Schedule view displays future tasks and schedules in list format grouped by date, supporting infinite scroll to load more dates.
* **Timeline Display**: Arranged vertically by date, clearly showing each day's to-dos
* **Infinite Scroll**: Automatically loads more dates' tasks when scrolling down
* **Postpone Actions**: Quickly postpone tasks to tomorrow or a specific date
* **Recurring Task Expansion**: Automatically expands recurring tasks to their respective dates
### Four-Quadrant View
Four-quadrant view is based on the Eisenhower Matrix, categorizing tasks by "Importance" and "Urgency" dimensions, helping you focus on what truly matters.
* **Four Quadrants**:
* **Important & Urgent**: High/Medium priority + due within next 7 days
* **Important but Not Urgent**: High/Medium priority + no due date
* **Not Important but Urgent**: Low/No priority + due within next 7 days
* **Not Important & Not Urgent**: Low/No priority + no due date
* **Drag-and-Drop Categorization**: Drag tasks to different quadrants to automatically adjust priority and date
* **Custom Filtering**: Each quadrant supports custom filter conditions (day range, priority, task source)
### Day View
Day view displays a single day's task schedule in timeline format, precise to the hour, suitable for planning specific daily time arrangements.
* **Single-Day Timeline**: 24-hour time scale clearly shows the day's time allocation
* **Time Block Creation**: Click on empty time slots to quickly create new tasks
* **Drag Adjustment**: Drag tasks to adjust start time, drag edges to adjust duration
### Kanban View
Kanban view displays tasks as cards, supporting three grouping methods:
* **Group by Due Date**: Display tasks in columns by "Overdue", "Today", "Tomorrow", "This Week", "Later", "No Date" time dimensions
* **Group by Priority**: Display tasks in columns by priority (High, Medium, Low, None)
* **Group by Tag**: Display tasks categorized by tags
Supports dragging tasks to different columns to quickly modify due dates or priorities, perfect for scenarios requiring quick browsing and organizing tasks.
### Timeline View
Timeline view displays tasks in Gantt chart format, with time on the horizontal axis and tags grouped on the vertical axis, visually presenting task duration and distribution.
* **Multiple Time Units**: Supports switching between "Day", "Week", "Two Weeks", "Month" time ranges
* **Inbox Area**: Tasks without scheduled times are displayed in the inbox area at the bottom, which can be dragged to the timeline for planning
* **Drag Adjustment**: Drag task bars to adjust start/due dates for intuitive time planning
Timeline view is particularly suitable for scenarios requiring a macro view of project progress and task distribution.
## 📅 Remote Calendar Subscription (Two-way Sync)
> User Guide: [Calendar Subscription](/guide/pro/calendar-sub.md)
Supports subscribing to remote calendars via ICS and CalDAV protocols, such as TickTick and Feishu Calendar, allowing you to centrally manage all your calendar data for easy viewing and planning.
Supports two-way sync via CalDAV protocol with [iCloud Calendar](/guide/pro/calendar-sub.md#subscribe-to-icloud-calendar-two-way-sync), [Google Calendar](/guide/pro/calendar-sub.md#subscribe-to-google-calendar-two-way-sync), and other [CalDAV Calendar](/guide/pro/calendar-sub.md#subscribe-to-caldav-calendar-two-way-sync) services, enabling task reminders across iOS, Android, macOS, Windows, Linux, and other platforms.
## 📝 Advanced List
> [Advanced List](/guide/pro/advanced-list.md)
Are you troubled by long tasks, bullet notes, and file lists? This time, we bring you the ultimate solution!🔍
👉 New Features
1️⃣ Page Turning: Even long lists can be easily browsed!📖
2️⃣ Sorting: Sort by date, status at will!📅
3️⃣ Search: Text and date search with one click, everything is under control!🔍
Not only that, the task collection and task completion list in the periodic notes also fully support these new features! Want to find a specific task or record? Just a few seconds!⏱️
### Search
### Sort
### Filter
## 🏡 Home Page View
> [Home Page View](/guide/pro/home-view.md)
Your central command center for life and work. Our sleek, user-friendly dashboard provides an at-a-glance overview of your inputs, projects, tasks, and outputs, enabling seamless coordination of all aspects of your life.
## Workflow
One-stop project management, from input to delivery, forming a closed loop, linking each step, driving the project forward steadily.
## Habit statistics
Not just recording, but also analyzing, statistics on the overall completion of the habit module in the diary, scientifically understanding your habit formation cycle.
## Flash random
Activate your historical notes, sparking endless creativity and allowing old thoughts to grow new branches.
## 📒 Theme Notes
> [Theme Notes](/guide/pro/theme-note.md)
Experience our upgraded note-taking system, evolved from the PARA method. With customizable options and an intuitive interface, Theme Notes simplifies the process of capturing, organizing, and utilizing information, making it accessible for users at all levels.
## 📱 Convenient Features
> [Convenient Features](/guide/pro/convenient.md)
1. Automatically insert timestamps in daily records
2. Right-click tags to create theme notes
3. Right-click on theme folders to quickly circulate
4. Click on folders to jump to theme index files
5. Click on file titles to expand and focus on sidebar files
6. When opening today's daily note, automatically focus on the last line of the daily record module
## 🔥 More Features in Development
We're constantly working on new features to enhance your experience.
New features are constantly being added! For the complete changelog, please visit [Changelog](/news/lifeos-pro-changelog.md).
---
url: /plugin/life-os.md
---
# Basic
> Visit Youtube for more information: https://www.youtube.com/watch?v=m-hD48UYRts
## Create Notes Visually
> See details in [Guide](/guide/free/create-note.md)
It is recommended to work with [Templater](https://silentvoid13.github.io/Templater/), Be sure to enable the "Trigger Templater on new file creation" option of the Templater plugin, so that you can use the template variables and functions provided by [Templater](https://silentvoid13.github.io/Templater/).
### Create Periodic Notes
### Create Theme Notes
## Main System
### Knowledge Management System
> See details in [Guide](/guide/core/main-system.md#knowledge-management-system)
### Periodic Notes System
> See details in [Guide](/guide/core/main-system.md#periodic-notes-system)
## Sub System
> See details in [Guide](/guide/core/sub-system.md)
### Task Management
### Time Management
Project time tracking and review
## Usememos Sync
> Capture daily inspiration quickly by [usememos](https://www.usememos.com/)
> See details in [Usage](/guide/readme/free.md#daily-record)
---
url: /plugin/pricing.md
---
# Plans
import { PricingTitle } from '../../../theme/components/PricingTitle';
import { Pricing } from '../../../theme/components/Pricing';
import { ProductBoundaryNotice } from '../../../../shared-site-theme/ProductComparison';
:::tip TL;DR
Already use Obsidian? Choose LifeOS Pro, and purchase DeepAsk separately only when you need AI inside Obsidian. If you want an integrated workspace with less plugin setup, consider [Aino Desktop Pro](https://aino.md/pricing/).
:::
LifeOS Pro, Calendar Pro, and DeepAsk are three separately purchased and activated Obsidian plugins. Buying one does not grant the other two, Aino Desktop Pro, or Aino Mobile Pro.
---
url: /news/lifeos-pro-changelog.md
---
# LifeOS Pro Changelog
> More details with pictures, please check [LifeOS for Obsidian](https://medium.com/@quanru)
## 3.1.0-beta.13
* Fixed shared settings switches and restored file, task, record, and topic creation actions in advanced lists.
* Improved the periodic-note sidebar, mobile layout, and button styles while isolating desktop-only creation-dialog dependencies.
## 3.1.0-beta.12
* Fixed the top-left launcher highlight so it follows the active Obsidian view after navigation.
* Fixed vault-path resolution when restoring AI snapshot indexes, improving workbench and review data recovery.
* Rebuilt the beta package from the latest stable baseline and refreshed its signature and integrity metadata.
## 3.1.0-beta.11
* Optimized update checks by briefly caching each plugin and release-channel result and deduplicating concurrent requests, reducing redundant network traffic, server logs, and resource use.
* Hardened shared Obsidian plugin builds and release artifact serialization so concurrent builds cannot overwrite or invalidate one another.
## 3.1.0-beta.10
* Added a unified in-settings feedback flow with optional privacy-sanitized diagnostics and responsive Obsidian light, dark, and narrow layouts.
* Hardened context handoff across AI Home, Workbench, and DeepAsk together with safer local CLI execution, preventing lost context, stale conversations, and unsafe commands.
* Expanded regression gates for conversation switching, periodic-note selection, no-write AI results, and host theme adaptation while preserving existing Aino Desktop shared-component behavior.
## 3.1.0-beta.9
* Refined the mobile note creator and settings surface: periodic notes retain a compact full-week interaction, while overflowing settings tabs remain reachable and automatically reveal the active item.
* Fixed compressed actions, residual shadows, and high-contrast surfaces across AI Workbench, Smart Organize, and Review in light, dark, narrow, and mobile layouts.
* Expanded responsive, theme-isolation, and real Obsidian regression coverage for shared views while preserving Aino Desktop compatibility.
## 3.1.0-beta.8
* Unified Obsidian semantic theme colors across settings, periodic notes, calendars, tasks, and AI surfaces, reducing harsh white backgrounds, shadows, and dividers while improving dark, narrow, and mobile layouts.
* Fixed AI Workbench counting repeated reads and alternate path forms of the same file as separate discoveries; completed runs now merge read counts and discovery rows by the resolved vault file.
* Expanded real DeepAsk workflow coverage for AI Review, Smart Organize, and Workbench, validating context handoff, report projection, completion receipts, and persisted conversations end to end.
## 3.1.0-beta.7
* Rebuilt the beta package from the source that passed the commit gates. It contains the same features as `3.1.0-beta.6` with refreshed signing and integrity metadata.
## 3.1.0-beta.6
* Completed Obsidian-native AI Home, Workbench, Board, Review, and Smart Organize flows so recalibration, file navigation, and host actions stay aligned with the shared Aino Desktop behavior.
* Refined daily and weekly selection, month navigation, created-note indicators, and compact spacing in the periodic-note creator while preserving the familiar standalone note-creation workflow.
* Fixed theme surfaces, primary-action text, embedded icons, and spacing across settings forms, AI Review lists, and shared plugin views in light, dark, and narrow layouts.
## 3.1.0-beta.5
* Rebuilt the shared-UI beta from the latest verified `main` revision after the stable-line merge, with refreshed signing and integrity metadata for the downloadable bundle.
## 3.1.0-beta.4
* Rebuilt the shared-UI beta from the final `main` revision and refreshed integrity metadata so the downloadable bundle matches the verified source; UI and behavior remain aligned with beta.3.
## 3.1.0-beta.3
* Refined the shared DeepAsk context and composer surfaces with quieter theme-aware groups, compact tags, and clearer attachment controls in narrow Obsidian sidebars.
* Improved localized AI composer guidance and active-control colors while preserving Aino Desktop's styling baseline.
* Strengthened cross-host release, theme-isolation, and packaged-artifact verification for the shared component migration.
## 3.1.0-beta.2
* Further unified the shared Home, Workbench, Board, and AI Workbench view boundaries, while fixing relative-note paths and host navigation after merging the stable branch.
* Refined Obsidian settings forms, mobile layouts, and theme adaptation to reduce wasted space, wrapping, and high-contrast surfaces in narrow sidebars.
* Expanded shared-component, theme-isolation, and cross-host regression coverage so Obsidian adaptations do not alter Aino Desktop styling.
## 3.1.0-beta.1
* Moved Home, Workbench, Board, Pomodoro, Quick Notes, AI Review, and other primary surfaces onto the same view and feature models used by Aino Desktop, reducing cross-host behavior drift.
* Preserved the familiar note-creation form while rebuilding periodic and topic-note interactions with native components; daily selection now includes week-number shortcuts, while weekly selection operates on full rows.
* Improved dark-theme, narrow-sidebar, and mobile behavior across Obsidian, fixing dialog dismissal, navigation layout, button overflow, themed surfaces, and several selection-state issues.
## 3.0.89
* Refined workspace initialization and guided onboarding for more reliable state restoration and settings handoff when first configuring a LifeOS vault.
## 3.0.88
* Fixed calendar drag-and-drop updating the wrong copied task when multiple tasks share a title or `block id`; the selected task is now resolved by its original source line.
## 3.0.87
* Expanded curated Skills and cross-product recommendation entry points so related capabilities are easier to discover from a LifeOS workspace.
* Improved plugin integrity verification for large or busy vaults, reducing repeated reads and making activated settings load more reliably.
## 3.0.86
* Fixed repeated integrity reads in large or busy vaults leaving activated settings tabs blank indefinitely.
* Added a visible verification loading state and bounded file-read handling so stalled checks no longer fail silently.
## 3.0.85
* Fixed advanced-list update dates being empty; the displayed date now comes from the source file's actual modification time.
* Fixed index pages intermittently rendering no results for `BulletListByTag`, including tagged nested bullets.
## 3.0.84
* Rebuilt the complete production package and refreshed signed integrity metadata for this release batch.
## 3.0.83
* Fixed version checks being triggered repeatedly after React rerenders, preventing requests from accumulating until Obsidian reports `ERR_INSUFFICIENT_RESOURCES`.
## 3.0.82
* Added AI Home today and board views so the current workspace can be reviewed and acted on more quickly.
* Improved LifeOS domain capabilities and shared runtime boundaries for more reliable behavior across hosts.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.81
* Added an Aino Mobile recommendation and author-page entry to the activation settings, making it easier to continue the workflow on mobile and discover the LifeOS product line.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.80
* Hardened the shared runtime architecture used by LifeOS Pro so plugin boundaries, host storage access, and release verification remain safer across desktop and Obsidian environments.
* Improved sync-backup and workspace context handling in the shared LifeOS foundation, reducing inconsistent task, calendar, and agent-context behavior after local or remote updates.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.79
* Improved LifeOS file-list query results with file path and tag metadata for consistent tag presentation across hosts.
* Hardened calendar task grouping and event previews to reduce inconsistencies after sync updates.
* Improved incremental reconciliation for external and ambiguous Markdown edits so plugin views refresh more reliably.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.78
* Improved task checkbox handling and external Markdown reconciliation to reduce state misclassification when local edits, external writes, and sync refreshes overlap.
* Hardened vault sync-scope detection to reduce accidental over-syncing or missed files when directory boundaries are ambiguous.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.77
* Updated time-management docs to clarify that the daily total time should be entered separately at the end of the project list and used as the baseline for project-time percentages.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.76
* Hardened task content parsing, block id detection, and local / remote calendar synchronization to reduce drift in task status, date fields, and remote events after multi-device sync.
* Improved remote calendar reading and visibility handling so CalDAV and other remote calendars keep enabled state and event lists aligned more reliably during settings changes and refreshes.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.75
* Improved incremental refresh after external Markdown file changes, reducing stale data in calendar, task, and periodic-note views.
* Fixed Calendar / Periodic statistics that could show inconsistent time rollups after source data changed; area-theme time totals now align more reliably with the latest task data.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.74
* Theme / PARA folder sync now watches only the directories for the enabled mode and respects the configured index filename type, avoiding incorrect sync work from inactive folders or different index naming rules.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 3.0.73
* Fixed open calendar and task views not always updating after another application writes Markdown tasks in the background; filename-less and rapid file changes now reconcile the index incrementally without duplicating recurring tasks.
* Unified the large-calendar refresh button around a lightweight reload of local tasks plus remote calendar data when enabled, without rebuilding the full index.
## 3.0.72
* Fixed Dataview metadata changes not always refreshing the large calendar, task lists, and related views immediately; rapid file updates now trigger follow-up refreshes more reliably.
* Improved Periodic Notes and Memos daily templates so empty daily notes stay lightweight and focus the intended record position when opened.
* Updated multilingual example-vault settings and hardened task conversion so recurrence rules, date fields, and task status are preserved more consistently.
## 3.0.71
* Maintained the current production package with the latest large-calendar live refresh, periodic-note, and example-template improvements
* Updated release archives, version indexes, and integrity metadata so downloads, updates, and activation verification remain consistent
## 3.0.70
* Fixed the large calendar not detecting tasks added or edited directly in Markdown files until the view was reopened; file changes that arrive during loading now reliably trigger a follow-up refresh
## 3.0.69
* Fixed recurring tasks with start/end bounds being treated as multi-day events in Schedule view, which caused duplicate entries to accumulate on later dates
## 3.0.68
* Added a Memos template and migration guide that converts existing vaults without discarding their content, with clearer template selection, onboarding, and migration checks
* Unified LifeOS query handling for themes, periodic notes, and related views, improving cache, document generation, and rendering consistency while reducing duplicate work
* Fixed rapid changes across multiple settings sometimes saving only the last field; updates within the same debounce window are now merged
* Improved localized activation errors and targeted plugin reloads after updates; reload failures now report failure instead of claiming the update succeeded
## 3.0.67
* Switched index-cache invalidation to a build fingerprint so existing caches rebuild reliably after Markdown parser changes
* Added full-width Chinese parentheses to tag parsing and improved boundary detection around links, paths, and adjacent characters
* Added related project time to area-theme rollups, including area-level duration, total time, and percentage
* Fixed meaningful spaces in theme-template and periodic-note configuration paths being removed and causing template or folder lookup mismatches
## 3.0.66
* Fixed wikilinks with block references and heading fragments (for example, `[[2026-07-16^#Habit Check-in]]`) incorrectly indexing the fragment as a tag; tag indexing now ignores heading fragments inside wikilinks
* Updated the shared Markdown index format so existing indexes rebuild automatically with the corrected tag parser
## 3.0.65
* Fixed daily templates rendering `{{weekYear}}-W{{week}}` as `gggg-Www`; week years and week numbers are now calculated directly and honor the configured locale and first day of the week
* Kept single-digit weeks consistently zero-padded as `W01`, aligning template output with weekly-note paths
## 3.0.64
* Regenerated and redeployed the complete release package and integrity metadata to address verification-code errors that some users could encounter during installation or activation
## 3.0.63
* Fixed historical periodic notes opened after plugin startup still showing template directives such as `{{if weekday}}`, `{{else}}`, and `{{endif}}`; conditions are now resolved from the note date while template source files keep their directives
* Improved template post-processing reliability on slow storage such as iCloud and after the service is re-enabled, avoiding missed processing or duplicate concurrent writes; ordinary notes and template source files are not rewritten merely by opening them
* Made legacy template-syntax migration safer: only fully migratable templates are rewritten automatically, while templates with mixed or unknown Templater syntax remain unchanged for manual review instead of being partially migrated
## 3.0.62
* Added column reordering to advanced list column settings; visibility and order are saved separately, the main column stays fixed, and hidden columns stay hidden when order changes
## 3.0.61
* Fixed reopened tasks or tasks switched back to a blank checkbox state still appearing completed because of stale status data; task display now stays aligned with the task text
* Fixed large-calendar checkbox and status-style changes sometimes not refreshing after task status updates
* Fixed month-view weekday headers gaining day numbers when 24-hour time is enabled, while day and week views keep their date-aware headers
## 3.0.60
* Fixed cold starts duplicating same-day recurring tasks in the large calendar; toggling or adding tasks now keeps the count consistent
## 3.0.59
* Fixed a large-calendar blank screen when clicking Create Task or date cells if FullCalendar renders a temporary event without its original task payload
* Improved calendar drag compatibility so drag interactions no longer break in some environments
## 3.0.58
* Added a "Don't remind again" option to the template syntax migration prompt; manual migration remains available from settings
* Fixed daily-template migration truncating complex date expressions, so previous/next daily links and task dates keep the correct relative date
* Fixed template post-processing for Chinese and custom daily-note path formats created through Obsidian Daily Notes, using the note date instead of the file creation time
## 3.0.57
* Fixed recurring tasks losing their current due date in advanced lists, Inbox, Schedule, and overdue grouping; the next recurrence date is now used for display, sorting, and filtering
* Preserved the original recurrence rule instead of writing the computed next due date back to the task, keeping large-calendar display and sync results stable
## 3.0.56
* Added an "编辑模版" entry on daily, weekly, PARA, and theme pages so the matching template can be opened directly from the current note
* Added deep links from AI, calendar, Home, and remote-calendar event surfaces to their related settings, reducing the steps needed to inspect or configure connected features
## 3.0.55
* Fixed remote calendar push gating so disabling the write calendar or related push no longer triggers sync actions or deletes remote events by mistake
* Aligned manual push buttons and calendar task actions with the real writable-calendar state for LifeOS Pro and shared calendar views
## 3.0.54
* Rebalanced large calendar time-grid density so the default height feels closer to the pre-fine-grained calendar layout while compact mode stays readable
* Fixed compact one-hour time-grid tasks so at least one title line and the `18:00-19:00` style time range remain visible
## 3.0.53
* Tightened compact time-grid density so dense calendar views can show more hours without wasting vertical space
* Added clearer Core Concepts guide links so new users can understand pressure-free capture and retrieval before getting started
## 3.0.52
* Fixed removed local tasks sometimes leaving matching remote calendar events behind; remote cleanup is now more reliable
* Preserved tag-only task titles when syncing to remote calendars, so tag-only tasks no longer become empty events
## 3.0.51
* Fixed Google / CalDAV sync failures caused by some remote event formats, making remote event write-back more reliable
* Improved duplicate-push protection so local tasks and remote events match more reliably
* Added the large calendar time-grid height setting and maintained the current stable release content
## 3.0.50
* Fixed time-grid event cards so the bottom time range stays visible instead of being covered by the title or checkbox layout
* Improved timed task editing and display for exact minute values, including compact ranges such as `8:25-12:10`
## 3.0.49
* Maintained the current stable LifeOS Pro package so user update content stays complete
* Carried forward remote calendar duplicate-push safeguards and time-grid all-day drop fixes in the latest stable package
## 3.0.48
* Fixed Kanban initial loading sometimes missing postponed in-progress secondary tasks; initial loading and later file changes now stay consistent
* Fixed unstable time-grid drag detection for all-day tasks, so moving tasks between all-day and timed slots writes the intended date/time
* Maintained stable release content after version 3.0.47
## 3.0.47
* Fixed Google / CalDAV sync creating duplicate remote events when a task lacks stable matching information; unreliable pushes are now skipped
* Fixed remote duplicate cleanup so refreshed or moved CalDAV events are matched reliably
* Improved timed calendar task display and drag write-back for time ranges and multi-day placement
## 3.0.46
* Added an optional Time Range column to advanced task tables, with display and sorting for task start/end times; it stays hidden by default so existing table layouts are unchanged
* Improved calendar task-card title and checkbox layout to reduce squeezed checkboxes or overflowing titles in compact views
## 3.0.45
* Fixed bulk postponing parent tasks and indented subtasks from the same file in Inbox / Schedule views only moving one or two items; bulk write-back is now more reliable
## 3.0.44
* Fixed dragging a timed task end to `24:00` writing the due date as the next day and making the task look cross-day or all-day; `21:00 - 24:00` now stays on the same due date
* Fixed same-day `24:00` time blocks such as `21:30 - 24:00` sometimes being placed in the all-day area, and improved the displayed end label so it no longer appears as 12:00 AM
* Unified task display-text cleanup so Kanban, calendar, and sync titles no longer turn `19:00 - 24:00 world` into `- world` or accidentally remove the task body
## 3.0.43
* Fixed the native FullCalendar right-edge resize handle not appearing on multi-day tasks in the large calendar
* Fixed timeline drag moves updating only the due date instead of shifting the start and due dates together
* Fixed date-only range tasks being written back as `00:00 - 24:00` after date drag or resize; time ranges are now written only when the task already had time or is explicitly dropped from the all-day area into a timed slot
* Fixed dragging a task from the all-day area into a timed grid slot not writing the target start/end time
* Fixed single timestamps such as `10:00 hello` being treated as calendar time blocks; dragging them into a timed slot now preserves the timestamp and inserts the new `HH:mm - HH:mm` range after it
* Enabled LifeOS task suggestions on mobile while keeping the desktop suggestion experience consistent with Obsidian Tasks when available
## 3.0.41
* Fixed multi-day all-day tasks showing `No start` in the task popover even when the task already had start and due dates
## 3.0.39
* Upgraded the task popover date control to a Start - Due range editor, so `🛫` start dates and `📅` due dates can be edited separately, including specific start/end times
* Fixed due-date-only edits from task popovers or large calendar views clearing existing start dates and time blocks
## 3.0.37
* Fixed task autocomplete in the editor when Obsidian Tasks is not installed; common task keywords now open LifeOS suggestions
## 3.0.36
* Fixed recurring tasks not creating the next task when checked from calendar/event-card surfaces outside the editor; LifeOS now uses Obsidian Tasks when available and falls back to its own recurring-task generation when the Tasks plugin is not installed
## 3.0.35
* Improved task query stability so nested tasks, grouped task rows, and incremental index updates stay consistent across advanced lists, calendar views, and editor status cycling
* Unified custom task status styling across LifeOS task surfaces, reducing mismatched checkbox/status display between tables, inbox, schedule, kanban, and event cards
## 3.0.32
* Improved Obsidian Live Preview task checkbox handling so status changes are more reliable when clicking real editor checkboxes
* LifeOS now handles editor checkbox clicks more reliably, reducing cases where other status-toggle behavior takes over first
## 3.0.31
* Fixed editor checkbox handling starting too late, so Live Preview task status changes more reliably follow the LifeOS custom status cycle
* Improved editor checkbox hit detection so clicks on the checkbox visual layer, label, or nested checkbox elements resolve to the same task status cycle
## 3.0.30
* Fixed daily-record tasks with a leading record timestamp plus a later time block, such as `17:41 10:00 - 10:30 ...`, being treated as all-day tasks instead of scheduled time-block tasks
## 3.0.29
* Fixed task checkbox clicks in Obsidian Live Preview so LifeOS follows the configured status cycle more reliably
* Editor task status changes now write back more cleanly, avoiding stale completion data when a completed task returns to an open state
## 3.0.28
* Changed the default task status cycle to Todo -> In Progress -> Done -> Todo, and migrated old default task status settings so editor checkbox clicks no longer stay in a two-state toggle
## 3.0.27
* Fixed an editor checkbox issue so custom task status clicks reliably follow the configured status cycle
## 3.0.26
* Fixed Obsidian editor checkbox clicks so custom task statuses follow the configured next-status cycle instead of falling back to Obsidian's native todo/done toggle
## 3.0.25
* Fixed task preview popovers in Kanban and calendar views so edited indented child content refreshes without leaving and re-entering the calendar
* Fixed task checkbox clicks to follow the configured custom task status cycle instead of hardcoding todo/done toggles
## 3.0.24
* Fixed incremental Obsidian task parsing so `[/]` and custom checkbox statuses keep appearing in Kanban after files change or local calendar data refreshes
## 3.0.23
* Improved task previews and date editing so task cards in calendar, task lists, and advanced lists preserve richer child-task and date context
* Fixed inconsistent custom task status, task timestamp, and Markdown task parsing behavior across views, reducing status or date display issues after task sync
## 3.0.22
* Fixed cross-plugin settings updates sometimes affecting LifeOS Pro state when multiple LifeOS plugins are enabled
## 3.0.19
* Updated the bundled LifeOS AI guidance with clearer topic maintenance workflows and examples
* Improved bundled AI guidance install and update behavior so installed content is less likely to lag behind
* Added a command-line entry for installing or updating the bundled AI guidance
## 3.0.18
* Fixed the note-create weekly picker showing English weekday names and starting the week on Sunday under Chinese locale; it now uses Chinese weekday names and a Monday week start
* Adjusted the AI Connect settings tab so LifeOS Pro keeps only the necessary AI guidance install / update entry
## 3.0.17
* Fixed clicking a week (e.g. week 23) in the note-create calendar jumping to / creating the previous week (week 22) under English locale: weekly note week numbers now match the week numbers shown in the calendar (Chinese locale was unaffected)
## 3.0.16
* Fixed built-in template snapshot variables such as `{{snapshot:Project}}` not detecting `*.README.md` project index files in readme index mode
* Updated example templates and reduced external plugin requirements for new users
* Removed `[createFile]` debug logs from periodic note creation
## 3.0.15
* Fixed `LifeOS` code blocks sometimes rendering as plain code instead of advanced lists when periodic notes open before vault indexing finishes
## 3.0.14
* Fixed periodic note templates sometimes failing when the app is still getting ready
## 3.0.13
* Fixed the Obsidian third-party plugin list sometimes hiding the settings button by registering the settings tab before vault indexing starts
## 3.0.12
* Added the AI Connect settings tab for related AI install and update entries
* Fixed settings white-screen and loading failures
* Fixed shared settings pages loading incorrectly in some environments
## 3.0.11
* Fixed dropdowns in Obsidian's detached settings window drifting to the main window or becoming hard to select
* Fixed settings tab highlight not following the active tab
* Fixed duplicate input borders in settings fields
* Fixed possible settings white-screen after upgrade and plugin state display issues
## 3.0.0
* Added device management: view device usage, refresh the device list, and unbind unused devices from plugin settings
* Added a manual update entry, making it easier to get the latest plugin when automatic updates fail
* Added task default start dates for new tasks, including today, tomorrow, day after tomorrow, and next week
* Added configurable task delay days with delay-to-today support for quick and bulk overdue actions
* Added Kanban tag column sorting by task count, alphabetical order, and manual drag ordering
* Added template variable help and support for inserting theme snapshots in templates
* Added custom periodic note path awareness in the note creation panel, so existing-note markers follow configured paths
* Added Memos 0.28 compatibility for more reliable daily record sync with newer Memos versions
* Improved startup, search, and context loading for large vaults, especially when multiple LifeOS plugins are enabled together
---
url: /news/calendar-pro-changelog.md
---
# Calendar Pro Changelog
> More details with pictures, please check [LifeOS for Obsidian](https://medium.com/@quanru)
## 2.1.0-beta.13
* Fixed shared settings switches and improved narrow-screen buttons and mobile theme compatibility.
* Rebuilt the beta package from the latest stable baseline with refreshed signatures and integrity metadata.
## 2.1.0-beta.12
* Rebuilt the calendar beta package from the latest stable baseline while preserving existing behavior and refreshing signature and integrity metadata.
## 2.1.0-beta.11
* Optimized update checks by briefly caching each plugin and release-channel result and deduplicating concurrent requests, reducing redundant network traffic, server logs, and resource use.
* Hardened shared Obsidian plugin builds and release artifact serialization so concurrent builds cannot overwrite or invalidate one another.
## 2.1.0-beta.10
* Added the unified feedback entry to shared settings with optional privacy-sanitized diagnostics.
* Refined native element semantics, theme adaptation, and narrow-layout behavior across shared controls, with additional periodic-note and host-theme regression gates.
## 2.1.0-beta.9
* Refined the shared mobile settings surface so narrow tab strips no longer clip from both edges and automatically reveal the active tab after navigation.
* Continued aligning shared controls with Obsidian semantic colors, compact spacing, and mobile touch targets to reduce overflow and host-style conflicts.
## 2.1.0-beta.8
* Unified Calendar Pro and shared task and settings controls with Obsidian semantic theme colors, reducing excessive surface contrast, shadows, and dividers.
* Improved button text, form spacing, calendar previews, and task-area readability across light, dark, narrow, and mobile layouts.
## 2.1.0-beta.7
* Rebuilt the beta package from the source that passed the commit gates. It contains the same features as `2.1.0-beta.6` with refreshed signing and integrity metadata.
## 2.1.0-beta.6
* Refined shared Obsidian settings and select controls, fixing visibility, clear, and tag-close icons that were overridden by host button styles.
* Improved control contrast, keyboard focus feedback, and release regression coverage across light, dark, and narrow Calendar Pro layouts.
## 2.1.0-beta.5
* Rebuilt the shared-calendar beta from the latest verified `main` revision after the stable-line merge, with refreshed signing and integrity metadata for the downloadable bundle.
## 2.1.0-beta.4
* Rebuilt the shared-calendar beta from the final `main` revision and refreshed integrity metadata so the downloadable bundle matches the verified source; UI and behavior remain aligned with beta.3.
## 2.1.0-beta.3
* Refined shared theme adaptation and compact-control behavior so Calendar Pro remains clear in narrow, dark, and mobile Obsidian layouts.
* Updated the shared plugin package with the latest cross-host navigation and component-isolation fixes without changing Aino Desktop's visual baseline.
* Expanded packaged-artifact and release verification for the shared Obsidian plugin build.
## 2.1.0-beta.2
* Further consolidated the shared Aino Desktop and Obsidian calendar view, aligning task titles, previews, period switching, and relative source-path handling.
* Refined theme colors, narrow-sidebar behavior, and mobile layouts to reduce clipped controls and labels in constrained widths.
* Added cross-host build and visual-isolation coverage so shared behavior still follows each host's native theme.
## 2.1.0-beta.1
* Moved the calendar surface onto the shared Aino Desktop and Obsidian view component, aligning task creation, period switching, event previews, and refresh behavior.
* Improved narrow-sidebar and mobile layouts so header actions no longer overlap, truncate their labels, or overflow horizontally.
* Fixed React runtime compatibility in the Obsidian bundle and expanded cross-host regression coverage for the shared calendar.
## 2.0.60
* Improved responsive calendar layout, sidebar state, and theme-color handling for more consistent browsing and interactions across window sizes.
## 2.0.59
* Fixed calendar drag-and-drop updating the wrong copied task when multiple tasks share a title or `block id`; the selected task is now resolved by its original source line.
## 2.0.58
* Improved shared plugin integrity verification, reducing repeated reads and activation waits in large or busy vaults.
* Synced the latest LifeOS product recommendation and shared release-infrastructure updates.
## 2.0.57
* Fixed repeated integrity reads in large or busy vaults leaving activated settings tabs blank indefinitely.
* Added a visible verification loading state and bounded file-read handling so stalled checks no longer fail silently.
## 2.0.56
* Rebuilt the complete production package and refreshed signed integrity metadata for this release batch.
## 2.0.55
* Fixed version checks being triggered repeatedly after React rerenders, preventing requests from accumulating until Obsidian reports `ERR_INSUFFICIENT_RESOURCES`.
## 2.0.54
* Improved shared LifeOS runtime and domain boundaries for more reliable Calendar Pro behavior across hosts.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.53
* Promoted the signed activation integrity protections, component runtime verification, and startup guards from 2.0.53-beta.1 into the stable release.
* Updated the production package, version index, and integrity metadata so calendar sync, downloads, updates, and authorization checks remain consistent.
## 2.0.53-beta.1
* Hardened signed activation integrity for Calendar Pro and the shared Obsidian plugin foundation, reducing activation failures caused by mismatches between downloads, release archives, and verification values.
* Added component runtime verification and delayed activation guards so startup, component mounting, and callback mismatches are surfaced earlier.
* Expanded authorization and integrity coverage across signature validation, component verification, and mobile startup paths.
## 2.0.52
* Hardened shared task and calendar synchronization behavior so Calendar Pro stays more consistent after local edits, remote refreshes, and provider-side delete recovery.
* Improved release-time compatibility checks for the shared Obsidian plugin bundle, reducing the risk of publishing packages with mismatched shared runtime assumptions.
* Updated the version index, release archive, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.51
* Hardened task content parsing, block id detection, and task-calendar synchronization to reduce drift in task status, date fields, and remote events after sync.
* Improved remote calendar reading and visibility handling so CalDAV and other remote calendars keep enabled state and event lists aligned more reliably during settings changes and refreshes.
* Updated the version index, release archive, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.50
* Improved lightweight refresh after external Markdown task changes so open calendar and task views stay aligned with the latest data more reliably.
* Fixed inconsistencies in task time ranges, periodic statistics, and area time rollups after calendar source data changes.
* Updated the version index, release archive, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.49
* Maintenance release that keeps Calendar Pro aligned with the latest stable shared LifeOS plugin foundation.
* Updated the version index, release archive, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.48
* Fixed open calendar and task views not always updating after another application writes Markdown tasks in the background; filename-less and rapid file changes now reconcile the index incrementally without duplicating recurring tasks.
* Unified the refresh button around a lightweight reload of local tasks plus remote calendar data when enabled, without rebuilding the full index.
## 2.0.47
* Fixed Dataview metadata changes not always refreshing the large calendar and task-related views immediately; file changes during loading now trigger follow-up refreshes more reliably.
* Hardened recurring-task and date-field conversion, reducing status and schedule display differences after refresh, sync, or reload.
* Continued polish for Periodic Notes settings persistence and entry points, with example-vault configuration updates kept in sync.
## 2.0.46
* Maintained the current production package with the latest recurring-task, Schedule view, and large-calendar refresh fixes
* Updated release archives, version indexes, and integrity metadata so downloads, updates, and activation verification remain consistent
## 2.0.45
* Fixed recurring tasks with start/end bounds being treated as multi-day events in Schedule view, which caused duplicate entries to accumulate on later dates
## 2.0.44
* Added stronger safeguards for remote-calendar orphan cleanup: remote events are no longer removed while the local index is empty or incomplete, and missing tasks must be confirmed across scans before cleanup
* Fixed rapid changes across multiple Calendar Pro settings sometimes saving only the last field; updates within the same debounce window are now merged
* Improved localized activation errors and targeted plugin reloads after updates; reload failures now report failure instead of claiming the update succeeded
## 2.0.43
* Rebuilt and redeployed the Calendar Pro production package, version archive, and integrity metadata so downloads, updates, and activation verification remain consistent
## 2.0.42
* Regenerated and redeployed the complete release package and integrity metadata to prevent update or activation failures caused by mismatches between downloads, version archives, and verification values
## 2.0.41
* Fixed reopened tasks or tasks switched back to a blank checkbox state still appearing completed because of stale status data; task display now stays aligned with the task text
* Fixed large-calendar checkbox and status-style changes sometimes not refreshing after task status updates
* Fixed month-view weekday headers gaining day numbers when 24-hour time is enabled, while day and week views keep their date-aware headers
## 2.0.40
* Fixed cold starts duplicating same-day recurring tasks in the large calendar; toggling or adding tasks now keeps the count consistent
## 2.0.39
* Fixed a large-calendar blank screen when clicking Create Task or date cells if FullCalendar renders a temporary event without its original task payload
* Improved calendar drag compatibility so drag interactions no longer break in some environments
## 2.0.38
* Added a "Don't remind again" option to the template syntax migration prompt; manual migration remains available from settings
* Fixed daily-template migration truncating complex date expressions, so previous/next daily links and task dates keep the correct relative date
* Fixed template post-processing for Chinese and custom daily-note path formats created through Obsidian Daily Notes, using the note date instead of the file creation time
## 2.0.37
* Fixed recurring tasks losing their current due date in advanced lists, Inbox, Schedule, and overdue grouping; the next recurrence date is now used for display, sorting, and filtering
* Preserved the original recurrence rule instead of writing the computed next due date back to the task, keeping large-calendar display and sync results stable
## 2.0.36
* Added contextual settings entries to the calendar header, task defaults, and remote-calendar event surfaces so related configuration opens directly
* Improved remote task source context for Google, iCloud, ICS, and CalDAV entries before jumping into settings
## 2.0.35
* Fixed remote calendar push gating so disabling the write calendar or related push no longer triggers sync actions or deletes remote events by mistake
* Aligned manual push buttons and calendar task actions with the real writable-calendar state for Calendar Pro and shared calendar views
## 2.0.34
* Rebalanced large calendar time-grid density so the default height feels closer to the pre-fine-grained calendar layout while compact mode stays readable
* Fixed compact one-hour time-grid tasks so at least one title line and the `18:00-19:00` style time range remain visible
## 2.0.33
* Tightened compact time-grid density so dense calendar views can show more hours without wasting vertical space
* Added clearer Core Concepts guide links so new users can understand pressure-free capture and retrieval before getting started
## 2.0.32
* Fixed removed local tasks sometimes leaving matching remote calendar events behind; remote cleanup is now more reliable
* Preserved tag-only task titles when syncing to remote calendars, so tag-only tasks no longer become empty events
## 2.0.31
* Fixed Google / CalDAV sync failures caused by some remote event formats, making remote event write-back more reliable
* Improved duplicate-push protection so local tasks and remote events match more reliably
* Added the large calendar time-grid height setting and maintained the current stable release content
## 2.0.30
* Fixed time-grid event cards so the bottom time range stays visible instead of being covered by the title or checkbox layout
* Improved timed task editing and display for exact minute values, including compact ranges such as `8:25-12:10`
## 2.0.29
* Maintained the current stable Calendar Pro package so user update content stays complete
* Carried forward Google / CalDAV duplicate-push safeguards and time-grid all-day drop fixes in the latest stable package
## 2.0.28
* Fixed Kanban initial loading sometimes missing postponed in-progress secondary tasks; initial loading and later file changes now stay consistent
* Fixed unstable time-grid drag detection for all-day tasks, so moving tasks between all-day and timed slots writes the intended date/time
* Maintained stable release content after version 2.0.27
## 2.0.27
* Fixed Google / CalDAV sync creating duplicate remote events when a task lacks stable matching information; unreliable pushes are now skipped
* Fixed remote duplicate cleanup so refreshed or moved CalDAV events are matched reliably
* Improved timed calendar task display and drag write-back for time ranges and multi-day placement
## 2.0.26
* Added an optional Time Range column to advanced task tables, with display and sorting for task start/end times; it stays hidden by default so existing table layouts are unchanged
* Fixed unstable target date/time placement when dragging tasks from the calendar sidebar into the large calendar or timeline
* Fixed stale local tasks sometimes remaining in the calendar cache after their source file was deleted
* Fixed bulk postponing parent tasks and indented subtasks from the same file in Inbox / Schedule views only moving one or two items
* Improved Schedule and Timeline date labels so Today / Tomorrow still show the exact date and weekday, with more compact localized formatting
## 2.0.25
* Fixed dragging a timed task end to `24:00` writing the due date as the next day and making the task look cross-day or all-day; `21:00 - 24:00` now stays on the same due date
* Fixed same-day `24:00` time blocks such as `21:30 - 24:00` sometimes being placed in the all-day area, and improved the displayed end label so it no longer appears as 12:00 AM
* Unified task display-text cleanup so Kanban, calendar, and sync titles no longer turn `19:00 - 24:00 world` into `- world` or accidentally remove the task body
## 2.0.24
* Fixed the native FullCalendar right-edge resize handle not appearing on multi-day tasks in the large calendar
* Fixed timeline drag moves updating only the due date instead of shifting the start and due dates together
* Fixed date-only range tasks being written back as `00:00 - 24:00` after date drag or resize; time ranges are now written only when the task already had time or is explicitly dropped from the all-day area into a timed slot
* Fixed dragging a task from the all-day area into a timed grid slot not writing the target start/end time
* Fixed single timestamps such as `10:00 hello` being treated as calendar time blocks; dragging them into a timed slot now preserves the timestamp and inserts the new `HH:mm - HH:mm` range after it
## 2.0.22
* Fixed multi-day all-day tasks showing `No start` in the task popover even when the task already had start and due dates
## 2.0.21
* Upgraded the task popover date control to a Start - Due range editor, so `🛫` start dates and `📅` due dates can be edited separately, including specific start/end times
* Fixed due-date-only edits from task popovers or large calendar views clearing existing start dates and time blocks
## 2.0.19
* Fixed recurring tasks not creating the next task when checked from calendar/event-card surfaces outside the editor; Calendar Pro now uses Obsidian Tasks when available and falls back to its own recurring-task generation when the Tasks plugin is not installed
## 2.0.18
* Improved task query stability for calendar-backed task lists, including nested task rows, grouped task rows, and incremental index refreshes
* Unified custom task status styling across calendar task surfaces, reducing mismatched checkbox/status display between schedule, kanban, event cards, and task quick actions
## 2.0.15
* Fixed daily-record tasks with a leading record timestamp plus a later time block, such as `17:41 10:00 - 10:30 ...`, being treated as all-day tasks instead of scheduled time-block tasks
## 2.0.14
* Improved calendar task previews and date editing so task cards preserve richer child-task, date, and status context
* Fixed custom task status, task timestamp, and Markdown task parsing inconsistencies that could appear after calendar refresh or sync
## 2.0.13
* Fixed cross-plugin settings updates sometimes affecting Calendar Pro state when multiple LifeOS plugins are enabled
## 2.0.11
* Fixed the Obsidian third-party plugin list sometimes hiding the settings button by registering the settings tab before vault indexing starts
## 2.0.10
* Fixed calendar dropdowns in Obsidian's detached settings window drifting to the main window or becoming hard to select
* Fixed settings tab highlight not following the active tab
* Fixed duplicate input borders in settings fields
* Fixed possible settings white-screen after upgrade and plugin state display issues
## 2.0.0
* Added device management: view device usage, refresh the device list, and unbind unused devices from plugin settings
* Added a manual update entry, making it easier to get the latest plugin when automatic updates fail
* Added task default start dates for new tasks, including today, tomorrow, day after tomorrow, and next week
* Added configurable task delay days with delay-to-today support for quick and bulk overdue actions
* Added Kanban tag column sorting by task count, alphabetical order, and manual drag ordering
* Improved calendar loading and task refresh performance for large vaults, especially when multiple LifeOS plugins are enabled together
---
url: /news/deep-ask-changelog.md
---
# DeepAsk Changelog
> More details with pictures, please check [LifeOS for Obsidian](https://medium.com/@quanru)
## 2.1.0-beta.13
* Refined the AI conversation header and mobile button layout.
* Fixed shared settings switches and refreshed beta package signatures and integrity metadata.
## 2.1.0-beta.12
* Fixed Excel-triggered spreadsheet Skills so they execute the requested workflow inside Obsidian instead of only showing instructions.
* Fixed vault-path resolution when restoring AI snapshot indexes, improving conversation context recovery.
* Rebuilt the beta package from the latest stable baseline and refreshed its signature and integrity metadata.
## 2.1.0-beta.11
* Optimized update checks by briefly caching each plugin and release-channel result and deduplicating concurrent requests, reducing redundant network traffic, server logs, and resource use.
* Hardened shared Obsidian plugin builds and release artifact serialization so concurrent builds cannot overwrite or invalidate one another.
## 2.1.0-beta.10
* Added a unified DeepAsk settings feedback flow with optional privacy-sanitized diagnostics across light, dark, and narrow sidebar layouts.
* Fixed existing-conversation switches retaining stale content, and expanded visual and functional coverage for context handoff, Chinese localization, and Skills management.
* Tightened local CLI execution rules so dangerous or unsupported commands cannot enter AI workflows while safe local capabilities remain available inside Obsidian.
## 2.1.0-beta.9
* Fixed the unresponsive conversation-history control, repeated context refreshes after switching conversations, and missing tag and folder counts in restored context.
* Tightened message actions into a single row in narrow sidebars and corrected `/` autocomplete, composer alignment, and dark-theme overflow behavior.
* Refined mobile DeepAsk touch targets, bottom-composer layout, and shared tab navigation, with expanded real Obsidian and component-level regression coverage.
## 2.1.0-beta.8
* Flattened the DeepAsk sidebar header, context, message bubbles, tool receipts, and composer with Obsidian semantic colors and fewer shadows, dividers, and overly dark surfaces.
* Fixed text and icon readability for downloads, message actions, secret visibility, model selection, and Skills installation across themes.
* Canonicalized file paths returned by real Agent tools so AI Review, Smart Organize, and Workbench merge alternate references to the same vault file instead of showing duplicate results.
## 2.1.0-beta.7
* Rebuilt the beta package from the source that passed the commit gates. It contains the same features as `2.1.0-beta.6` with refreshed signing and integrity metadata.
## 2.1.0-beta.6
* Closed AI conversation, review, and Home workflows inside Obsidian, removing Aino handoff actions while aligning shared recalibration and host behavior.
* Refined DeepAsk conversation switching, restored context, composer layout, and message actions with fewer dividers, shadows, and high-contrast surfaces.
* Fixed API-key visibility, model-select close, and LifeOS Skills install controls so their text and icons remain readable with semantic host colors in light and dark themes.
## 2.1.0-beta.5
* Rebuilt the shared-AI beta from the latest verified `main` revision after the stable-line merge, with refreshed signing and integrity metadata for the downloadable bundle.
## 2.1.0-beta.4
* Rebuilt the shared-AI beta from the final `main` revision and refreshed integrity metadata so the downloadable bundle matches the verified source; UI and behavior remain aligned with beta.3.
## 2.1.0-beta.3
* Reworked expanded AI context into quiet, borderless sections with compact theme-aware tags and attachment groups aligned with Aino Desktop's hierarchy.
* Improved localized composer placeholders and attachment-button colors for clearer input guidance in light, dark, narrow, and mobile layouts.
* Added stronger theme-adapter and cross-host regression coverage so Obsidian refinements remain isolated from Aino Desktop styling.
## 2.1.0-beta.2
* Flattened DeepAsk's header actions, message bubbles, context area, and composer to reduce excessive surface contrast inside Obsidian.
* Unified message actions, welcome states, and quick-prompt styling for clearer behavior in narrow sidebars and dark themes.
* Isolated Obsidian-specific theme overrides in a dedicated adapter layer, preserving shared Aino Desktop AI behavior without changing Aino's styling baseline.
## 2.1.0-beta.1
* Moved the DeepAsk chat surface onto the shared AI conversation UI used by the Aino Desktop sidebar, aligning conversations, messages, context, quick prompts, and the composer.
* Fixed stale content after switching conversations, lost restored context, and misaligned `/`, `#`, and `@` autocomplete menus.
* Flattened header actions and message-bubble styling while improving spacing, themed backgrounds, and bottom-composer layout in dark themes, narrow sidebars, and mobile Obsidian.
## 2.0.46
* Improved when custom AI-model settings are persisted, reducing redundant writes and UI churn while editing configuration.
## 2.0.45
* Fixed an infinite rerender while restoring and saving conversation context that surfaced as React error `#185` and blanked the AI chat view.
* Stabilized conversation and header-control callbacks while skipping unchanged context saves, preventing the loop when reopening existing chats.
## 2.0.44
* Improved shared plugin integrity verification, reducing repeated reads and activation waits in large or busy vaults.
* Added a recoverable DeepAsk runtime error boundary with a visible retry state so chat failures no longer blank the entire surface.
* Hardened recommendation cleanup, AI chat interactions, and file-lifecycle integration for better Desktop and Mobile stability.
* Synced the latest LifeOS product recommendation and shared release-infrastructure updates.
## 2.0.42
* Fixed repeated integrity reads in large or busy vaults leaving activated settings tabs blank indefinitely.
* Added a visible verification loading state and bounded file-read handling so stalled checks no longer fail silently.
## 2.0.41
* Rebuilt the complete production package and refreshed signed integrity metadata for this release batch.
## 2.0.40
* Fixed version checks being triggered repeatedly after React rerenders, preventing requests from accumulating until Obsidian reports `ERR_INSUFFICIENT_RESOURCES`.
## 2.0.39
* Improved shared LifeOS runtime and domain boundaries for more reliable DeepAsk behavior across hosts.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.38
* Refactored AI chat helper boundaries and shared runtime tooling so DeepAsk remains easier to verify and safer to evolve across Obsidian desktop and mobile builds.
* Hardened chat context and sync-backup integration paths, reducing layout or context drift when larger workspace context is refreshed.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.37
* Fixed long messages, code blocks, and tool output overflowing horizontally inside chat bubbles, making DeepAsk conversations steadier in narrow sidebars and on mobile.
* Hardened AI chat context rendering and bundled Agent guidance updates to reduce layout issues when larger context payloads are synchronized.
## 2.0.36
* Improved the DeepAsk mobile chat composer so attachment and context areas are height-limited and scroll independently, reducing page jumps during focus, loading, and hover states.
* Hardened mobile chat scrolling anchors and composer layout so narrow screens are less likely to overflow or jitter around the bottom action area.
## 2.0.35
* Fixed configured Claude Code or Codex executable paths failing when meaningful whitespace was trimmed from the path
* Fixed rapid changes across multiple DeepAsk settings sometimes saving only the last field; updates within the same debounce window are now merged
* Improved localized activation errors and targeted plugin reloads after updates; reload failures now report failure instead of claiming the update succeeded
* Updated the bundled LifeOS Agent guidance with a Memos template, existing-vault migration, and a more complete first-run workflow
## 2.0.34
* Regenerated and redeployed the complete release package and integrity metadata to prevent update or activation failures caused by mismatches between downloads, version archives, and verification values
## 2.0.33
* Improved the waiting experience when DeepAsk uses local coding agents. The chat now shows clearer progress states and reduces first-launch idle time.
## 2.0.32
* Fixed command prompt windows appearing on Windows when DeepAsk starts local agents or tool services, keeping the workflow inside Obsidian.
## 2.0.31
* Fixed local coding-agent launch failures on Windows when DeepAsk sends large vault context.
## 2.0.30
* Fixed clipped top-right actions when the right sidebar is narrow. The DeepAsk title now hides in compact containers so model, conversation, settings, and help buttons remain accessible.
* Fixed the bottom quick-suggestion row being cut off in narrow sidebars. The suggestion list now supports horizontal scrolling.
## 2.0.29
* Fixed chat-list jitter while DeepAsk is streaming a reply. The message list now follows the bottom steadily during live output and does not force-scroll users back down after they scroll up to read history.
## 2.0.28
* Added a settings entry to the AI chat surface so model, provider, and DeepAsk configuration can be opened directly
* Extended the shared settings button to target related settings sections, making the right configuration easier to find when multiple LifeOS plugins are enabled
## 2.0.27
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.26
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.25
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.24
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.23
* Maintenance release for the shared LifeOS plugin foundation, keeping compatibility with the current Obsidian plugin versions
## 2.0.22
* Fixed agent context so DeepAsk includes the active note, current web page, and open tab summary when sending requests
## 2.0.21
* Fixed periodic daily-note lookup to honor Obsidian Daily Notes folder and format settings, including month subfolders
## 2.0.20
* Fixed cross-plugin settings updates sometimes affecting DeepAsk state when multiple LifeOS plugins are enabled
## 2.0.19
* Improved DeepAsk desktop component loading stability, reducing missing-component issues after updates
* Fixed the chat panel sometimes reporting a false loading failure right after plugin updates
## 2.0.18
* Improved DeepAsk chat panel loading so required components are less likely to be missing after updates
* Fixed desktop components sometimes missing after updates from older versions
## 2.0.17
* Fixed DeepAsk chat panel and local capabilities sometimes failing to load after updates
## 2.0.15
* Fixed Codex CLI replies stopping after the first partial segment in DeepAsk
## 2.0.14
* Updated Ordinary Model Tools settings so built-in capabilities are available by default while external capabilities stay disabled by default
* Split write/update permission from delete permission for ordinary model chat
* Fixed the Ordinary Model Tools settings layout so switches and inputs display cleanly
## 2.0.13
* Fixed DeepAsk failing to load because of dependency version mismatches
## 2.0.12
* Fixed the latest DeepAsk release missing the Ordinary Model Tools settings section in AI Connect
* Added a note that Ordinary Model Tools only apply to DeepAsk ordinary model chat and do not affect local coding-agent modes
## 2.0.11
* Fixed the Obsidian third-party plugin list sometimes hiding the settings button by registering the settings tab before vault indexing starts
## 2.0.10
* Added controlled tool calling for ordinary AI model chat, with permission-aware context reading and tool use
* Added ordinary model tool-call settings, with write and delete capabilities disabled by default to prevent accidental note edits
* Added the AI Connect settings tab for related DeepAsk AI connection, install, and update entries
* Fixed the missing AI Connect settings tab in DeepAsk
* Fixed settings white-screen and loading failures
## 2.0.9
* Fixed AI model dropdowns in Obsidian's detached settings window drifting to the main window or becoming hard to select
* Fixed other settings dropdowns and active tab highlight behavior
* Fixed duplicate input borders in settings fields
* Fixed possible settings white-screen after upgrade and plugin state display issues
## 2.0.0
* Added device management: view device usage, refresh the device list, and unbind unused devices from plugin settings
* Added a manual update entry, making it easier to get the latest plugin when automatic updates fail
* Added Anthropic configuration support while keeping the existing OpenAI-compatible services available
* Added more flexible model service configuration, so the same service can keep separate settings for different usage modes
* Added local coding-agent modes, allowing Obsidian context to be sent directly to local agents
* Added OpenAI and Anthropic identity marks in the chat page, making the active model service clearer
* Added an animated pre-response placeholder, so sending a message immediately shows that a reply is being prepared
* Improved context loading for large vaults, especially when DeepAsk is used alongside other LifeOS plugins
---
url: /news/remosidian-host-changelog.md
---
# Remosidian Host Changelog
> Remosidian official site: [remosidian.pages.dev](https://remosidian.pages.dev)
## 0.1.7-beta.1
* Added a separate beta package with shared plugin build updates and real Obsidian startup validation, without replacing stable downloads.
## 0.1.6
* Synced shared Obsidian plugin runtime and release-infrastructure updates for more reliable distribution.
## 0.1.5
* Maintenance release aligned with this Obsidian plugin stability fix and production release batch.
## 0.1.4
* Maintenance release: rebuilt the production package and refreshed the distribution metadata for this release batch.
## 0.1.3
* Maintenance release aligned with the shared Obsidian plugin runtime fix and production release batch.
## 0.1.2
* Maintenance release: kept the current plugin version aligned with this LifeOS / Calendar Pro release batch
## 0.1.1
* Maintenance release: completed public version information for distribution
## 0.1.0
* Initial release: private desktop host for Remosidian
* Pair your phone via QR code, then browse, edit, and ask AI about your vault remotely
* Local-first design: your vault never leaves this machine
---
url: /news/advanced-list.md
---
# LifeOS Pro for Obsidian introduced Advanced List ✨
Are you troubled by long tasks, bullet notes, and file lists? This time, we bring you the ultimate solution!🔍
👉 New Features
* 1️⃣ Page Turning: Even long lists can be easily browsed!📖
* 2️⃣ Sorting: Sort by date, status at will!📅
* 3️⃣ Search: Text and date search with one click, everything is under control!🔍
Not only that, the task collection and task completion list in the periodic notes also fully support these new features! Want to find a specific task or record? Just a few seconds!⏱️
## Search
## Sorting
## Filtering
Not only that, the task collection and task completion list in the periodic notes also fully support these new features! Want to find a specific task or record? Just a few seconds!⏱️
🌟 Upgrade to LifeOS Pro 2.1.0 now and enjoy more surprises:
* 1️⃣ Big Calendar: Schedule planning is clearer!🗓️
* 2️⃣ Advanced List: Query records are more convenient!📂
* 3️⃣ Home Page View: Core content is clear at a glance!🏠
* 4️⃣ Theme Notes: Easy to build workflows!📝
Experience the new efficiency tool and improve your work and life quality!🙌🚀
---
url: /news/post-dec-2024-lifeos-deepask.md
---
# LifeOS Pro / DeepAsk Updates After December 2024
After the December 2024 update, the Obsidian LifeOS line kept moving in two directions: a steadier core experience, and paid capabilities for tasks, templates, activation, and AI workflows. This summary is assembled from the [LifeOS Pro changelog](/news/lifeos-pro-changelog.md) and the [DeepAsk changelog](/news/deep-ask-changelog.md).
## Free / Core Experience
* **Easier example vaults**: example-vault templates moved to built-in template syntax and no longer depend on Dataview / Templater by default.
* **More reliable periodic notes**: fixed weekly-note week numbers, Chinese weekday display, custom periodic-note paths, `*.README.md` project-index detection, and `LifeOS` code block rendering.
* **More stable daily-record sync**: added Memos 0.28 compatibility so daily-record sync works better with newer Memos versions.
* **Large-vault improvements**: improved startup, search, and context loading, especially when several LifeOS plugins are enabled together.
* **Settings stability**: fixed dropdown positioning, active-tab highlights, duplicate borders, and possible blank screens in Obsidian detached settings windows.
## Paid / LifeOS Pro
* **Device management**: settings can show device usage, refresh the device list, and unbind unused devices.
* **Manual updates**: added a beta / manual update entry for cases where automatic update fails.
* **Task planning improvements**: added default task start dates, task deferral settings, and kanban tag-column sorting by task count, alphabetical order, or manual drag.
* **Custom task states are more complete**: Markdown tasks, custom checkbox states, task timestamps, indented subtasks, and editor checkbox clicks now follow LifeOS status-cycle logic more consistently.
* **Task previews and date editing improved**: task cards in calendar, task lists, and advanced lists preserve richer child-task and date context.
* **Template improvements**: added template-variable guidance, theme snapshots in templates, and better `{{snapshot:Project}}` recognition for project index files.
* **LifeOS Skill updates**: the bundled LifeOS Skill now follows the newer AI Wiki guidance, including the `.AI.md` topic-maintenance flow; the CLI also added `lifeos skill install`.
## Paid / DeepAsk
* **Multi-model configuration**: added Anthropic configuration while keeping OpenAI-compatible services; the same model service can save different connection modes.
* **Local coding-agent modes**: Claude Code CLI and Codex CLI can process the current Obsidian vault context from the local machine.
* **Tool calling for regular models**: regular AI model chat can use Skills and MCP tools, read vault / user skills, and call embedded LifeOS MCP tools.
* **Finer permissions**: write / update permission is separated from delete permission, while external Skills and external MCP tools stay off by default.
* **Central AI connection settings**: the AI Connection tab now gathers DeepAsk HTTP Server, LifeOS Skill install / update, and MCP-related entries.
* **More accurate daily-note lookup**: embedded MCP periodic-note tools now honor Obsidian Daily Notes core folder and format settings.
## Stability and Compatibility
* **More reliable activation state**: fixed cross-plugin authentication-context pollution when several LifeOS plugins are enabled together.
* **More complete DeepAsk packaging**: the chat panel and desktop Koa server were bundled back into the main plugin file to avoid missing-runtime update failures.
* **Codex CLI response fix**: fixed DeepAsk Codex CLI responses stopping after the first partial segment.
* **React / antd compatibility**: fixed settings blank screens, Invalid hook call crashes, and dropdown issues caused by duplicated React / antd copies.
For the full version-by-version notes, see the [LifeOS Pro changelog](/news/lifeos-pro-changelog.md) and the [DeepAsk changelog](/news/deep-ask-changelog.md).
---
url: /news/dec-changelog.md
---
# December 2024 Updates 🎉
## New Features 🎉
* **Calendar Update**: Updated 2025 holidays and lunar calendar display
* **Usememos Adaptation**: Better compatibility with usememos version 0.23.0
## Bug Fixes 🐞
* **Week Calculation Optimization**: Fixed cross-year week number calculation issue
* **Settings Page Optimization**: Added debounce mechanism to avoid frequent validation
* **Usememos Sync Optimization**: Fixed extra spaces issue during synchronization
* **Lunar Calendar Display Fix**: Resolved display error when month is double-digit
---
url: /news/nov-changelog.md
---
# November 2024 Updates 🎉
## New Features 🎉
* **Settings Page Enhancement**: Improved tab switching interaction
* **Font Configuration Optimization**: Fully following Obsidian global settings
* **Usememos Enhancement**: Support cross-domain requests for static resources (e.g., images)
## Bug Fixes 🐞
* **Search Mechanism Optimization**: Strictly search index files according to user configuration
* **Periodic Notes Fix**: Resolved 10-year period switching error
---
url: /news/oct-changelog.md
---
# October 2024 Updates 🎉
## New Features 🎉
* **Enhanced Query View**: Support opening notes in new pane with Ctrl key
* **Localization Support**: Complete Chinese localization for settings page, command palette, and sidebar
* **PARA Notes Optimization**: Support tag wrangle navigation through aliases field
* **Theme Adaptation**: Unified variable definitions for better theme compatibility
## Bug Fixes 🐞
* **Query Optimization**: Smart filtering of template file content
* **Periodic Notes Fix**: Fixed date display in navigation panel
---
url: /news/sep-changelog.md
---
# September 2024 Update 🎉
## New Features 🎉
* **New Domain**: Faster and more stable access at [lifeos.vip](https://lifeos.vip/)
* **PARA Notes Tag Query**: Now case-insensitive, consistent with Obsidian's official behavior
* **Visual Note Creation Form**: Not expanded by default on cold start, can be reopened via the diary icon in the left sidebar
* **Theme Compatibility**: Visual creation form now supports more themes, fully integrating with custom themes
* **File Index List**: Now ignores the current index file by default
## Bug Fixes 🐞
* Fixed prompt disappearance in non-Chinese/non-English environments
* Fixed issue where clicking a selected date didn't navigate to the periodic file
* Improved filtering of periodic note files
* Energy allocation list now filters out non-existent files
---
url: /news/aug-changelog.md
---
# August 2024 Update 🎉
## New Features 🎉
* **Project Time Tracking**: Added 'h' syntax support, both 1h30 and 1hr30 are now valid
* **Cross-Platform Sync**: Unified snapshot list generation order on mobile and desktop to prevent file conflicts
---
url: /news/july-changelog.md
---
# July 2024 Update 🎉
## New Features 🎉
* **Periodic Notes Enhancement**: Visual creation form automatically locates to the corresponding date
* **[Usememos](https://usememos.com/) Integration**: Automatically creates and syncs diary if it doesn't exist
---
url: /news/june-changelog.md
---
# June 2024 Update 🎉
## New Features 🎉
* **[Usememos](https://usememos.com/) Compatibility**: Support for breaking changes in version 0.22.3 and above
* **Index Query Optimization**: All query statements now support ignoring template files
---
url: /news/may-changelog.md
---
# 2024 May Update
New Features 🎉
* 📆 Super useful calendar feature upgrade, now supporting viewing holidays, adjusted days off, and lunar dates!
* 📁 DIY template paths! A brand new feature that supports freely defining your template file paths!
* 🔄 When syncing memos, if the diary for the current day hasn't been created, you now have the option to turn off notifications!
---
url: /news/apr-changelog.md
---
# 2024 April Update
New Features 🎉
* New configuration interface, folder support drop-down selection to avoid mismatch
* PARA index file can be matched as a folder of the same name, which is convenient to work with the [folder notes](https://github.com/LostPaul/obsidian-folder-notes) plugin
* Add indicators to dates which have notes recorded
* Support the modification of the start time of the week
---
url: /news/mar-changelog.md
---
# 2024 March Update
New Features 🎉
* Support for index files to have the same name as their folders, making it easier to work with the folder notes plugin 👌
* Added "FileListByTag" view for indexing all files that match the tag 📑
* Reduced the area occupied by the note creation form, making it more convenient for small screen devices 📱
* Full Chinese localization of the plugin, making it more suitable for Chinese users 🇨🇳
Bug Fixes 🐞
* Fixed the issue where the directory and index form were not automatically filled in after selecting the autocomplete tag when creating PARA notes ❗
* Fixed the issue where the index list prompted for a tag not provided when creating PARA notes for the first time ❌
* Compatible with PARA notes tags that start with # ✔️
---
url: /news/feb-changelog.md
---
# 2024 February Update
New Features 🎉
* 💼 Quick access to cyclical notes, allowing you to jump to or create notes for today, this week, this month, this quarter, and this year with a simple command.
* ✒️ Autocompletion of tags when creating PARA notes, eliminating the need for manual tag copying.
* 📸 Addition of Resource and Archive to the snapshot feature, enabling quick generation of current PARA snapshots in templates.
* 🌍 Added a command for fast navigation to the official LifeOS website.
* 🔍 When a Bullet record contains a reference ID, you can directly jump to the corresponding line.
Bug Fixes 🐞
* 📱 Ensured that unfinished tasks are always prioritized in the mobile task list.
* 🎨 Synchronized the calendar interface style when switching between dark and light themes.
* 🏷️ Corrected the issue of inaccurate tag matching in the task index list.
* 📅 Fixed the issue of incorrect calculation of weekly journal file addresses.
* 📑 Resolved the issue of mutual influence during validation between form fields when creating PARA notes, which resulted in submission failure.
---
url: /news/jan-changelog.md
---
# 2024 January Update
New Features 🎉
* 🎁 More user-friendly PARA note creation experience, immediately notifying invalid input
* 📊 Task statistics module is no longer affected by tasks in template files
* 💫 Easily pull code blocks recorded in usememos
* 📱 Continuously optimizing note creation experience on mobile devices
* 🔗 Compatible with attachments returned by the new version of usememos
Bug Fixes 🐞
* 🚀 Fixed issue where note creation form disappears after disabling periodic note function
* 📅 Fixed calculation error for year when setting weekly start day as Sunday
* 🗂️ Fixed issue where weekly report file names do not match for the first 10 weeks of the year
---
url: /news/deepask-changelog.md
---
# DeepAsk Changelog
> More details with pictures, please check [LifeOS for Obsidian](https://medium.com/@quanru)
## 2.1.0-beta.13
* Refined the AI conversation header and mobile button layout.
* Fixed shared settings switches and refreshed beta package signatures and integrity metadata.
## 2.1.0-beta.12
* Fixed Excel-triggered spreadsheet Skills so they execute the requested workflow inside Obsidian instead of only showing instructions.
* Fixed vault-path resolution when restoring AI snapshot indexes, improving conversation context recovery.
* Rebuilt the beta package from the latest stable baseline and refreshed its signature and integrity metadata.
## 2.1.0-beta.11
* Optimized update checks by briefly caching each plugin and release-channel result and deduplicating concurrent requests, reducing redundant network traffic, server logs, and resource use.
* Hardened shared Obsidian plugin builds and release artifact serialization so concurrent builds cannot overwrite or invalidate one another.
## 2.1.0-beta.10
* Added a unified DeepAsk settings feedback flow with optional privacy-sanitized diagnostics across light, dark, and narrow sidebar layouts.
* Fixed existing-conversation switches retaining stale content, and expanded visual and functional coverage for context handoff, Chinese localization, and Skills management.
* Tightened local CLI execution rules so dangerous or unsupported commands cannot enter AI workflows while safe local capabilities remain available inside Obsidian.
## 2.1.0-beta.9
* Fixed the unresponsive conversation-history control, repeated context refreshes after switching conversations, and missing tag and folder counts in restored context.
* Tightened message actions into a single row in narrow sidebars and corrected `/` autocomplete, composer alignment, and dark-theme overflow behavior.
* Refined mobile DeepAsk touch targets, bottom-composer layout, and shared tab navigation, with expanded real Obsidian and component-level regression coverage.
## 2.1.0-beta.8
* Flattened the DeepAsk sidebar header, context, message bubbles, tool receipts, and composer with Obsidian semantic colors and fewer shadows, dividers, and overly dark surfaces.
* Fixed text and icon readability for downloads, message actions, secret visibility, model selection, and Skills installation across themes.
* Canonicalized file paths returned by real Agent tools so AI Review, Smart Organize, and Workbench merge alternate references to the same vault file instead of showing duplicate results.
## 2.1.0-beta.7
* Rebuilt the beta package from the source that passed the commit gates. It contains the same features as `2.1.0-beta.6` with refreshed signing and integrity metadata.
## 2.1.0-beta.6
* Closed AI conversation, review, and Home workflows inside Obsidian, removing Aino handoff actions while aligning shared recalibration and host behavior.
* Refined DeepAsk conversation switching, restored context, composer layout, and message actions with fewer dividers, shadows, and high-contrast surfaces.
* Fixed API-key visibility, model-select close, and LifeOS Skills install controls so their text and icons remain readable with semantic host colors in light and dark themes.
## 2.1.0-beta.5
* Rebuilt the shared-AI beta from the latest verified `main` revision after the stable-line merge, with refreshed signing and integrity metadata for the downloadable bundle.
## 2.1.0-beta.4
* Rebuilt the shared-AI beta from the final `main` revision and refreshed integrity metadata so the downloadable bundle matches the verified source; UI and behavior remain aligned with beta.3.
## 2.1.0-beta.3
* Reworked expanded AI context into quiet, borderless sections with compact theme-aware tags and attachment groups aligned with Aino Desktop's hierarchy.
* Improved localized composer placeholders and attachment-button colors for clearer input guidance in light, dark, narrow, and mobile layouts.
* Added stronger theme-adapter and cross-host regression coverage so Obsidian refinements remain isolated from Aino Desktop styling.
## 2.1.0-beta.2
* Flattened DeepAsk's header actions, message bubbles, context area, and composer to reduce excessive surface contrast inside Obsidian.
* Unified message actions, welcome states, and quick-prompt styling for clearer behavior in narrow sidebars and dark themes.
* Isolated Obsidian-specific theme overrides in a dedicated adapter layer, preserving shared Aino Desktop AI behavior without changing Aino's styling baseline.
## 2.1.0-beta.1
* Moved the DeepAsk chat surface onto the shared AI conversation UI used by the Aino Desktop sidebar, aligning conversations, messages, context, quick prompts, and the composer.
* Fixed stale content after switching conversations, lost restored context, and misaligned `/`, `#`, and `@` autocomplete menus.
* Flattened header actions and message-bubble styling while improving spacing, themed backgrounds, and bottom-composer layout in dark themes, narrow sidebars, and mobile Obsidian.
## 2.0.46
* Improved when custom AI-model settings are persisted, reducing redundant writes and UI churn while editing configuration.
## 2.0.45
* Fixed an infinite rerender while restoring and saving conversation context that surfaced as React error `#185` and blanked the AI chat view.
* Stabilized conversation and header-control callbacks while skipping unchanged context saves, preventing the loop when reopening existing chats.
## 2.0.44
* Improved shared plugin integrity verification, reducing repeated reads and activation waits in large or busy vaults.
* Added a recoverable DeepAsk runtime error boundary with a visible retry state so chat failures no longer blank the entire surface.
* Hardened recommendation cleanup, AI chat interactions, and file-lifecycle integration for better Desktop and Mobile stability.
* Synced the latest LifeOS product recommendation and shared release-infrastructure updates.
## 2.0.42
* Fixed repeated integrity reads in large or busy vaults leaving activated settings tabs blank indefinitely.
* Added a visible verification loading state and bounded file-read handling so stalled checks no longer fail silently.
## 2.0.41
* Rebuilt the complete production package and refreshed signed integrity metadata for this release batch.
## 2.0.40
* Fixed version checks being triggered repeatedly after React rerenders, preventing requests from accumulating until Obsidian reports `ERR_INSUFFICIENT_RESOURCES`.
## 2.0.39
* Improved shared LifeOS runtime and domain boundaries for more reliable DeepAsk behavior across hosts.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.38
* Refactored AI chat helper boundaries and shared runtime tooling so DeepAsk remains easier to verify and safer to evolve across Obsidian desktop and mobile builds.
* Hardened chat context and sync-backup integration paths, reducing layout or context drift when larger workspace context is refreshed.
* Updated the production package, version index, and integrity metadata so downloads, updates, and activation verification remain consistent.
## 2.0.37
* Fixed long messages, code blocks, and tool output overflowing horizontally inside chat bubbles, making DeepAsk conversations steadier in narrow sidebars and on mobile.
* Hardened AI chat context rendering and bundled Agent guidance updates to reduce layout issues when larger context payloads are synchronized.
## 2.0.36
* Improved the DeepAsk mobile chat composer so attachment and context areas are height-limited and scroll independently, reducing page jumps during focus, loading, and hover states.
* Hardened mobile chat scrolling anchors and composer layout so narrow screens are less likely to overflow or jitter around the bottom action area.
## 2.0.35
* Fixed configured Claude Code or Codex executable paths failing when meaningful whitespace was trimmed from the path
* Fixed rapid changes across multiple DeepAsk settings sometimes saving only the last field; updates within the same debounce window are now merged
* Improved localized activation errors and targeted plugin reloads after updates; reload failures now report failure instead of claiming the update succeeded
* Updated the bundled LifeOS Agent guidance with a Memos template, existing-vault migration, and a more complete first-run workflow
## 2.0.34
* Regenerated and redeployed the complete release package and integrity metadata to prevent update or activation failures caused by mismatches between downloads, version archives, and verification values
## 2.0.33
* Improved the waiting experience when DeepAsk uses local coding agents. The chat now shows clearer progress states and reduces first-launch idle time.
## 2.0.32
* Fixed command prompt windows appearing on Windows when DeepAsk starts local agents or tool services, keeping the workflow inside Obsidian.
## 2.0.31
* Fixed local coding-agent launch failures on Windows when DeepAsk sends large vault context.
## 2.0.30
* Fixed clipped top-right actions when the right sidebar is narrow. The DeepAsk title now hides in compact containers so model, conversation, settings, and help buttons remain accessible.
* Fixed the bottom quick-suggestion row being cut off in narrow sidebars. The suggestion list now supports horizontal scrolling.
## 2.0.29
* Fixed chat-list jitter while DeepAsk is streaming a reply. The message list now follows the bottom steadily during live output and does not force-scroll users back down after they scroll up to read history.
## 2.0.28
* Added a settings entry to the AI chat surface so model, provider, and DeepAsk configuration can be opened directly
* Extended the shared settings button to target related settings sections, making the right configuration easier to find when multiple LifeOS plugins are enabled
## 2.0.27
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.26
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.25
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.24
* Maintenance release for the shared LifeOS plugin foundation, keeping the current stable release content complete
## 2.0.23
* Maintenance release for the shared LifeOS plugin foundation, keeping compatibility with the current Obsidian plugin versions
## 2.0.22
* Fixed agent context so DeepAsk includes the active note, current web page, and open tab summary when sending requests
## 2.0.21
* Fixed periodic daily-note lookup to honor Obsidian Daily Notes folder and format settings, including month subfolders
## 2.0.20
* Fixed cross-plugin settings updates sometimes affecting DeepAsk state when multiple LifeOS plugins are enabled
## 2.0.19
* Improved DeepAsk desktop component loading stability, reducing missing-component issues after updates
* Fixed the chat panel sometimes reporting a false loading failure right after plugin updates
## 2.0.18
* Improved DeepAsk chat panel loading so required components are less likely to be missing after updates
* Fixed desktop components sometimes missing after updates from older versions
## 2.0.17
* Fixed DeepAsk chat panel and local capabilities sometimes failing to load after updates
## 2.0.15
* Fixed Codex CLI replies stopping after the first partial segment in DeepAsk
## 2.0.14
* Updated Ordinary Model Tools settings so built-in capabilities are available by default while external capabilities stay disabled by default
* Split write/update permission from delete permission for ordinary model chat
* Fixed the Ordinary Model Tools settings layout so switches and inputs display cleanly
## 2.0.13
* Fixed DeepAsk failing to load because of dependency version mismatches
## 2.0.12
* Fixed the latest DeepAsk release missing the Ordinary Model Tools settings section in AI Connect
* Added a note that Ordinary Model Tools only apply to DeepAsk ordinary model chat and do not affect local coding-agent modes
## 2.0.11
* Fixed the Obsidian third-party plugin list sometimes hiding the settings button by registering the settings tab before vault indexing starts
## 2.0.10
* Added controlled tool calling for ordinary AI model chat, with permission-aware context reading and tool use
* Added ordinary model tool-call settings, with write and delete capabilities disabled by default to prevent accidental note edits
* Added the AI Connect settings tab for related DeepAsk AI connection, install, and update entries
* Fixed the missing AI Connect settings tab in DeepAsk
* Fixed settings white-screen and loading failures
## 2.0.9
* Fixed AI model dropdowns in Obsidian's detached settings window drifting to the main window or becoming hard to select
* Fixed other settings dropdowns and active tab highlight behavior
* Fixed duplicate input borders in settings fields
* Fixed possible settings white-screen after upgrade and plugin state display issues
## 2.0.0
* Added device management: view device usage, refresh the device list, and unbind unused devices from plugin settings
* Added a manual update entry, making it easier to get the latest plugin when automatic updates fail
* Added Anthropic configuration support while keeping the existing OpenAI-compatible services available
* Added more flexible model service configuration, so the same service can keep separate settings for different usage modes
* Added local coding-agent modes, allowing Obsidian context to be sent directly to local agents
* Added OpenAI and Anthropic identity marks in the chat page, making the active model service clearer
* Added an animated pre-response placeholder, so sending a message immediately shows that a reply is being prepared
* Improved context loading for large vaults, especially when DeepAsk is used alongside other LifeOS plugins
---
url: /faq/index.md
---
import { ProductBoundaryNotice, ProductDecisionGuide } from '../../../../shared-site-theme/ProductComparison';
# FAQ
## Are LifeOS Pro, DeepAsk, and Aino Desktop the same product?
No. LifeOS Pro is the LifeOS workflow plugin for Obsidian; DeepAsk is the separately purchased and activated AI plugin for Obsidian; Aino Desktop is a standalone desktop app. They can work with the same Markdown vault, but installation, settings, purchases, and licenses are separate. See [Obsidian vs Aino](/guide/pro/aino-desktop.md) for the full comparison.
## Does Obsidian Mobile support every AI feature?
No. Regular model API chat can work when the plugin and provider support it, but features that depend on Node.js, CLI tools, local agents, or external processes are desktop-only.
## How many devices are supported?
5 devices, if you need to reset the device, please contact me
## Support offline use?
No, because activation needs to be checked online from time to time
## Can I request the example vault in another language?
Yes. If you need a custom-language version of the example vault, please contact me after purchase and tell me your preferred language. I will send it when it is available.
## What if the paid version is not maintained?
First, I have been using LifeOS since 2022, so it is impossible to not maintain it;
Second, the paid version is profitable, which is one of the motivations for long-term maintenance of LifeOS; The paid version ensures sustainable development and continuous maintenance;
Third, if it is not maintained due to unavoidable circumstances, there is an open-source version of LifeOS that can be used as a replacement, both of which have the same core functions, but the paid version has more convenience and display functions;
## Is it strongly bound to the CODE/PARA process?
No, CODE/PARA is just one of the available practices, in the LifeOS Pro version, the PARA feature is optional, you can choose it according to your needs;
You can completely implement your own workflow templates through the '[Theme Note](/guide/pro/theme-note.md)' feature, such as '[Academic Library](/guide/best-practice/custom-workflow.md#academic-library)', '[Sales Library](/guide/best-practice/custom-workflow.md#sales-library)', '[Media Library](/guide/best-practice/custom-workflow.md#media-library)', etc.
More information please refer to『[Example Vault Selection](/guide/overview/usage.md#example-vault-selection)』
## How to manually update the plugin?
Download the corresponding plugin ZIP from Feishu and extract it. Quit Obsidian, then copy the extracted plugin files into the existing folder under `.obsidian/plugins/` and allow files with the same names to be overwritten. Do not delete the existing plugin folder: keep its `data.json`, which contains your plugin settings.
### LifeOS Pro Plugin
Download: [LifeOS Pro plugin ZIP](https://www.feishu.cn/file/VvEEbYwRuoFlbTxHthncFhyhnne)
Copy the extracted files into `.obsidian/plugins/lifeos-pro/` and overwrite files with the same names while keeping `data.json`.
### Calendar Pro Plugin
Download: [Calendar Pro plugin ZIP](https://www.feishu.cn/file/K2i8b9wdwoEJtBxeMuZcINE2n3c)
Copy the extracted files into `.obsidian/plugins/calendar-pro/` and overwrite files with the same names while keeping `data.json`.
### Deep Ask Plugin
Download: [Deep Ask plugin ZIP](https://www.feishu.cn/file/GvzebfVr9ohUwcxK3lFcShtLnpd)
Copy the extracted files into `.obsidian/plugins/deep-ask/` and overwrite files with the same names while keeping `data.json`.
:::warning
.obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method
1. MacBook: Use the shortcut key Command + Shift + .
2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders
:::
## How to archive projects?
Right-click the project folder and select 'Move to "4. Archive"' to archive it, similarly, right-click on any 'theme folder' can make the folder freely circulate between 'project', 'field', 'resource', and 'archive' directories, they are all themes!
---
url: /contact/index.md
---
# Contact
## User Groups
* [🎮 Discord](https://discord.gg/HZGanKEkuZ)
* [💬 Telegram](https://t.me/+OLTasChvEEthMjBl)
## Podcast
* [Spotify](https://open.spotify.com/show/2uEwTN48SC5wkTx1nPbct1)
## Official Twitter
* [🐦 LifeOS for Obsidian](https://twitter.com/lifeos_md)
## Contact the Author
* [🐦 Twitter](https://x.com/lifeos_md)
* [📺 Youtube](https://www.youtube.com/@LeYangLin)
* [📧 Email](mailto:quanruzhuoxiu@gmail.com)
---
url: /legal/privacy.md
---
# Privacy Policy
*Last updated: 2026-08-31*
LifeOS ("we", "our", or "us") provides Obsidian plugins, a desktop application, a browser extension, and supporting backend services (collectively, the "Service") published at . This Privacy Policy explains what information we collect, how we use it, and the choices you have.
If you have any questions about this policy, please contact us at ****.
## 1. Information We Collect
### 1.1 Information you provide
* **Account / activation information.** When you purchase or activate a paid plugin, we collect your email address and an activation token issued for your account.
* **Support communications.** If you contact us by email or via our community channels, we receive the contents of those communications.
### 1.2 Information collected automatically
* **Basic usage telemetry.** We may log anonymous request metadata (timestamp, plugin version, error messages) to operate and improve the Service. We do not collect the contents of your Obsidian vault.
* **Website analytics.** Microsoft Clarity and, in commercial builds, Google AdSense storage are disabled by default. They are enabled only after you choose **Allow analytics**, and you can continue without analytics.
### 1.3 Information stored locally on your device
LifeOS is a **local-first** product. Your notes, tasks, calendars, and AI conversation history are stored on your own device (in your Obsidian vault or local application data) and are **not** uploaded to our servers unless you explicitly enable a sync feature you control.
## 2. Third-Party Services
We rely on the following third parties only for the specific purposes listed below:
* **Creem** — payment processing for plugin purchases. Creem receives your billing details directly; we never see your full card number.
* **Google OAuth / Google Calendar / Google Drive** — only if you connect your Google account to enable calendar sync or Drive integration. Tokens are stored locally on your device.
* **OpenAI / Anthropic / other AI providers** — only if you configure an AI feature with your own API key. Prompts are sent directly to the provider you configure; we do not proxy or store them.
## 3. How We Use Information
We use the information described above to:
* Deliver, maintain, and secure the Service;
* Validate license / activation tokens;
* Respond to support requests;
* Detect, prevent, and address fraud, abuse, and security incidents;
* Comply with legal obligations.
We do **not** sell your personal information.
## 4. Data Retention
* **Activation records** are retained for as long as your license is active and for a reasonable period afterward to support refunds, fraud prevention, and recordkeeping.
* **Support emails** are retained as long as needed to handle your request.
* **Local data** (notes, tasks, calendars, AI history) lives on your device; you can delete it at any time by removing the plugin or clearing the vault.
## 5. Your Rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal information, or to object to certain processing. To exercise these rights, email us at **** and we will respond within a reasonable timeframe.
## 6. Children's Privacy
The Service is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us so we can delete it.
## 7. Security
We use reasonable administrative and technical measures to protect personal information. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
## 8. International Users
LifeOS is operated from China and may be accessed worldwide. By using the Service, you consent to the transfer and processing of your information in jurisdictions that may have different data protection rules than your own.
## 9. Changes to This Policy
We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the latest revision. Material changes will be announced on this page.
## 10. Contact Us
For privacy questions or requests:
* **Support email:**
* **Website:**
---
url: /legal/terms.md
---
# Terms of Service
*Last updated: 2026-04-29*
These Terms of Service ("Terms") govern your access to and use of LifeOS — including the LifeOS, Calendar Pro, and Deep Ask Obsidian plugins, the Life Context desktop application, the LifeOS browser extension, and the website at (collectively, the "Service") provided by LifeOS ("we", "our", or "us").
By installing, activating, or otherwise using the Service, you agree to these Terms. If you do not agree, do not use the Service.
For any questions, contact ****.
## 1. Eligibility
You must be at least 13 years old (or the minimum age required in your jurisdiction) and able to form a binding contract to use the Service.
## 2. Accounts and Activation
* Some features require a paid license. After purchase, you receive an activation token tied to the email you provided at checkout.
* You are responsible for keeping your activation token confidential. Do not share, resell, or sublicense it.
* We may revoke licenses obtained through fraud, chargeback abuse, or violations of these Terms.
## 3. License Grant
Subject to your compliance with these Terms and payment of any applicable fees, we grant you a limited, non-exclusive, non-transferable, revocable license to install and use the Service for your personal or internal business use. All rights not expressly granted are reserved.
You may **not**:
* copy, modify, reverse engineer, decompile, or create derivative works of the Service, except as permitted by applicable law;
* redistribute, resell, sublicense, or share activation tokens;
* use the Service to violate any law or third-party right;
* attempt to bypass license checks, rate limits, or security mechanisms.
## 4. Payments, Refunds and Renewals
* Plugin purchases are processed by our payment partner **Creem**. By purchasing, you also agree to Creem's terms and privacy policy.
* Prices are listed on the pricing pages of the Service and may change. Changes do not affect orders already placed.
* Refunds are handled on a case-by-case basis. To request a refund, email **** within 14 days of purchase, describing the issue.
* For subscription products, you may cancel at any time; cancellation takes effect at the end of the current billing period.
## 5. Third-Party Services
The Service can integrate with third-party platforms you choose to connect (for example, Google Calendar, Google Drive, OpenAI, Anthropic, CalDAV providers). Your use of those services is governed by their own terms. We are not responsible for the availability, content, or practices of third-party services.
## 6. User Content
You retain all rights to the notes, tasks, calendars, and other content you create or store with the Service ("User Content"). LifeOS is local-first: User Content lives on your device and is not transmitted to us unless you explicitly enable a feature that requires it.
You are solely responsible for backing up your User Content and for your use of any sync, AI, or sharing features.
## 7. Privacy
Your use of the Service is also governed by our [Privacy Policy](/legal/privacy.md), which is incorporated into these Terms by reference.
## 8. Disclaimers
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE, OR THAT ANY DATA WILL NOT BE LOST.
## 9. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL LIFEOS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, DATA, OR GOODWILL, ARISING OUT OF OR RELATED TO YOUR USE OF THE SERVICE. OUR TOTAL LIABILITY FOR ANY CLAIM ARISING OUT OF OR RELATED TO THESE TERMS WILL NOT EXCEED THE AMOUNT YOU PAID US IN THE 12 MONTHS PRECEDING THE EVENT GIVING RISE TO THE LIABILITY, OR USD 50, WHICHEVER IS GREATER.
## 10. Termination
We may suspend or terminate your access to the Service if you violate these Terms or if required by law. Upon termination, the license granted to you ends, and you must stop using the Service. Sections that by their nature should survive termination (including ownership, disclaimers, limitation of liability, and dispute resolution) will survive.
## 11. Changes to the Terms
We may update these Terms from time to time. The "Last updated" date at the top reflects the latest revision. If we make material changes, we will provide reasonable notice (for example, by posting on this page). Continued use of the Service after the changes take effect constitutes acceptance of the updated Terms.
## 12. Contact
* **Support email:**
* **Website:**
---
url: /index.md
---
---
url: /lizhi/authorization.md
---
import { Authorization } from '../../../theme/components/Authorization';