Skip to content

feat(instances): import local standalone nullclaw homes#73

Merged
DonPrus merged 10 commits into
nullclaw:mainfrom
vernonstinebaker:feat/local-existing-nullclaw
May 29, 2026
Merged

feat(instances): import local standalone nullclaw homes#73
DonPrus merged 10 commits into
nullclaw:mainfrom
vernonstinebaker:feat/local-existing-nullclaw

Conversation

@vernonstinebaker
Copy link
Copy Markdown
Contributor

Summary

  • add support for importing local same-machine NullClaw standalone homes from either the default ~/.nullclaw path or a custom path
  • add standalone detection and imported-runtime handling so attached custom-path installs report correctly in NullHub
  • add the install-page UI flow for attaching an existing NullClaw with path and optional name

Testing

  • zig build test --summary all
  • zig build
  • npm run build

Notes

  • scope is limited to local same-machine NullClaw imports
  • imported external instances are expected to follow the normal log convention: logs/stdout.log 2>&1
  • no automated UI test harness was added in this change

DonPrus added 6 commits May 28, 2026 22:19
Resolve conflicts after main moved to NullBoiler/NullWatch routes and keep standalone import coverage current.

Review fixes: document standalone detection route, avoid duplicate install-page loading, use symlink-based imported runtime detection, escape import-name errors, and keep standalone runtime test on a dynamic port.
@DonPrus DonPrus merged commit 6d3ed0d into nullclaw:main May 29, 2026
4 checks passed
@vernonstinebaker vernonstinebaker deleted the feat/local-existing-nullclaw branch May 29, 2026 04:12
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.

2 participants