MENLO PARK, Calif. — Corepass has given Remy, its AI coding agent, a team workspace — “a workspace, not just shared billing,” in the company’s words — that lets an engineering organization manage seats, see what the agent costs and decide which repositories count as team work, without letting administrators read anyone’s conversations or code.
Colleagues join by email invitation or through an allowed email domain, and each gets a plan of their own that can be changed as their work changes. Three roles — owner, admin and member — decide who can change seats and billing; everyone else simply works.
Repositories decide what is team work
Attribution runs through repositories. An owner or admin approves a repository and binds it to the team; runs inside it are then attributed to the team. Everything else — including projects that exist only on a developer’s machine — stays personal. “Unbound and local work never reaches the team,” the Remy for teams page says.
Usage you can read
Administrators see runs, tokens, agent work and cost, broken down by member and by repository, against one centrally billed account. They can set spend limits for the whole team or for a single member, and seats, invoices and payment sit in one place.
Visible to the team
- Name, email, role and seat type
- Number of runs, tokens used and cost
- Which models were used
- Agent run counts
- PR and task metrics
- Activity in repositories bound to the team
Never visible to the team
- The content of any conversation, including private ones
- Prompts, and the code Remy reads or writes
- Anything in repositories not bound to the team
- Anything done in Personal or in another team
Identifiers, not content
The line Corepass draws is between identifiers and content. A team sees counts, costs, models and repository names; it never sees a conversation, a prompt or the code the agent touches. Every member can read the same policy inside the app, in full, at any time. Administrators see one row per member on the team’s Usage page, and that page is the only place a member’s activity is reported.
A team sees counts, costs, models and repository names. It never sees a conversation, a prompt or the code.
Larger organizations can move to Enterprise, which adds single sign-on, SCIM directory sync, custom role-based access controls and custom data retention. Team workspaces start with model training on their data switched off, and Enterprise data is never used for training. Current team pricing is on the pricing page.