📢 Heads up: .squad/ will be removed from version control before v1.0

[bradygaster]

Hey folks! ��

Wanted to give everyone a heads-up on an important change coming before v1.0.

What's changing

We're going to remove the .squad/ directory from version control. Since SDK mode (squad.config.ts + squad build) now generates .squad/ as build output, tracking it in git creates merge conflicts, dirty working trees, and CI noise that we don't need.

Timeline

• v0.9.0 (this weekend): New release ships. We'll begin documenting the migration path and adding tooling to make this smooth.
• v0.10.0 (the release after v0.9.0): .squad/ gets added to .gitignore and removed from tracking in this repo. CI workflows will run squad build to regenerate it.

That gives everyone one full release cycle to prepare.

What this means for you

If you're building on Squad and have a .squad/ directory tracked in your repo:

1. Your local .squad/ files stay on disk — nothing gets deleted
2. squad build regenerates .squad/ from your squad.config.ts
3. We'll add a squad export command so you can save your team's state (charters, history, decisions) before the switch
4. If you're not using SDK mode yet, you'll want to adopt it (squad init --sdk) before this change lands

The Squad squad

Before we remove .squad/ from this repo, we'll publish the Squad project's own team configuration somewhere public so the community can reference it — whether you want to study how a large squad is set up, or use it as a starting point for your own team.

Full PRD

The implementation plan is tracked in #498. Feel free to comment there with questions or concerns.

We want to make this transition as smooth as possible. If you see any issues with this plan or have suggestions, please let us know here or on #498!

[laurentkempe]

I am confused, how do you share the squad with a human team then?

[bdangit]

It sounds like your squad config (aka squad.config.ts) gets checked in. From there the squad gets built at runtime, whenever you start your team of agents to do work for you.

[melodiouscode]

But how do the history files, rules, charters, etc get shared with the human team. Or between devices?

[mikeholczer]

If you're not using SDK mode yet, you'll want to adopt it (squad init --sdk) before this change lands

Is this suggesting that everyone using squad should be using SDK mode? I thought that was just for building tooling? Or is this whole announcement just relevant to people building tooling on top of squad?

[melodiouscode]

Hi @bradygaster; firstly I love Squad.... I'd like to understand more about the change here and how it affects multi person teams that are using squad. I have a number of my staff making use of squad accross projects and they also really like it!

Also; any thoughts in turning on sponsorship on the repo? I'd love to give a little back (personally for now, but who knows about corporate eventually).