Repository navigation
Support isolated SkillClaw instances with SKILLCLAW_HOME - #105
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Multiple worktree proxies previously shared PID/lock and default data paths even when selecting different config files. Add
SKILLCLAW_HOMEfor instance-specific config, PID/start lock, default daemon log, records/cache, skills, dashboard DB and adapter backups. Launcher cleanup retains its selected PID path. Config output now reports the actual selected file.Addresses instance isolation in #25; model routing and subscription authentication remain separate. Explicit data paths and
SKILLCLAW_CONFIG_FILEprecedence are preserved. New isolated homes default to no automatic client configuration; external agent profiles and shared storage must be separately selected, as documented in both READMEs.Validation: five regression cases; full suite 215 passed, 1 skipped; Ruff and format checks passed. Started two real loopback-only daemons with separate homes/ports, verified both healthy with different PIDs, stopped A and confirmed B remained healthy, then stopped B. No inference/provider calls.