docs: document FLOW_MANAGE_SERVER in the run command - #5
Merged
Conversation
Prefix the root README launch command with FLOW_MANAGE_SERVER=1 so a fresh clone gets the engine-owned setup, where the canvas restart button applies merged agents, skills and MCP changes without leaving the app. Note the opt-in behavior and per-shell prefix syntax. Co-Authored-By: Claude Opus 4.8 <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
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.
Prefix the root README launch command with
FLOW_MANAGE_SERVER=1so a fresh clone gets the engine-owned setup, where the canvas restart button applies merged agents, skills and MCP changes without leaving the app.What changed
FLOW_MANAGE_SERVER=1 bun openflow.ts$env:/ cmdset)Root
README.mdis a fork-owned surface, so this stays within the no-upstream-modification rule.🤖 Generated with Claude Code