Personal coding seats
Personal coding seats let QualityMax run eligible, user-initiated coding work through an AI coding subscription your team member already has. This is a different choice from QualityMax-hosted AI or an API key: it can keep the AI-provider portion of that work on a subscription you already pay for.
Will this raise our AI bill?
Section titled “Will this raise our AI bill?”Usually, a personal seat does not add a separate QualityMax AI-provider charge for work routed through that seat. The work uses the connected person’s existing Claude Code or Codex subscription, subject to that provider’s own plan, limits, and terms.
That does not make every QualityMax cost disappear. Your QualityMax plan, cloud-sandbox usage, hosted-AI features, and any provider usage outside a subscription are separate. Choose the route that matches the work rather than assuming every task has the same billing model.
| Route | Who supplies the AI access | When it fits | Billing boundary |
|---|---|---|---|
| Personal coding seat | An individual connects their existing Claude Code or Codex subscription | A person wants their agent work to use that subscription | The provider applies the connected subscription’s limits and terms; QualityMax plan and execution usage remain separate |
| QualityMax-hosted AI | QualityMax provides the model capacity included with the plan | A team wants centrally managed access without individual connections | Uses the hosted-AI allowance or credits for the selected plan |
| Your API key | A customer provides an API account | A team needs its own provider account, model choice, or usage controls | The provider bills usage to that API account |
What you can connect
Section titled “What you can connect”- Codex: available as a personal coding seat.
- Claude Code: available as a personal coding seat.
- OpenCode: shown as a planned option, but it is not yet an active personal-seat connector. Do not plan a workflow around it until its connection flow is available.
The connected seat is an execution route, not a promise that every QualityMax feature will use it. The product presents the available engine for the task you are starting; choose a hosted or API-key route when that is the route your plan and workflow require.
Connect with informed consent
Section titled “Connect with informed consent”The person who owns the subscription connects it from their signed-in QualityMax account and accepts the Personal Coding Seats terms before it can be used. They can review whether a connection is active and disconnect it later.
Connecting a seat authorizes QualityMax to run user-initiated work through that subscription in an isolated execution environment. It does not give other users access to that person’s subscription. A team lead can decide which workflows are appropriate, but should not connect another person’s account on their behalf.
Connect Claude Code
Section titled “Connect Claude Code”Open Settings → Coding Agent Accounts → Connect Claude Code. When your deployment enables hosted Claude Code, select Open Claude Code to start the official, unmodified CLI in your private cloud environment. Follow its sign-in choices, open its Anthropic sign-in link, and complete any verification inside that terminal. Select Finish sign-in when the CLI reports success. QualityMax checks the CLI’s authentication status before showing the connection as active.
If hosted sign-in is unavailable, the same dialog accepts your own Anthropic API key for Claude Code. API usage is billed to that Anthropic account. Settings → AI Keys (BYOLLM) configures keys for other AI features separately. Native Claude Code also preserves its own authentication choices. Review Anthropic’s authentication and hosting terms; users pay Anthropic directly for their subscription or API access.
Credential JSON imports and setup-token pastes are no longer accepted. Previously imported subscriptions must reconnect through native sign-in. A QualityMax MCP API token connects tools to Claude; it does not connect your Claude personal seat. No setup prompt or credential export is required.
If the connection expires, use Open Claude Code again. Closing the dialog pauses the environment; an interrupted sign-in is not reported as successful. Disconnect permanently deletes the hosted environment and its native login state. Disconnect before switching between a hosted environment and a separately saved API key.
What QualityMax can and cannot see
Section titled “What QualityMax can and cannot see”QualityMax needs enough context to run the work you request: the selected project or repository context, the task, execution state, and resulting test or code evidence. Treat those artifacts according to your normal repository and access policies.
Hosted Claude Code stores its native login state inside its private environment. QualityMax retains only an environment reference and connection status in its seat registry; it does not import, read back, or export the CLI’s credential files. The sign-in terminal is relayed to its signed-in owner and excluded from session recording. Like other hosted execution, the environment is operated by QualityMax and its sandbox provider; this is not a claim that infrastructure operators cannot access its disk.
This is not a replacement for reviewing an agent’s proposed changes. Keep repository permissions narrow, inspect generated artifacts, and use the same pull-request and test gates you would use for any other automation.
One active turn per seat
Section titled “One active turn per seat”A personal seat is serialized per user: one active turn uses that seat at a time. If the same person starts parallel work, the later turn waits or asks them to try again after the current turn finishes.
Hosted Claude Code reserves the seat for the entire coding session, including follow-ups, or for one sign-in session. Reconnecting and disconnecting also require that seat to be idle.
This is intentional. A connected subscription is one person’s route, so QualityMax prevents competing work from using it at the same time. Serializing a user’s seat protects the connection and makes ownership of a running task clear. It is not a limit on all QualityMax work: hosted AI, API-key routes, and other users’ seats can follow their own available concurrency.
Isolated execution and credential boundaries
Section titled “Isolated execution and credential boundaries”Hosted Claude Code reuses one private environment for its owner so the CLI can retain its native login. Repository workspaces and temporary QualityMax/Git access files are cleared between coding sessions, and the environment pauses afterward. Other seat routes use their own task sandbox lifecycle.
Hosted Claude sessions do not provide automatic Files snapshots, live Preview, or workspace checkpoint restoration. Save work through the repository’s commit and pull-request workflow before ending a session; the next session starts with a fresh workspace. Native CLI state remains private to the environment until disconnect or provider expiration.
Use the least access needed for the repository and task. Before enabling a team workflow, agree on who may connect a seat, which repositories it may work with, how generated changes are reviewed, and when a connection should be removed. For broader controls, read Security and Evidence & trust.
Choose a route
Section titled “Choose a route”Use a personal seat when an individual wants to use the subscription they already have. Use hosted AI when the team wants centrally managed capacity, or an API key when provider-account control matters more than seat convenience. Then start with qmax-code or connect a coding agent through MCP, and keep the resulting tests and changes reviewable.