Team Collaboration

Signed out, everything is local. Signing in adds a cloud lane that shares project metadata — never your code.

Seeing each other

The header’s team chip opens the roster: who owns what, what’s routed to them, and their last decision. It’s a footprint, not a presence indicator. Settings → Team manages seats and members.

Not colliding

• Claims — mm_claim_spec claims a teammate’s spec; first claim wins, and /mm:spec-start refuses to start someone else’s spec without one.
• Radar — mm_team_radar checks before you start whether anyone else is on that spec.
• Path claims — in a shared checkout, mm_claim_paths and mm_release_claims keep two agents off the same files.

Staying in touch

/mm:checkin posts what you’re working on; /mm:team-status shows the team’s check-ins. Verification reports can be shared to the team from Settings → sharing.