fix: set workspace.baseDir to target directory on instances create/clone#215
Merged
0xmrpeter merged 1 commit intoOpen-ACP:developfrom Apr 7, 2026
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.
Summary
When creating or cloning an instance via
openacp instances create --dir <path>, theworkspace.baseDirin the generated config was hardcoded to~/openacp-workspace. This caused agent sessions to operate in the wrong directory instead of the target folder.Fix: Set
workspace.baseDirtoresolvedDir(the--dirpath) for both clone and new instance flows.Test plan
openacp instances create --dir /tmp/test --no-interactive --json→ config hasworkspace.baseDir: "/tmp/test"