.squad/config.json contains a machine-specific absolute teamRoot path

.squad/config.json e.g.,

{
  "version": 1,
  "teamRoot": "D:\\projects\\bc\\17343-add-squad"
}

Committing local paths makes the configuration non-portable across developers/agents.
When adding a squad to an existing project shouldn't it be set to

{
  "version": 1,
  "teamRoot": "."
}

I tried this change on my squad with squad doctor

🩺 Squad Doctor
═══════════════

Mode: remote

✅  .squad/ directory exists — directory present
✅  config.json valid — parses as JSON, schema OK
✅  team root resolves — resolved to D:\projects\bc\17343-REAL-add-squad
✅  team.md found with ## Members header — file present, header found
✅  routing.md found — file present
✅  agents/ directory exists — directory present (6 agents)
✅  casting/registry.json exists — file present, valid JSON
✅  decisions.md exists — file present

🏗️ Squad Triage — Flight (Lead)

Issue: #356 — .squad/config.json contains a machine-specific absolute teamRoot path
Assigned to: Flight (Lead)
Reason: No specific domain match — assigned to Lead for further analysis

@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.

⚠️ No squad member found matching label squad:fenster. Check .squad/team.md (or .ai-team/team.md) for valid member names.

📋 Assigned to EECOM (Core Dev)

Issue: #356 — .squad/config.json contains a machine-specific absolute teamRoot path

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 #356

fix: cross-platform filename and config path issues (#348, #356)

history: EECOM cross-platform fixes (#348, #356)

Merge pull request #404 from bradygaster/squad/348-356-cross-platform…

Already fixed by PR #404 (merged to dev). Closing.

fix: use relative teamRoot path in config.json (#356)

fix: implement P1 UX polish from Marquez audit (github#356)

feat: rich progress indicators for agent work (github#357)

feat: accessibility hardening and guidelines (github#359)

Navigation Menu

Repository navigation

.squad/config.json contains a machine-specific absolute teamRoot path #356

🏗️ Squad Triage — Flight (Lead)

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

📋 Assigned to EECOM (Core Dev)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

.squad/config.json contains a machine-specific absolute teamRoot path #356

Description

Activity

github-actions commented on Mar 13, 2026

🏗️ Squad Triage — Flight (Lead)

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

github-actions commented on Mar 13, 2026

github-actions commented on Mar 13, 2026

📋 Assigned to EECOM (Core Dev)

bradygaster commented on Mar 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions