Skip to content

v7.1.1: core package.json missing runtime deps (smol-toml et al) — Pulse crashes on boot #1699

Description

@gangwaydigital

Version: 7.1.1 (macOS 27.0 arm64, bun 1.3.14)

Summary

On a fresh runtime deploy (DeployCore.ts --apply), the core install/package.json placed at <configRoot>/package.json declares only yaml, but the runtime imports packages that never get installed. Pulse crashes on boot (launchd exit 1) and several TOOLS fail to import.

Evidence

  • Placed ~/.claude/package.json after DeployCore --apply: "dependencies": { "yaml": "^2.8.2" } — nothing else.
  • Pulse boot fails: error: Cannot find package 'smol-toml' from '.../LIFEOS/PULSE/pulse-unified.ts'.
  • smol-toml is imported by 9 runtime files, including TOOLS/PaiConfig.ts (loadPaiConfig()), which hooks and many TOOLS call — so this isn't Pulse-only.
  • The full runtime set is already declared in install/LIFEOS/PULSE/package.json:
    @anthropic-ai/claude-agent-sdk ^0.1.0, grammy ^1.34.0, jose ^5.0.0, minisearch ^7.0.0, smol-toml ^1.3.0.
  • But DeployCore runs bun install against the top-level install/package.json, which omits all five.

Impact

Any install that runs DeployCore without a separate bun install inside PULSE/ gets a Pulse service that exits 1 on load — :31337, cron, and voice never start. Hit this on a second-host (worker) macOS install from the v7.1.1 payload.

Repro

  1. DeployCore.ts --apply onto a clean <configRoot>.
  2. Start the Pulse launchd service (Services.ts install --only pulse).
  3. Service exits 1: Cannot find package 'smol-toml'.

Proposed fix

Merge the runtime deps from install/LIFEOS/PULSE/package.json into the core install/package.json (or have DeployCore also bun install in PULSE/). At minimum smol-toml is required for Pulse + config loading.

Workaround

cd ~/.claude && bun add smol-toml grammy jose minisearch @anthropic-ai/claude-agent-sdk

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions