Replace --parallel-launch flag with --sequential-launch flag#482
Merged
Conversation
- Renamed flag from --parallel-launch to --sequential-launch - Inverted logic: parallel launch is now the default behavior - Updated all references in code (cmd, config, server, tests) - Updated test names and assertions to reflect new flag - Flag description clarifies parallel is default Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update launch flag to sequential default
Replace --parallel-launch flag with --sequential-launch flag
Jan 26, 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.
The
--parallel-launchflag was enabled by default, making the flag name confusing since users had to explicitly set it to opt into the default behavior. Flags should represent opt-in to non-default behavior.Changes
--parallel-launch→--sequential-launch(default:false)ParallelLaunch→SequentialLaunchin TOML/JSON configsparallelLaunch→sequentialLaunchthroughout codebaseBehavior
Before:
After:
Default behavior unchanged - servers launch in parallel. Only the flag naming and logic direction changed.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
nonexistent.local/tmp/go-build2056086634/b269/launcher.test /tmp/go-build2056086634/b269/launcher.test -test.testlogfile=/tmp/go-build2056086634/b269/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo zuLZZ0Z6i /snap/bin/git credential.helpe/opt/hostedtoolcache/go/1.25.6/x64/pkg/tool/linux_amd64/vet(dns block)this-host-does-not-exist-12345.com/tmp/go-build2056086634/b278/mcp.test /tmp/go-build2056086634/b278/mcp.test -test.testlogfile=/tmp/go-build2056086634/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo OUOwgIYji .12/x64/as credential.usernbash(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.