Repository navigation
feat(firstmate): allow Pi as the primary supervisor - #117
Merged
Merged
Conversation
lanej
marked this pull request as ready for review
November 1, 2026 16:22
This was referenced Nov 2, 2026
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.
Select Pi for new Firstmate captains on either tmux or Zellij with
FM_PRIMARY_HARNESS=pi firstmate start, or save a persistent preference. This allows a Pi supervisor trial while retaining Codex as the default primary and configured crew harness. Both backends carry the selection, executable lookup path, and Firstmate checkout into the new captain; reattaching preserves the running process. Installation preserves existing primary and backend preferences.Pi requires version 1.4.0 or newer, an updated Firstmate checkout with its tracked primary extensions, and approval of Pi’s project trust prompt. #114 supplies the optional
BOOTSTRAP_PI=1installation and shared resources; an already installed Pi works independently. Launcher checks use fixture agents, so live Pi extension loading and autonomous crew supervision remain unverified.