You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
loadCapabilities() in packages/squad-sdk/src/ralph/capabilities.ts hardcodes ~/.squad/machine-capabilities.json as the user-level fallback path. It does not use resolveSquadHome() (added in #1038 / PR #1041), so the SQUAD_HOME env var is ignored.
Reproduction
mkdir -p /mnt/synced-drive/.squad
cat > /mnt/synced-drive/.squad/machine-capabilities.json << 'EOF'{ "needs": ["node", "dotnet"] }EOFexport SQUAD_HOME=/mnt/synced-drive/.squad
# Ralph triage — machine-capabilities.json is NOT loaded
Ralph behaves as if no machine-capabilities.json exists, routing all needs:* issues regardless of capability.
Expected behavior
loadCapabilities() should resolve the user-level fallback through resolveSquadHome() so that SQUAD_HOME overrides are respected.
Actual behavior
The path is always path.join(os.homedir(), '.squad', 'machine-capabilities.json').
Relevant source:packages/squad-sdk/src/ralph/capabilities.ts, loadCapabilities() line 105.
resolveSquadHome() is already exported from resolution.ts (added in #1038 / PR #1041) and is the correct replacement.
Environment
squad-sdk: v0.10.0
OS: any
Node: v22+
Related: Issue #1038 (SQUAD_HOME feature), PR #1041, #1279 (same root cause in comms-teams.ts).
Activity
test: fix Teams home resolution mocks
fix: respect SQUAD_HOME env var, implement SQUAD_PERSONAL_DIR, fix Wi…