LifeOS

https://docs.ourlifeos.ai
Admin
LifeOS is an intent engineering platform and AI harness designed to move users from their current...
Tokens:443,575
Snippets:2,821
Trust Score:6.4
Update:1 week ago
Show doc for...
Tokens:
Raw
### Manual kitty install steps

Source: https://docs.ourlifeos.ai/Terminal__Helm

Manual install steps: install kitty and a Nerd Font, copy the config set into ~/.config/kitty (overwrites existing), then launch kitty. Does not create the Helm.app wrapper or helm command. Helper scripts reference ~/.config/kitty by absolute path, so install there.

```bash
# 1. Kitty + a Nerd Font.  macOS:
brew install --cask kitty font-hack-nerd-font
#    Linux: install kitty from your package manager or https://sw.kovidgoyal.net/kitty/
#    and install any Nerd Font (https://www.nerdfonts.com) for the tab-bar icons.

# 2. Copy the config set into place (this overwrites — back up ~/.config/kitty first)
mkdir -p ~/.config/kitty
cp -R ~/.claude/LIFEOS/DOCUMENTATION/Terminal/kitty/ ~/.config/kitty/

# 3. Launch kitty (or reload with shift+cmd+r inside it)
```

--------------------------------

### Install UV package manager

Source: https://docs.ourlifeos.ai/Tools__Tools

Installs the UV package manager, a prerequisite for running the script.

```bash
curl -LsSf https://astral.sh/uv/install.sh | sh
```

--------------------------------

### Recovery and setup commands for LifeOS work tracking

Source: https://docs.ourlifeos.ai/Work__WorkSystem

Commands for recovery and setup: re-authenticate GitHub CLI, seed labels, restart Pulse, and install the work sweep launchd job.

```bash
gh auth login
```

```bash
bun BootstrapLabels.ts
```

```bash
bash ~/.claude/LIFEOS/PULSE/manage.sh restart
```

```bash
bun ~/.claude/LIFEOS/TOOLS/InstallWorkSweep.ts
```

```bash
bun ~/.claude/LIFEOS/TOOLS/InstallWorkSweep.ts
```

```bash
bun ~/.claude/LIFEOS/TOOLS/InstallWorkSweep.ts
```

--------------------------------

### Example: Well-Configured Tool (bun Generate.ts)

Source: https://docs.ourlifeos.ai/Skills__SkillSystem

Shows minimal and full invocations of a CLI tool using bun. The full configuration demonstrates resource selection, output configuration, post-processing flags, and output path. Comments in the code explain each flag category.

```bash
# Minimal invocation (sensible defaults)
bun Generate.ts --prompt "..." --output /tmp/image.png

# Full configuration
bun Generate.ts \
  --model nano-banana-pro \    # Resource selection
  --prompt "..." \
  --size 2K \                  # Output configuration
  --aspect-ratio 16:9 \
  --thumbnail \                # Post-processing
  --remove-bg \
  --output /tmp/header.png
```

--------------------------------

### GET /api/security/attack-surface

Source: https://docs.ourlifeos.ai/Observability__ObservabilitySystem

Retrieves deployed-estate scan snapshot. Returns 404 when no scanner is configured on the install.

```APIDOC
## GET /api/security/attack-surface

### Description
Deployed-estate scan snapshot (404 when no scanner is configured on the install).

### Method
GET

### Endpoint
/api/security/attack-surface

### Response
#### Success Response (200)
- Attack surface snapshot

#### Response Example
{
  "snapshot": {}
}

#### Error Response (404)
- No scanner configured
```

--------------------------------

### Install Conduit via launchd

Source: https://docs.ourlifeos.ai/Conduit__ConduitSystem

Commands to install, check status, and uninstall the Conduit launchd agent. The install command polls every 120 seconds.

```bash
bun LIFEOS/PULSE/Conduit/InstallConduit.ts             # install + load (polls every 120s)
bun LIFEOS/PULSE/Conduit/InstallConduit.ts --status    # launchd state
bun LIFEOS/PULSE/Conduit/InstallConduit.ts --uninstall # unload + remove
```

--------------------------------

### Run Helm install script

Source: https://docs.ourlifeos.ai/Terminal__Helm

Preferred one-command install. Installs kitty and a Nerd Font if missing, backs up an existing ~/.config/kitty directory with a timestamp, links Helm's config, builds a Helm.app wrapper, and adds helm to PATH. On Linux, expects kitty to be pre-installed.

```bash
bash ~/.claude/LIFEOS/DOCUMENTATION/Terminal/install.sh
```

--------------------------------

### Example 2: Publish

Source: https://docs.ourlifeos.ai/Skills__SkillSystem

Example workflow for publishing blog content, showing the user request and the steps taken.

```markdown
User: "Publish the AI agents post"
→ Invokes Publish workflow
→ Runs build validation
→ Deploys to Cloudflare Pages
```

--------------------------------

### Example diary entry

Source: https://docs.ourlifeos.ai/Pulse__DaSubsystem

Example JSON object for a diary entry.

```json
{
  "date": "2026-04-03",
  "interaction_count": 8,
  "topics": ["LifeOS architecture", "newsletter draft", "feed system debugging"],
  "mood": "positive",
  "avg_rating": 8.2,
  "notable_moments": [
    "Designed the DA subsystem together - the principal was excited about heartbeat",
    "Fixed a tricky feed worker bug that had been open for 3 days"
  ],
  "learning": "The principal prefers architecture diagrams in ASCII over Mermaid"
}
```

--------------------------------

### Example 1: Write new content

Source: https://docs.ourlifeos.ai/Skills__SkillSystem

Example workflow for writing new blog content, showing the user request and the steps taken.

```markdown
User: "Write a post about AI agents for the blog"
→ Invokes Create workflow
→ Drafts content in scratchpad/
→ Opens dev server preview at localhost:5173
```

--------------------------------

### Install and Configure Hermes

Source: https://docs.ourlifeos.ai/docs/Hermes__HermesSidecar

Commands to install Hermes, authenticate, and mount the LifeOS environment.

```bash
# 1. Install Hermes (pinned, no Playwright — LifeOS uses Interceptor)
curl -fsSL https://hermes-agent.nousresearch.com/install.sh -o install.sh
# review it, then:
bash install.sh --non-interactive --skip-setup --skip-browser --commit <reviewed-sha>

# 2. Authenticate (its OWN session — never import a sibling agent's tokens)
hermes auth add openai-codex --type oauth --no-browser

# 3. Mount LifeOS
bun LIFEOS/HERMES/Mount.ts

# 4. Install the launcher (below) and start from it, never from bare `hermes`
```

--------------------------------

### Output Formats Example

Source: https://docs.ourlifeos.ai/Tools__CliFirstArchitecture

Demonstrates human-readable default output, JSON for scripting, and specific fields for parsing.

```bash
# Human-readable by default
evals list use-cases

# JSON for scripting
evals list use-cases --json

# Specific fields for parsing
evals query runs --fields id,score,model
```

--------------------------------

### Configuration Flags Example

Source: https://docs.ourlifeos.ai/Tools__CliFirstArchitecture

Shows various configuration flags for execution mode, output control, resource selection, and post-processing.

```bash
# Execution mode flags
tool run --fast              # Quick mode (less thorough, faster)
tool run --thorough          # Comprehensive mode (slower, more complete)
tool run --dry-run           # Show what would happen without executing

# Output control flags
tool run --format json       # Machine-readable output
tool run --format markdown   # Human-readable output
tool run --quiet             # Minimal output
tool run --verbose           # Detailed logging

# Resource selection flags
tool run --model haiku       # Use fast/cheap model
tool run --model opus        # Use powerful/expensive model

# Post-processing flags
tool generate --thumbnail    # Generate additional thumbnail version
tool generate --remove-bg    # Remove background after generation
tool process --no-cache      # Bypass cache, force fresh execution
```

--------------------------------

### Opinions YAML example

Source: https://docs.ourlifeos.ai/Pulse__DaSubsystem

Example YAML file for DA opinions with confidence-weighted beliefs.

```yaml
# DA Opinions -- evolve over time
# Confidence: 0.0 (wild guess) to 1.0 (proven repeatedly)
# Source: observation | inference | stated (principal told me)

opinions:
  - topic: "Architecture documentation format"
    belief: "The principal prefers ASCII diagrams over Mermaid"
    confidence: 0.85
    source: observation
    evidence_count: 7
    first_observed: "2026-01-20"
    last_confirmed: "2026-04-03"

  - topic: "Response length preference"
    belief: "Short for simple tasks, deep when warranted"
    confidence: 0.92
    source: stated
    evidence_count: 12
    first_observed: "2025-12-01"
    last_confirmed: "2026-04-01"

  - topic: "Late night productivity"
    belief: "The principal does their best deep work after 10 PM"
    confidence: 0.70
    source: observation
    evidence_count: 15
    first_observed: "2026-01-05"
    last_confirmed: "2026-03-28"
```

--------------------------------

### Well-formed ISA example for adding --json flag

Source: https://docs.ourlifeos.ai/ISA__ISAFormat

A complete ISA file example that satisfies the format contract for a small CLI tool. It includes frontmatter, goal, claims, and test strategy. The example shows minimal frontmatter, sequential claim numbering, and empty sections omitted.

```markdown
---
task: "add --json output flag to the CLI"
slug: 20260723-140000_cli-json-flag
phase: complete
progress: 3/3
started: 2026-07-23T14:00:00Z
updated: 2026-07-23T14:40:00Z
---

## Goal
The CLI accepts a `--json` flag that prints one valid JSON object carrying the
same data it prints as text, and the default text output is unchanged.

## Claims
- [x] C1: `--json` prints output that parses as a single JSON object.
- [x] C2: The JSON carries the same fields the text output shows.
- [x] C3: Anti: running without `--json` produces byte-identical text to before.

## Test Strategy
| claim | type     | check                                        | threshold | tool | anchors_to |
| C1    | bash     | `cli --json \| jq .` exits 0                 | exit 0    | bash | literal |
| C2    | bun-test | fields(json) == fields(text)                 | equal     | bun test test/cli.test.ts -t "json parity" | literal |
| C3    | bash     | `cli` output diff vs saved baseline is empty | empty     | bash | derived: text-parity |
```

--------------------------------

### Install Pulse Menu Bar App

Source: https://docs.ourlifeos.ai/Pulse__PulseSystem

Builds and deploys the menu bar app to ~/Applications and installs the launchd plist. Run from the MenuBar directory.

```bash
cd ~/.claude/LIFEOS/PULSE/MenuBar
bash install.sh    # Builds, deploys to ~/Applications, installs plist
```
Tokens:
Raw