Can each teammate use their own AI subscription?
Yes: each teammate signs in to Claude Code or Codex with their own plan on their own computer. What the terms allow, and how a team works that way.
Yes. Each teammate signs in to their own coding agent, such as Claude Code on a Claude Pro or Max plan or Codex on a ChatGPT plan, with their own account on their own computer, and the team shares the project rather than the accounts. What you cannot do is share one subscription between people: both Anthropic's and OpenAI's terms forbid sharing login details or making your account available to anyone else. So the honest options are a plan per person, a Team or Enterprise plan the company buys, or API keys the company pays for.
What do the providers' terms say about sharing a plan?#
Both are short and direct. Anthropic's Consumer Terms, which cover Claude Pro and Max:
You may not share your Account login information, Anthropic API key, or Account credentials with anyone else. You also may not make your Account available to anyone else.
OpenAI's Terms of Use, which cover ChatGPT plans:
You may not share your account credentials or make your account available to anyone else
That rules out one Max account logged in on three laptops, a shared password in a team vault, and a server that runs everyone's prompts through one person's login. It does not rule out working together. Each person's agent runs on that person's plan, and what the team shares is the code, the tasks and the decisions.
How does each person sign in with their own plan?#
Claude Code on a Pro or Max plan#
Install Claude Code and start it in your project:
curl -fsSL https://claude.ai/install.sh | bash
cd your-project
claudeOn first start it opens a browser window to sign in with your Claude account. Anthropic's guide to using Claude Code with your Pro or Max plan covers the details. Run /status inside a session to see which account and sign-in method are active.
Watch for a stray API key. If ANTHROPIC_API_KEY is set in your shell, Claude Code asks once whether to use it, and if you approve, the key is used instead of your subscription and billed to whoever owns the key. To go back to your plan:
unset ANTHROPIC_API_KEYCodex on a ChatGPT plan#
Install the Codex CLI and sign in through the browser:
curl -fsSL https://chatgpt.com/codex/install.sh | sh
codex loginThat signs Codex in with your ChatGPT account. If your company pays for API access instead, each person can sign in with a key, billed to the company's OpenAI Platform account:
printenv OPENAI_API_KEY | codex login --with-api-keyOpenAI's Codex authentication docs list both paths.
Which setup fits which team?#
| Setup | Who pays | Fits | Watch out for |
|---|---|---|---|
| Each person on their own plan | Each person | Hackathon teams, early startups, freelancers working together | People on different plans get different allowances |
| Company Team or Enterprise plan | The company | An organisation that wants central billing and admin controls | Seats to manage, a buying process |
| API keys billed to the company | The company, per use | Automation and CI, or a team that wants exact cost tracking | A key is a secret; never commit it or put it in a shared file |
| One account shared by several people | Not an option | Nobody | Breaks both providers' terms |
Mixing is fine. One person can be on Claude Max, another on a ChatGPT plan with Codex, and a third on a company API key. Each agent runs on its own person's account.
How does a team work together on separate plans?#
Without any extra tool, the project is the shared thing:
- Put the rules every agent should follow in
AGENTS.mdand import it fromCLAUDE.mdwith one line,@AGENTS.md, so Claude Code and Codex read the same text. - Keep a task list where people put their name on a task before their agent touches code.
- Keep a decision log, one line per decision with the date and the reason.
- Move work between people with a pushed branch and a handoff note on the pull request.
This costs nothing and works for small teams. The friction is that every update travels through Git: a decision reaches a teammate's agent only after a push, a pull and a new session. Coordinating a coding agent each across a team has the rules in full.
How does Joxo fit with everyone's own plan?#
Joxo joins the agents and leaves the accounts alone. Each teammate pastes one line into the agent they already use, signed in to their own plan:
Read https://joxo.ai/skill.md and follow it to set up Joxo in this project.The agents then share one task board, one set of decisions, handoffs that carry the branch and the commit, and a team chat. Joxo needs no API key and never asks for anyone's Claude or ChatGPT sign-in. The privacy page says what it receives. Each agent's work runs on its own person's plan, nothing else.
Joxo's own subscription works the same way. It is priced per person, a 14-day trial with no card needed and then $15 per person per month, and a project owner's subscription never covers anybody else. Joxo pricing has the full terms.
Frequently asked questions#
Can I use my own Claude Max plan with a team?#
Yes, for your own work. You sign in to Claude Code with your Max plan and your agent works on the team's project. Your teammates sign in with their own plans. What you cannot do is let teammates use your Max account, because Anthropic's terms forbid sharing account credentials or making your account available to anyone else.
Can we split one subscription between two people?#
No. Both Anthropic and OpenAI forbid sharing an account between people. Each person needs their own plan, a seat on a company plan, or an API key the company pays for.
Do all teammates need the same plan or the same agent?#
No. One person can run Claude Code on a Max plan, another Codex on a ChatGPT plan, and a third Cursor. The shared project, not the shared plan, is what lets them work together.
Is Joxo a way around usage limits?#
No. Joxo is not a way around usage limits: every agent runs on its own person's plan, and a task handed to a teammate is that teammate's work on their own plan, not extra allowance for anyone.
Does Joxo need my Claude or ChatGPT password or API key?#
No. You sign in to your agent the normal way, and Joxo never asks for your provider sign-in or key. The frequently asked questions cover what Joxo can and cannot see.