Skip to content

Personal squad docs reference ~/.squad/ instead of platform-specific paths #343

Closed

Description

@jsturtevant

Problem

The SDK correctly resolves the personal squad path using platform-specific directories via resolveGlobalSquadPath():

Platform Actual Path
Linux $XDG_CONFIG_HOME/squad/.squad/ (default ~/.config/squad/.squad/)
macOS ~/Library/Application Support/squad/.squad/
Windows %APPDATA%\squad\.squad\

However, documentation and code comments throughout the codebase refer to ~/.squad/ as the personal squad path, which is incorrect on all platforms.

Affected Files

Documentation (21+ references)

  • docs/src/content/docs/guide/personal-squad.md — Lines 21, 54, 68, 88, 103, 108, 123, 132, 139, 254, 262, 267, 295, 306, 309 all reference ~/.squad/
    • Example (line 21): "Your team identity — agents, charters, skills, casting history — moves to a global directory (~/.squad/)"

Code Comments

  • packages/squad-sdk/src/sharing/consult.ts — Lines 898, 1009, 1010, 1038, 1056 have comments saying "Routes to ~/.squad/"

Correct Implementation (no code change needed)

The actual path resolution is correct:

// packages/squad-sdk/src/resolution.ts:232-255
export function resolveGlobalSquadPath(): string {
  // Returns platform-specific path (Linux: ~/.config/squad/)
}

// packages/squad-sdk/src/sharing/consult.ts:315-316
export function getPersonalSquadRoot(): string {
  return path.resolve(resolveGlobalSquadPath(), '.squad');
}

Fix

Update all ~/.squad/ references in docs and comments to either:

  1. Use a platform-agnostic description (e.g., "your personal squad directory")
  2. Show all three platform paths in a table
  3. Reference the function name (resolveGlobalSquadPath()) in code comments

Files

  • Docs: docs/src/content/docs/guide/personal-squad.md
  • Code comments: packages/squad-sdk/src/sharing/consult.ts
  • Correct implementation: packages/squad-sdk/src/resolution.ts

Activity

  1. added 2 commits that reference this issue on Mar 11, 2026
    13a4c9b
    f0b1d51
  2. added a commit that references this issue on Mar 11, 2026
    09b6a56
  3. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #343 — Personal squad docs reference ~/.squad/ instead of platform-specific paths
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    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.

  4. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

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

  5. bradygaster commented on Mar 13, 2026

    @bradygaster
    Collaborator

    📌 Brady requested this issue be assigned to @diberry (docs/UX triage). Pending collaborator invite to complete assignment.

  6. added 3 commits that reference this issue on Mar 14, 2026
    9bb1067
    94307e0
    6dbf688
  7. added a commit that references this issue on Mar 18, 2026
    ee10f72
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

    go:needs-researchNeeds investigationpriority:p2Next sprintsquadSquad triage inbox — Lead will assign to a membertype:docsDocumentation work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions