fix: update post-init message to recommend copilot --agent squad#1045
Merged
bradygaster merged 1 commit intobradygaster:devfrom Apr 30, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the post-squad init guidance to reflect the deprecation of using the standalone squad shell entrypoint, and instead recommends starting Squad via copilot --agent squad.
Changes:
- Updated the final init console message to recommend
copilot --agent squad. - Updated the human journey test to assert the new recommended command is shown.
- Updated docs example output and added a changeset for the CLI patch release.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
test/human-journeys.test.ts |
Updates assertion to require the new copilot --agent squad guidance. |
packages/squad-cli/src/cli/core/init.ts |
Changes the post-init “what to do next” message to point to Copilot CLI. |
docs/src/content/docs/scenarios/multiple-squads.md |
Updates example init output to match the new recommendation. |
.changeset/fix-post-init-message.md |
Adds a patch changeset documenting the user-facing message change. |
Comment on lines
296
to
297
| console.log(`${GREEN}${BOLD}Your team is ready.${RESET} Run ${CYAN}${BOLD}copilot --agent squad${RESET} to start.`); | ||
| console.log(); |
There was a problem hiding this comment.
This updates the final init guidance, but there is still an earlier init message that tells users to "start squad" when options.prompt is set (.init-prompt stored — team will be cast when you start squad). That becomes inconsistent with the new recommended entrypoint; consider updating that message to reference copilot --agent squad as well so users don’t get mixed instructions.
gaburn
force-pushed
the
gaburn/1034-fix-post-init-message
branch
from
1bbc05a to
a2c05a8
Compare
Closes bradygaster#1034 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gaburn
force-pushed
the
gaburn/1034-fix-post-init-message
branch
from
a2c05a8 to
787b529
Compare
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.
Fixes #1034
Fixes #1007
Both issues report the same bug: after squad init, the CLI prints "Run squad to start" but the standalone squad CLI is deprecated. Updated to recommend copilot --agent squad instead.
Changes
n- Updated test assertions in est/human-journeys.test.tsn- Updated docs example output in docs/src/content/docs/scenarios/multiple-squads.md`n- Added changeset