Connect LifeOS to AI clients

Use LifeOS Skill in WorkBuddy, Doubao Work, Codex, Cherry Studio, and other clients to query tasks, organize notes, and work with the same local Markdown vault. Clients with a built-in browser can also display Aino Web directly, with calendars, tasks, topic indexes, and file editing. Aino Desktop and Obsidian do not need to stay open.

Copy the setup prompt

Copy this entire prompt into your current AI client. No command or vault-path editing is required. The AI first uses your current project; if no folder is available, it asks you to select your vault. Use an Agent mode with local file and terminal tools.

Install and enable the complete LifeOS Skill bundle in this client, connect my current vault, and show the embedded Aino Web workbench.
1. Resolve the vault's absolute path from the current project or working folder. Pass that same explicit vault= path to every command. Do not guess, scan unrelated folders, or initialize a vault. If the folder is unclear, ask me to select it.
2. Read https://github.com/quanru/lifeos-skill and check this client's local file, terminal, and Skill capabilities, plus Node.js 24+. Reuse an already verified local CLI with web support; otherwise use npx -y @life-os/cli@latest. Check that help includes web. If missing, report the required update; do not replace a local candidate with an older release.
3. With the same CLI, run skill status, review and preserve local customizations, then skill install. Only write .agents/skills inside the vault; do not change, move, or delete notes. Complete import, enablement, and Agent binding through this client's supported method.
4. Load all six skills: lifeos, aino-web, lifeos-today, lifeos-board, lifeos-onboarding, lifeos-content. Preserve references and sibling paths. Run config and profile against the same vault as read-only verification.
5. Follow the installed lifeos/references/web-workbench.md. Start or reuse a service verified to belong to this vault with view=home and open=none. Keep it running in this client's persistent terminal. Do not stop other services or change global permissions or system network settings.
6. Once the service is ready, prefer this client's built-in browser or webpage tools to display the real workbench. In WorkBuddy, present_files can open the HTTP URL actually returned by the service; in Cherry Studio, follow the current cherry-browser Skill. Do not generate substitute HTML or open the system browser by default. If embedding is unavailable, provide a clickable entry and explain where it can open.
Briefly report the vault, skill enablement and verification, and whether the page is visibly open inside this client. Identify specific missing requirements without exposing credentials. Installation or an open request alone is not proof of success.

After setup, say “LifeOS”, “Show this week's tasks”, or “Open the calendar”. When the client supports embedded webpages, the workbench appears beside the conversation. Terminal clients such as Codex / Claude Code use the browser entry for the same workbench. Complete any required first-time permissions, folder selection, or manual skill import through the client.

Download the Skill or connect manually

The public repository ZIP currently contains a single-entry skill inside a repository folder. It is not the complete six-skill bundle, nor a universally importable upload package. Extract it to inspect SKILL.md and its references. Use the prompt above with the CLI to obtain the complete bundle. For manual import, use the six directories installed below and package them as required by your client.

Prepare the vault and runtime

Use an Agent mode with local file and terminal tools. Select your vault as its working directory, or pass vault="/path/to/My Vault" explicitly. Chat-only mode, retrieval, and uploaded copies do not provide access to the original folder.

Install Node.js 24 or later, including npx, in the environment that actually runs commands. A cloud sandbox cannot access your local folder merely because Node.js is installed on your computer; use local execution with access to that folder.

Open a terminal in the vault, inspect the current installation, then install the complete bundle:

npx -y @life-os/cli@latest skill status vault="/path/to/My Vault"
npx -y @life-os/cli@latest skill install vault="/path/to/My Vault"

Replace the example with your vault's absolute path. Review local changes before updating, then check backups and custom rules.

The installer writes these directories under .agents/skills/:

SkillPurpose
aino-webLaunch the current vault's visual workbench
lifeosShared configuration, CLI, and write safety
lifeos-todayToday and periodic reviews
lifeos-boardWorkflow / PARA boards
lifeos-onboardingSetup and migration
lifeos-contentNotes, attachments, AI Wiki, and dashboards

If your client does not discover project skills, import all six directories. Preserve each SKILL.md, references/, and assets/; copying the instructions alone is insufficient.

For ZIP-only importers, archive the contents of each skill directory separately, with SKILL.md at the archive root. Do not upload the entire GitHub repository archive as one skill. Ask the Agent to verify all six skills and cross-skill references after import. Resolve references first if the importer rearranges their directories.

WorkBuddy

