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
Rename .ai-team/ to .squad/ with backward-compatible migration #69
We named the team state directory .ai-team/ but we should have called it .squad/. It's our product name, it's shorter, and it's immediately clear what tool owns it.
Scope of Change
This is a breaking rename affecting ~745 occurrences across ~123 files in the source repo alone — plus every customer repo that has run squad init.
What references .ai-team/:
squad.agent.md — the coordinator prompt (paths in every spawn template, every file operation)
This is me personally speaking to all Squad team members and users - I'm so glad you're enjoying Squad, but this is a change we need to make now, while growth is still in its infancy, to make sure our files are obvious from now on. ai-team is so bland and generic. I'm shocked no one caught it earlier. We need to make sure it is obvious where "OUR" files are in users' repositories. We'll try to implement this in such a way that it impacts only new users, but this may be the first of what-I-hope-is-less-than-2-forever breaking changes we ever ship in Squad.
This change will come prior to 1.0. I'm going to try to get this into 0.5.0, but if I try it myself on a few existing projects and things hit the oscillator, I'll come up with a one-time workaround.
We've designed a migration strategy that balances automatic upgrade with user control. Before we implement this, we want your feedback. Does this approach work for your workflows? Any edge cases we're missing?
Three Migration Paths (All Scripted)
1. Auto-Migrate (Default)
When you run any Squad command after upgrading to v0.5.0, migration happens automatically:
npx github:bradygaster/squad init
🔄 Migrating .ai-team/ → .squad/...
📦 Backed up to .ai-team.backup-20260216-143022/
📁 Moved .ai-team/ → .squad/
📝 Updated .gitignore and .gitattributes
✅ Changes committed. Push when ready: git push
What happens:
Pre-flight checks (repo clean, no conflicts)
Auto-backup to .ai-team.backup-{timestamp}/
Atomic git move via git mv
Config updates (.gitignore, .gitattributes)
Auto-commit with message
You just need to push
2. Defer Auto-Migrate (Scripted Workaround)
If you want control over timing:
# Skip auto-migrationexport SQUAD_SKIP_AUTO_MIGRATE=true
npx github:bradygaster/squad init
# → Shows: "⚠️ .ai-team/ detected. Migrate when ready: squad upgrade --migrate-directory"# When you're ready:
npx github:bradygaster/squad upgrade --migrate-directory
# → Runs same migration script, YOU commit and push
3. Rollback (Safety Valve)
Changed your mind? Rollback is one command:
squad upgrade --rollback-migration
# → Restores .ai-team/ from backup# → You can downgrade: npx github:bradygaster/squad@v0.4.1
Key Points
✅ Automatic by default - Zero friction for 95% of users
✅ Fully scripted workaround - Defer with env var, migrate when ready
✅ Safe - Auto-backup, pre-flight checks, rollback available
✅ No dual-path maintenance - v0.5.0 only reads .squad/
✅ Forward-only - Users upgrade linearly (v0.4.1 → v0.5.0)
Per Brady's directive (2026-02-20): wisdom.md and now.md are now part of v0.5.0 instead of deferred to v0.6.0. Rationale: we're already touching every path during the rename — adding two files under .squad/identity/ is near-zero marginal effort.
New sub-issue: #107 — Add identity layer (wisdom.md + now.md) to .squad/ structure
New sub-issue: #108 — Scrub email addresses from .squad/ files during migration
The squad upgrade --migrate-directory tool must also scrub user email addresses that were written to .ai-team/ files by earlier versions. This is now part of the auto-migration checklist.
Activity
bradygaster commentedon Feb 15, 2026
This is me personally speaking to all Squad team members and users - I'm so glad you're enjoying Squad, but this is a change we need to make now, while growth is still in its infancy, to make sure our files are obvious from now on.
ai-teamis so bland and generic. I'm shocked no one caught it earlier. We need to make sure it is obvious where "OUR" files are in users' repositories. We'll try to implement this in such a way that it impacts only new users, but this may be the first of what-I-hope-is-less-than-2-forever breaking changes we ever ship in Squad.This change will come prior to 1.0. I'm going to try to get this into 0.5.0, but if I try it myself on a few existing projects and things hit the oscillator, I'll come up with a one-time workaround.
Sorry in advance if it comes to that!
docs(ai-team): agent history updates and decision inbox entries
spboyer commentedon Feb 16, 2026
Can we have a migration script included in the move to this version
bradygaster commentedon Feb 16, 2026
Migration Plan for v0.5.0: .ai-team/ → .squad/
We've designed a migration strategy that balances automatic upgrade with user control. Before we implement this, we want your feedback. Does this approach work for your workflows? Any edge cases we're missing?
Three Migration Paths (All Scripted)
1. Auto-Migrate (Default)
When you run any Squad command after upgrading to v0.5.0, migration happens automatically:
What happens:
2. Defer Auto-Migrate (Scripted Workaround)
If you want control over timing:
3. Rollback (Safety Valve)
Changed your mind? Rollback is one command:
Key Points
✅ Automatic by default - Zero friction for 95% of users
✅ Fully scripted workaround - Defer with env var, migrate when ready
✅ Safe - Auto-backup, pre-flight checks, rollback available
✅ No dual-path maintenance - v0.5.0 only reads .squad/
✅ Forward-only - Users upgrade linearly (v0.4.1 → v0.5.0)
Timeline
What We Need From You
Would this migration approach work for your workflow?
Feedback welcome here or in Discussions. We want to get this right before we start coding.
bradygaster commentedon Feb 16, 2026
Note - these dates aren't accurate. We'll have it out by EOW.
feat: dual-path support for .squad/ and .ai-team/ directories
Merge feature/dual-path-squad-support into develop
bradygaster commentedon Feb 18, 2026
Updated Scope: Single .squad/ Folder
Brady directive (Feb 18): Everything goes inside
.squad/— no separate templates directory.Impact on your audit:
.ai-team-templates/→.squad/templates/(nested inside .squad/)Your 3-PR plan still works:
Migration logic addition:
.squad/templates/subdirectory structure.squad/templates/first, fall back to.ai-team-templates/Full directive captured in
.ai-team/decisions/inbox/copilot-directive-single-squad-folder.mdbradygaster commentedon Feb 20, 2026
v0.5.0 Consolidation Directive — Clarified
From: Today's session with Brady, Keaton, Fenster
This comment clarifies the consolidation scope for the .ai-team/ → .squad/ migration in v0.5.0.
Brady's Directive (Consolidated)
In v0.5.0, consolidate everything under .squad/ except:
Rationale: Eliminate the naming sprawl. One branded folder (.squad/) for all team artifacts; npx-critical files stay at root.
Directory Migration Plan
.ai-team/ → .squad/
.ai-team-templates/ → .squad/templates/ (merged under .squad)
templates/ → templates/ (stays at root)
Guard Workflow Policy
Block .squad/ entirely from protected branches** (main/preview/insider).
Why simple, no carve-outs:
Guard workflow updated Feb 20 to also block docs/proposals/ (internal design work).
Affected Scopes
Branch Content Policy (Formalized Feb 20)
✅ ALLOWED on main/preview/insider: index.js, package.json, templates/, .github/, docs/ (except proposals), test/
❌ FORBIDDEN on main/preview/insider: .squad/, .ai-team/, .ai-team-templates/, team-docs/, docs/proposals/
See .ai-team/decisions/inbox/copilot-branch-content-policy.md for full policy.
Status: Epic updated with consolidated directive from today's session.
docs(ai-team): session log, orchestration entries, decision merge
bradygaster commentedon Feb 20, 2026
Scope Update: Identity Layer added to v0.5.0
Per Brady's directive (2026-02-20):
wisdom.mdandnow.mdare now part of v0.5.0 instead of deferred to v0.6.0. Rationale: we're already touching every path during the rename — adding two files under.squad/identity/is near-zero marginal effort.New sub-issue: #107 — Add identity layer (wisdom.md + now.md) to .squad/ structure
Updated sub-issue list:
docs(ai-team): Capture identity layer scope change to v0.5.0
bradygaster commentedon Feb 20, 2026
Privacy: Email scrub added to migration scope
New sub-issue: #108 — Scrub email addresses from .squad/ files during migration
The
squad upgrade --migrate-directorytool must also scrub user email addresses that were written to .ai-team/ files by earlier versions. This is now part of the auto-migration checklist.Updated sub-issue list:
bradygaster commentedon Feb 20, 2026
Complete. .ai-team/ → .squad/ migration shipped via PRs #109–#113: CLI dual-path (#111), workflow dual-path (#109), .ai-team-templates/ move (#112), docs/test updates (#113), email scrubbing (#110). Backward-compatible migration via 'squad upgrade'.
Merge pull request github#69 from jbenami_microsoft/squad/64-watchdog…