Repository navigation
Read the repositories folder as the MainSequence CLI does (0.3.16) - #28
Merged
Merged
Conversation
A bare folder name such as `mainsequence-dev` is a folder in the home directory for the `mainsequence` CLI (`normalize_mainsequence_path`). devtools read it three ways: setup resolved it against the working directory, which for the Claude worker is the Code session's folder, so a session in ~/whiteboxblackbox cloned into ~/whiteboxblackbox/mainsequence-dev/<org>/projects/; local listings, Projects setup and saved settings rejected it as not absolute. `repositoriesFolder(value, home?)` follows the CLI's rule (`~` is home, a bare name is a folder in it, any other path is an ordinary one) and every entry point uses it: setup, `local-repositories` and the other project operations, organization project setup, workspace settings (saved absolute, as the CLI saves `mainsequence_path`) and the preferences read. Checkouts stay in `<base>/<organization>/projects/`, the folder the CLI uses from SDK 9.0.33. Tests: the resolver's cases, a listing and a setup clone with a bare name landing under home rather than the working directory, and settings saving a bare name under home. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
A Claude Desktop plugin with its repositories folder set to
mainsequence-devcloned StoryForgeBackend into~/whiteboxblackbox/mainsequence-dev/main-sequence-workbench/projects/. The Code session was open in~/whiteboxblackbox, and setup resolved the bare name against the worker's working directory. ThemainsequenceCLI reads a bare name as a folder in the home directory (normalize_mainsequence_path). The other devtools entry points disagreed with both: local listings, Projects setup and saved settings rejected the name as not absolute. With that setting the plugin couldn't list local checkouts or set up a Project.What changes
repositoriesFolder(value, home?)(exported) follows the CLI's rule:~is the home folder.local-repositoriesand the other project operationsmainsequence_pathis saved absolute, as the CLI saves it)<base>/<organization>/projects/, the same folder the CLI uses from SDK 9.0.33.Verification
npm run release:checkpasses with 187 tests, plus the docs check and the package checks. New tests:🤖 Generated with Claude Code