Start with the setup prompt above. Use these manual steps if automatic import or enablement is unavailable.

  1. Open Skills → Add Skill → Upload Skill and import the local packages.
  2. Install and enable all six skills. The documented conversational installation flow is for marketplace skills; use upload for custom packages.
  3. Select your vault for the task, grant the required file and command permissions, and run the read-only check below.

See the official WorkBuddy skill guide. This guide does not claim a LifeOS marketplace listing.

Doubao Work

Start with the setup prompt above. Use these manual steps if automatic import or enablement is unavailable.

  1. Use the Doubao Work desktop client and open its Skills / Connectors / Partners section (also called Plugins / Skills / Partners in some documentation).
  2. Use local skill import to install the complete bundle. If the entry is absent, check your version and organization restrictions.
  3. Select the local vault and an execution environment that can access it. Check that npx runs before performing the read-only check.

These steps concern local tasks in Doubao Work. Ordinary Doubao chat does not imply equivalent permissions. See Feishu's official feature guide and the Doubao skill integration guide. Private import is separate from marketplace review and listing.

Cherry Studio

Start with the setup prompt above. Use these manual steps if automatic import or enablement is unavailable.

  1. Open Settings → Skills → Add Skill → Local import. Import ZIP files or folders containing SKILL.md for all six skills.
  2. Enable them globally, then bind them under Work → Agent menu → Edit → Skills. Bindings apply from the next message.
  3. Select the vault working directory, enable file and Bash tools, and keep Ask Before Acting enabled. Use a tool-capable model and run the read-only check.

A chat assistant differs from a Work Agent. Global enablement alone does not bind skills to an Agent. See Skills and tools and permissions.

Qwen Work

Start with the setup prompt above. Use these manual steps if automatic import or enablement is unavailable.

  1. Open Extensions → Skills → Add → Upload Skill, upload each of the six packages, and check that they are enabled.
  2. Explicitly request the LifeOS Skill in chat, or type / to select an installed skill.
  3. Select the vault for a local task. Verify file access and Node.js in the execution environment, then run the read-only check.

See the Qwen Work skill guide. Organization, cloud, and local task permissions can differ; check actual tools and results.

Codex / Claude Code

Send the setup prompt in a local project with the vault already open. Follow the client's supported Skill discovery/import rules and preserve sibling references. Verify config and profile against the same vault. Terminal clients use the browser workbench; do not assume an embedded webpage is available.

Verify with a read-only task

Send this prompt after replacing the vault path:

Use the complete LifeOS Skill Bundle for /path/to/My Vault.
Check that all six skills and their reference files are readable, then run:
npx -y @life-os/cli config vault="/path/to/My Vault" --json
npx -y @life-os/cli profile vault="/path/to/My Vault" --json
Report only the vault path, structure, and available capabilities. Do not reveal
credentials or create or modify files. If file access, a terminal, or Node.js
is missing, report the missing requirement instead of claiming success.

After confirming the correct folder, ask for today's tasks without changing files. To test writing, explicitly request a test entry and ask the Agent to read back the original file. Migration, moves, and broad overwrites still require a preview and confirmation.

Update client copies separately

skill status checks the vault bundle, not the copies imported into your client. Reimport or update those copies after upgrading, then verify Agent bindings and reference files again.

Use the visual workbench inside your client

The workbench reuses Aino Desktop's views, editor, and sidebars. A local LifeOS CLI service reads the current vault. A built-in browser is enough; MCP Apps setup is not required. Both sidebars start collapsed. Expand the knowledge library for project/topic indexes, or use the calendar and random walk.

Aino Web calendar inside WorkBuddy's built-in browser

This real WorkBuddy capture shows the example vault's knowledge projects on the left and the monthly calendar with tasks on the right. The workbench connects to local Markdown files, rather than an uploaded copy of your notes.

EnvironmentWorkbench entry
WorkBuddyOpen the real HTTP page through the currently available present_files tool; built-in Browser display has been verified
Doubao Work, Cherry Studio, and other desktop AgentsUse the webpage tools or built-in browser actually available in the current session; capabilities and permissions depend on the version
Codex / Claude Code terminalUse the same workbench in a browser
Cloud-only chatCannot directly start or access services on your computer; local execution access is required

The setup prompt checks CLI web support, vault identity, and actual page state. It reports missing capabilities, does not treat an open request as visible-page evidence, and does not silently switch vaults. The workbench follows LifeOS CLI authorization; installing Skills does not grant Pro access.

Ask the AI for a particular view:

  • “Open this week's calendar in week view.”
  • “Show the task board grouped by priority.”
  • “Expand the knowledge projects and open the presentation's topic index.”
  • “Open random walk to revisit past notes.”