Skip to content

Personal/global squad fails to reslove #1010

Closed

Description

@tzahi2k1

Hi,
I might do someting worng but on 2 diffrent machines I it fails to resolve that I have a global one.
I follow the instructions:

C:\Users\tzkarni\AppData\Roaming> squad init --global

It created a squad and the status seems ok.

Squad Status

Active squad: personal (global)
Path: C:\Users\tzkarni\AppData\Roaming\squad.squad
Reason: No repo .squad/ found; personal squad exists at global path

Repo resolution: not found
Global path: C:\Users\tzkarni\AppData\Roaming\squad
Global squad: C:\Users\tzkarni\AppData\Roaming\squad.squad

Than I want to my source code folder and :
squad init
⚠ node:sqlite is not available in Node.js v20.18.3.
The Copilot SDK uses node:sqlite for session storage.
Upgrade to Node.js ≥22.5.0 or launch with --experimental-sqlite.
Squad will attempt to continue, but session persistence may fail.

Let's build your team.

✓ .squad\config.json
✓ .squad\agents\scribe\charter.md
✓ .squad\agents\scribe\history.md
✓ .squad\identity\now.md
✓ .squad\identity\wisdom.md
✓ .squad\ceremonies.md
✓ .squad\decisions.md
✓ .squad\team.md
✓ .squad\routing.md
✓ .squad/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.

PS C:\Users\tzkarni\source\repos\foo> squad status
⚠ node:sqlite is not available in Node.js v20.18.3.
The Copilot SDK uses node:sqlite for session storage.
Upgrade to Node.js ≥22.5.0 or launch with --experimental-sqlite.
Squad will attempt to continue, but session persistence may fail.

Squad Status

Active squad: repo
Path: C:\Users\tzkarni\source\repos\foo.squad
Reason: Found .squad/ in repository tree

Repo resolution: C:\Users\tzkarni\source\repos\foo.squad
Global path: C:\Users\tzkarni\AppData\Roaming\squad
Global squad: C:\Users\tzkarni\AppData\Roaming\squad.squad

Now in the docs it says that I should see: ✅ Squad initialized.
.squad/config.json → teamRoot: {personal squad directory}
Team identity inherited from personal squad.
Project-local state (decisions, logs) stays here.

But as can been it is not,
Than I went to the config.json and got:
cat ..squad\config.json
{
"version": 1,
"teamRoot": "C:\Users\tzkarni\source\repos\foo"
}

instead of pointing to the global.
Moreover, even when I changed the json to point to the global one, it stills refer to local in the copilot session.
I think it has to do with the agent.md files which state to enter to init mode.

I also created a team in the global and then asked it in the project level to address the team root thier. Only than he made the right resolution,

OS: windows
agent version 0.9.1

Activity

  1. JCGreaves commented on Apr 28, 2026

    @JCGreaves

    I belive I'm seeing the same issue with my step as well but in my case when I inialise squad in my repo having initialised a global squad first the config.json just looks like this. This then I think has a knock on to the creation of the team.md file inside the repo as well.

    v0.9.4

    { "version": 1, }

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

    triagedIssue has been triagedwave:1-nextWave 1 — immediate next sprint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions