Skip to content

fix(install): hand off to /LifeOS setup — /lifeos-setup is not a registered command#1403

Open
rpriven wants to merge 1 commit into
danielmiessler:mainfrom
rpriven:fix/installer-handoff-lifeos-setup
Open

fix(install): hand off to /LifeOS setup — /lifeos-setup is not a registered command#1403
rpriven wants to merge 1 commit into
danielmiessler:mainfrom
rpriven:fix/installer-handoff-lifeos-setup

Conversation

@rpriven

@rpriven rpriven commented Jul 3, 2026

Copy link
Copy Markdown

What happens

The installer's final step execs claude "/lifeos-setup", but the shipped skill registers as LifeOS (SKILL.mdname: LifeOS, argument-hint: [setup|…]). Client-side command resolution rejects /lifeos-setup (and /lifeos) before skill routing ever sees it:

Unknown command: /lifeos-setup

Only /LifeOS setup works. So every fresh install currently ends with an error instead of onboarding, and a new user who doesn't guess the casing + argument form is stranded at the finish line. The fallback printf and the dry-run message send them to the same dead command.

Validated: clean Debian 13 container AND a separate Linux host with only the skill present (Claude Code 2.1.198) — deterministic, client-side. The currently-served ourlifeos.ai/install.sh has the same handoff, so it needs a redeploy after this merges.

The fix

/lifeos-setup/LifeOS setup at all 5 occurrences (exec, dry-run message, fallback printf, two header comments), applied to both the repo installer and the nested skill-payload copy (LifeOS/install/skills/LifeOS/install/install.sh).

Alternative if you'd rather keep the published copy valid: register an explicit lifeos-setup alias command in the skill — the SKILL.md routing table already maps /lifeos-setup internally, but the client rejects unregistered commands before that routing applies. Happy to rework the PR that way instead.

Found during day-one Linux (Debian) runtime validation of v6.

…stered command

The installer's final step (and its dry-run message, fallback printf, and
header comments) invokes /lifeos-setup, but the shipped skill registers as
'LifeOS' (SKILL.md name: LifeOS), so client-side command resolution rejects
it: 'Unknown command: /lifeos-setup'. Every fresh install currently ends
with an error instead of onboarding.

Validated on a clean Debian 13 container and a separate Linux host
(Claude Code 2.1.198) — deterministic, client-side. Applied to both the
repo installer and the nested skill-payload copy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@rpriven

rpriven commented Jul 4, 2026

Copy link
Copy Markdown
Author

Re-verified against v6.0.3 / current main: both install.sh files still call the unregistered /lifeos-setup (install.sh:143), and this PR still applies cleanly — GitHub reports MERGEABLE, no rebase needed after the 6.0.2/6.0.3 packaging churn. The new INSTALL.md flow routes agentic installs around the slash command, but curl … | bash remains the human entry point and still hands off to the dead command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant