Support non-Docker local installations - #108
Draft
thomwolf wants to merge 1 commit into
Draft
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.
Summary
/app/scriptsfseventsscriptWhy
The Docker image installs the agent CLIs and places application scripts under
/app, but those build steps and paths do not exist when Agent Manager is launched directly with Node or systemd. As a result, a local backend can report CLIs such as OpenCode as unavailable and install lifecycle hooks that point to files outside the checkout.This keeps the Docker behavior unchanged while giving local deployments an explicit provisioning path and portable helper locations.
Validation
npm ci --strict-allow-scriptsnode test/local-install.test.mjsnode test/opencode-resume.test.mjs(37 checks)sh -n scripts/install-local-clis.shgit diff --checkThe branch was prepared in an isolated worktree and the complete commit was scanned for credentials, tokens, network addresses, Tailscale data, usernames, and absolute host paths before pushing.