Repository navigation
Conversation
jay23606
force-pushed
the
fix/1913-octop-home
branch
2 times, most recently
from
October 15, 2026 16:52
d16be56 to
65c2c15
Compare
jay23606
force-pushed
the
fix/1913-octop-home
branch
from
October 15, 2026 17:07
65c2c15 to
7e7e0c7
Compare
This branch has not been deployed
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
1 participant
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 setup created the default
general-assistant, its local backend used the host drive root even whenOCTOP_HOMEwas configured on another drive. Use the configured Octop home for the default expert when present, while preserving an explicit workspace policy root and the existing fallback whenOCTOP_HOMEis unset.Closes #1913
Target branch
develop(feature / fix — default)main(release/*orhotfix/*only)Type of change
Test plan
CHANGELOG.mdmake allpasses locally (GNU make is unavailable in this Windows environment; backend checks were run directly)Regression gate: the new test fails on two clean
developworktrees and passes on two clean fix worktrees. The focused setup/default-agent tests pass (9 passed). Ruff checks and formatting pass; strict mypy reports no issues across 570 source files.The full local Windows suite reported 4,443 passed, 199 skipped, and 12 failed. I reran the affected tests on unchanged
develop; the same 12 failures reproduce there (Windows bash shim behavior, native process cleanup, and/procpath handling).