Owner
Manages members, company settings, and content. Every team has one.
One shared context file your whole team's agents read
The Company plan adds one shared Company Strap on top of your personal one. Every member's agents read the same company context before they answer, so you stop re-explaining how the team works to every tool. Roles, section permissions, an activity view, and admin controls come built in.
How a Company Strap works
One shared file
A Company Strap is the same structured profile as a personal one, owned by the team. It holds how you work, what you are building, and the conventions everyone should follow.
Every agent reads it
Members connect their own agents over MCP and read the shared Strap before they act, so answers match how the team actually operates instead of drifting.
Proposals, not sludge
Agents propose narrow updates as they learn. Section permissions decide who edits directly and who proposes, and every change is attributed.
See the activity
The activity view shows reads, proposals, and edits across every member and agent, so the shared context stays accountable.
Roles that keep the file trusted
A shared file only stays useful if edits are governed. Roles and section permissions decide who can change what, and every edit is attributed.
Admin
Manages members and content. Keeps the shared Strap sharp.
Member
Reads the shared Strap and proposes updates their work reveals.
Free for your whole team
A Company Strap is free: invite as many members as you need, and run AI on the included key or your company's own key (BYOK).
Company plan questions
A Company Strap is one shared context file that every member's agents read before they act. It holds the canonical company context: how the team works, what it is building, and the conventions and constraints that apply to everyone, so agents stop drifting from how the team actually operates.
A wiki is a large, complete record for people to search. A Company Strap is short, curated, and written to be read by agents before they answer. It is the profile your AI reads, not the archive your team browses. Most teams keep both.
Three: Owner, who manages company settings, members, and content; Admin, who manages members and content; and Member, who reads and proposes. Section permissions can further control who edits each section directly versus by proposal, and every change is attributed in the activity view.
No. A member needs a Strap account to join, but not a personal Strap. They connect their own agents over MCP and read the shared Company Strap. They can keep a personal Strap too, and switch between them from the workspace dropdown.
Nothing. It is free, with as many members as you need, and every company supports BYOK so model spend can run on the company's own key.