feat: launch crews from per-account directories (publish local-only cutover) - #23
Closed
ruby-dlee wants to merge 13 commits into
Closed
feat: launch crews from per-account directories (publish local-only cutover)#23ruby-dlee wants to merge 13 commits into
ruby-dlee wants to merge 13 commits into
Conversation
Owner
Author
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.
Intent
Publish the account-directory launch cutover, which was merged into local
mainon 2026-07-23 via the local-only path and never pushed. Origin was believed to be an external repo with no write access; that is stale — origin isruby-dlee/firstmateand pushes work.Why now
These 13 commits are what makes per-account crew launching work today (crews pin
CODEX_HOME/CLAUDE_CONFIG_DIRinstead of sharing the ambient desktop account). Until this lands they exist only on one machine — the same single-copy risk class we just cleaned up elsewhere.Contents
610f55dlaunch crews from account directories9ceada3make bootstrap backend tests hermeticno-mistakes(review)hardening commits from the original gate run295ec04legacy continuation fixture fixf036ae7account launch shell lintValidation
Already driven through the no-mistakes gate on its original branch — the review/test/lint commits above are that run's output. This PR publishes the validated result; it introduces no new changes on top.
Note
Unblocks
fm/chrome-isolation-c3, whose rebase gate correctly refused to bundle these unrelated commits into a browser-isolation PR.