Complete the isolated install process

Open
#2,884 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start by searching the repository for CLAUDE_CONFIG_DIR, LIFEOS_CONFIG_DIR, and LIFEOS_CONFIG_PATH to find the existing setup and configuration entry points. Reproduce with run /lifeos setup, then trace where setup writes files and how Claude is launched. Done means the isolated option keeps writes out of the user directory and Claude's global configuration; the issue does not name a test or implementation files.

Written by the indexing model from the issue text.

Description

bug
Version

LifeOS 8.761.0 / Claude

What is broken

There are a couple of variables (CLAUDE_CONFIG_DIR, LIFEOS_CONFIG_DIR, LIFEOS_CONFIG_PATH) and that when set will almost let LifeOS run in an "isolated" mode. Could that be completed? It would be useful to have an isolated mode to test it, to test improvement to the system, and to allow using Claude for other projects on the same machine.

Where (file:line)

?

Repro on a clean tree
run /lifeos setup
Negative control

Confirm that with the environmental setting in place, nothing is written to the user directory (~) or Claude's global configuration.

Suggested fix

Add this as an option to the /setup prompt. May need to create a launcher or maybe the user launched Claude from the install directory.

Before submitting
  • I searched open and closed issues for this defect.
  • The repro runs against a clean tree of the version above, not against my modified install.
  • I removed personal data from the pasted output — real names, absolute home paths, tokens, my own content.
Dominant language
TypeScript
Stars
19.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.