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
{{ message }}
Repository navigation
[External State] Tracking: command and docs integration gaps #1402
picking up #1397 and #1398 — both are the same team.md read/write miss, so they'll land as one PR reusing the effective-state resolution from the #1396 export fix. #1399 crosses into squad-sdk agent discovery, that one comes separately.
The new container hosting guide (#1566) and production ops guide (#1568) both include state-backend selection guidance for containerized deployments, with explicit warnings about branch-based (orphan) state being unsafe for concurrent writes from multiple pods. Both cross-link to this issue as the tracking home for external state gaps. Not a duplicate — these are the deployment docs companion. See umbrella #1564 for full context.
Closing this integration umbrella as complete. Live state confirms #1396, #1397, #1398, #1399, and #1400 are closed by merged fixes/docs (#1443, #1464, #1465, #1466). The remaining #1401 question is a separate move-vs-copy product decision; current copy-back behavior is explicitly documented by #1466 and #1401 remains open to decide whether it should change.
Activity
omercangumus commentedon Jul 10, 2026
picking up #1397 and #1398 — both are the same team.md read/write miss, so they'll land as one PR reusing the effective-state resolution from the #1396 export fix. #1399 crosses into squad-sdk agent discovery, that one comes separately.
fix(cli,sdk): follow externalized state in squad cast agent discovery (…
docs: align external-state page with actual externalize/internalize b…
fix(cli): follow externalized state in squad copilot and squad rc (#1464
bradygaster commentedon Aug 3, 2026
The new container hosting guide (#1566) and production ops guide (#1568) both include state-backend selection guidance for containerized deployments, with explicit warnings about branch-based (orphan) state being unsafe for concurrent writes from multiple pods. Both cross-link to this issue as the tracking home for external state gaps. Not a duplicate — these are the deployment docs companion. See umbrella #1564 for full context.
docs: production operations — observability, state backend selection,…
docs: production security hardening — threat model, prompt injection …
chore: promote dev -> main (v0.12.0) (#1698)
bradygaster commentedon Sep 24, 2026
Closing this integration umbrella as complete. Live state confirms #1396, #1397, #1398, #1399, and #1400 are closed by merged fixes/docs (#1443, #1464, #1465, #1466). The remaining #1401 question is a separate move-vs-copy product decision; current copy-back behavior is explicitly documented by #1466 and #1401 remains open to decide whether it should change.