Skip to content

bug: init --global using npx for personal squad doesn't work #576

New issue
New issue
Closed
#580
Closed
bug: init --global using npx for personal squad doesn't work#576
#580
Labels
bugSomething isn't workinggo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a member

Description

@Fl4t
Fl4t
opened on Mar 23, 2026

Hello,

Unfortunately I can't use the regular npm install -g @bradygaster/squad-cli (require high privileges) so I tried npx @bradygaster/squad-cli init --global to setup a personal squad, however initializing a repository doesn't take into account what has been created under ~/.config/squad/

Activity

  1. stevenkuhn commented on Mar 23, 2026

    @stevenkuhn
    stevenkuhn
    on Mar 23, 2026

    I'm not using npx, but using npm install -g @bradygaster/squad-cli and I'm running into the same issue.

    I'm starting from scratch and reading through https://bradygaster.github.io/squad/docs/guide/personal-squad/.

    I ran squad init --global, went to my project directory (~/code/stevenkuhn/project on Linux and d:\code\stevenkuhn\project on Windows), and ran squad init.

    When I ran my first session on Linux on v0.8.25, created my cast, and had them explore my codebase, it was all contained in my project -- nothing was changed in my personal squad folder. I was expecting the squad identity and non-project related items to be stored in the personal squad folder.

    I reset everything and tried running the same process with v0.9.1 on my Windows machine. I haven't created the cast yet, but I'm not seeing any indication that it would be any different. When I ran squad init in my project folder, it just reports:

    Let's build your team.

✓ .squad\config.json
✓ .squad\agents\scribe\charter.md
✓ .squad\agents\scribe\history.md
✓ .squad\agents\ralph\charter.md
✓ .squad\agents\ralph\history.md
✓ .squad\identity\now.md
✓ .squad\identity\wisdom.md
✓ .squad\ceremonies.md
✓ .squad\decisions.md
✓ .squad\team.md
✓ .squad\routing.md
✓ .copilot/skills
✓ .gitattributes
✓ .gitignore
✓ .github\agents\squad.agent.md
✓ .squad\templates
✓ .github\workflows\squad-heartbeat.yml
✓ .github\workflows\squad-issue-assign.yml
✓ .github\workflows\squad-triage.yml
✓ .github\workflows\sync-squad-labels.yml
✓ .copilot\mcp-config.json
✓ .gitignore
✓ .squad\.first-run

◆ SQUAD

  📁  Team workspace
  📋  Skills & ceremonies
  🔧  Workflows & CI
  🧠  Identity & wisdom
  🤖  Copilot agent prompt

Your team is ready. Run squad to start.

    No where in that does it look like what the documentation page says:

    .squad/config.json → teamRoot: {personal squad directory}
Team identity inherited from personal squad.

    I noticed that teamRoot was removed entirely from the config.json file in v0.9.1.

    Is this a separate issue than OP? Do the squad identities need to be created first before running squad init in the project?

  2. bradygaster commented on Mar 24, 2026

    @bradygaster
    bradygaster
    on Mar 24, 2026
    Collaborator

    there's no more npx method. if that's something folks need we can re-implement it but the idea is you install the CLI globally. i'll check on the other issues. to clarify - this is specific to a personal squad and not an in-repo squad right @stevenkuhn ?

  3. bradygaster
    added 3 commits that reference this issue on Mar 24, 2026

    test: personal squad init discovery tests (#576)

    c307187

    fix(cli): personal squad init via npx discovers ~/.config/squad (#576)

    6b6420c

    chore: sync templates and update agent history (#576)

    e0e3ff6

  4. bradygaster commented on Mar 24, 2026

    @bradygaster
    bradygaster
    on Mar 24, 2026
    Collaborator

    Fixed in PR #580. init --global now creates personal-squad/ alongside .squad/, and repo-level init detects it.

  5. bradygaster
    closed this as completedon Mar 24, 2026

  6. stevenkuhn commented on Mar 24, 2026

    @stevenkuhn
    stevenkuhn
    on Mar 24, 2026

    to clarify - this is specific to a personal squad and not an in-repo squad right @stevenkuhn ?

    Correct. I was looking for the correct order of operations when starting from a blank slate. The specific instructions to properly create a new personal squad and then create the repo-level squad that detects the personal one.

    From reading #580, this looks like it should work. If I'm understanding correctly, once I'm able to pull down the new change, I should be able to do the following:

    npm install -g @bradygaster/squad-cli

squad init --global

cd ~/code/stevenkuhn/project/
squad init

copilot --agent squad

    And then begin my first session with something like

    > I'm building a recipe sharing app with React and Node.js. Users can
> post recipes, search by ingredient, and save favorites.

    And my expectation is that team identity is set at the personal squad level, not the repo/project level.

  7. stevenkuhn commented on Mar 24, 2026

    @stevenkuhn
    stevenkuhn
    on Mar 24, 2026

    And my apologies to @Fl4t if I stepped over the npx method no longer being a thing.

  8. bradygaster commented on Mar 24, 2026

    @bradygaster
    bradygaster
    on Mar 24, 2026
    Collaborator

    all good!

  9. bradygaster commented on Mar 24, 2026

    @bradygaster
    bradygaster
    on Mar 24, 2026
    Collaborator

    here's my thinking - you'd never want to just use a personal squad for one project, right? from this summary it seems like that's your use case; that's like, opposite the use case for a personal squad.

    i'd strongly discourage someone use a personal squad for a short term project. Am I not understanding your use case right?

  10. bradygaster
    reopened this on Mar 24, 2026
  11. bradygaster
    added 3 commits that reference this issue on Mar 24, 2026

    test: personal squad init discovery tests (#576)

    9a76749

    fix(cli): personal squad init via npx discovers ~/.config/squad (#576)

    c9eba72

    chore: sync templates and update agent history (#576)

    9ac7360

  12. 1 remaining item

  13. bradygaster
    added 2 commits that reference this issue on Mar 24, 2026

    fix(cli): personal squad init via npx discovers ~/.config/squad (#576)

    14a3801

    chore: sync templates and update agent history (#576)

    a609176
  14. bradygaster
    closed this as completedin #580on Mar 24, 2026
  15. bradygaster
    added a commit that references this issue on Mar 24, 2026

    fix: personal squad init via --global discovers ~/.config/squad/ (#576)

    dcf9fd4
  16. bradygaster
    added
    bugSomething isn't working
    squadSquad triage inbox — Lead will assign to a member
    squad:eecom
    on Mar 24, 2026
  17. github-actions
    added
    squad:fido
    on Mar 24, 2026

  18. github-actions commented on Mar 24, 2026

    @github-actions
    github-actionsBot
    on Mar 24, 2026 – with GitHub Actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #576 — bug: init --global using npx for personal squad doesn't work
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: No strong capability match — routed to squad member.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  19. github-actions
    added
    go:needs-researchNeeds investigation
    on Mar 24, 2026

  20. github-actions commented on Mar 24, 2026

    @github-actions
    github-actionsBot
    on Mar 24, 2026 – with GitHub Actions
    Contributor

    📋 Assigned to EECOM (Core Dev)

    Issue: #576 — bug: init --global using npx for personal squad doesn't work

    EECOM will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    EECOM, work on issue #576

  21. qbradley
    added a commit that references this issue on Mar 25, 2026

    fix: resolve pre-existing test failures (github#273) (github#279)

    96241fe
  22. atuannguyen1101
    added a commit that references this issue on Mar 31, 2026

    fix: personal squad init via --global discovers ~/.config/squad/ (git…

    2605909
  23. bradygaster
    removed
    squad:eecom
    squad:fido
    on Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions