Studio Enterprise
A private AI workspace for every employee, connected to your company.
Prepare a customer brief, compare supplier documents or work through a question with AI that can use your company’s shared knowledge and connected tools. Each person works in their own browser workspace, on your company’s Claude, Codex or Cursor plans. Add a colleague when you want to work together, or share a reusable agent as a Crew.
An illustrative example: Leena is preparing for a customer meeting. She wants one brief drawn from the account documents and the company’s approved product information, with unanswered questions kept visible.
Customer meeting Illustrative
AI for this workspace
Connected tools
Google DriveConnected
SlackConnected
Shared knowledge
Approved product information
Customer meeting guide
Working files
Account notes
Customer brief · draft
Workspace access
Private until Leena adds co-owners. Admins and assigned reviewers can inspect chats, files and costs; every review is recorded.
Customer meeting · Leena’s chatClaude Code
Prepare a brief for my customer meeting from the account notes and our approved product information. Flag anything we still need to confirm.
Read account notes and shared product knowledge
Draft ready. I’ve saved the customer’s priorities, relevant product details and sources in the brief. Their requested delivery date still needs confirmation.
I’ve checked the brief. Keep the delivery date as an open question and add a handover note for my colleague.
Brief updated. The handover includes the open question and the documents behind it.
Leena reviews the result before handing it over. If a colleague needs to continue the work, she can add them as a co-owner; they get their own chat in the same workspace. Her files and the handover are already there.
Cowork
For business work: research, documents, browser tasks and a dashboard, through chat.
Dev
For engineers: ask your coding agent to change files, run commands and check the tests.
Local
Work on files on your own computer, with the same agents and tools.
Company plans and usage
Use the plans you have. See who uses them.
Connect your company’s Claude, Codex and Cursor accounts. People use the plans you share without receiving the login, and you can see cost and usage per person and workspace. A shared account’s owner pays for the work run on it.
Coding accountsOn your server
Usage this weekBy person and workspace
Illustrative example.
Connected from day one
Set up once. Everyone starts ready.
Your plans
Claude Code, Codex, Cursor, Muse, Pi and Antigravity, on the subscriptions you already have.
Your knowledge and skills
Company knowledge from Brain and shared skills, available in every workspace.
Your tools
MCP tools, Slack, Gmail and Google apps, connected once and used from chat.
Other agents
Reach agents on the AgentBridge network and the coding agents running on people's own computers.
Your other AI apps
Use what you build from ChatGPT, Claude and Cursor over MCP.
Work together
Run a project in one workspace: add co-owners who each work in their own chat, let others use what you built, or hand work to a colleague.
Contractors and freelancers
Give them a workspace. Keep the work.
Start with your company’s context
The contractor starts with your knowledge, skills and tools already connected.
The work stays with you
Files and chats live on your server, not on a personal laptop or account.
No logins to hand out
They use the company's plans without ever seeing the login. They see only what you share with them.
Ends when you say
Disable the account and access stops at once. Cost is tracked per person.
Start here
One workspace, many jobs.
Research and documents
Compare supplier proposals against your requirements, prepare a customer brief or organize a set of documents.
Software helper
Ask your coding agent to investigate a bug, change the code and run the relevant checks.
Personal assistant
Plan the week, prepare a daily briefing and follow up on tasks.
Team expert
One job for your team, such as invoices or support questions, using your instructions and files.
Automation
Repeatable work on a schedule, an event or a webhook, with skills and reusable functions.
Company knowledge
Find answers in your company Brain and suggest how to improve it.
Chief of Staff
Coordinate your Crews and workflows, follow up on blockers and prepare status summaries.
Build it in Studio. Share it as a Crew so anyone on your team can ask it.
Use cases
Engineering work has a home here too. Illustrative examples.
-
Work from your phone
WhatsAppcheckout-service
Did the retry change pass the tests?
Yes, all 48 pass. Want a summary?
-
Share one plan
RioAva's shared Claude Max
Fix the flaky webhook test.
Fixed. It ran on Ava's plan, and she can see it was you.
-
See where spend went
AdminUsage
Who used the most this week?
Rio, on checkout-service, through Ava's account.
-
Review the week
Manager's ClaudeReview
What did the team ship this week?
Review over MCP · every view recorded
Checkout retries, a CSV export and two bug fixes.
-
Check a plan's limit
Account ownerAccounts
How much of my plan is left?
Live usage check from the coding CLI
38% of this week's limit used.
-
Use your Crews
Your workspaceDevOps Crew
Is staging healthy before I deploy?
Yes. All checks are green.
Private until you add co-ownersAdmins and assigned reviewers can review, every view recordedEvery command sandboxedCost per person, workspace and plan
checkout-servicePrivate · Claude Code
Add retries to the payment webhook handler, then run the tests.
Ran npm test in the sandbox · 2 failures, fixed, re-ran
Done Retries with backoff on 5xx and timeouts, capped at 3. All 48 tests pass. The change is in webhook.ts and its test file.
Who can see this workspacePrivate until you add co-owners
Connections
Connect your own tools. They stay yours.
Your own MCP servers
Sign in to GitHub, Slack, Google Workspace and more with your own account. Only your chats can use them.
Personal secrets
Stored encrypted, visible only to you, used only in your chats.
Antigravity
FAQ
Studio, answered.
Which coding plans can we bring?
Claude Code, Codex, Cursor, Muse, Pi and Antigravity. Connect an account by browser login (Claude Code, Codex, Cursor, Muse) or by API key. The login stays on the server.
Who pays when someone uses a shared account?
The account's owner. Runs on a shared account act as that owner and use their plan, and the owner can see who used it and where.
Can we see how much of a plan is left?
Yes. Each account has a live usage check that reads the coding CLI's own usage or status, so you see the limit the vendor reports.
Can someone using my shared account see my login?
Not through the app, and runs can't reach it either: every coding run is confined to its own workspace and files, so it cannot read another account's login files on the server. Still, share an account only with people and Crews you trust.
Is there a terminal?
No. There is no standalone terminal or shell. You ask the agent, and it runs the commands for you, each one in its own sandbox.
What can my team audit when using Claude Code?
In AgentWorks Studio, admins and assigned reviewers can read a person's chats, files and costs without changing them; every review view is recorded. The company can review cost, usage and output centrally. This describes review of the AgentWorks workspace, not a promise of a complete event log from the native coding CLI.
Who can see my workspace?
Only you, until you add co-owners. A workspace starts private; the owner can add co-owners to work on it together, and anyone else uses what you share from it, such as a Crew. Admins and anyone an admin names as a reviewer can also read its chats, files and costs without changing anything, and every view is recorded. The workspace tells you this in its settings.
How is it isolated?
Every command the agent runs is sandboxed with Linux Landlock and gets its own private /tmp, and the agent's own files are protected. The sandbox covers commands. Some coding agents' built-in read tools aren't sandboxed yet, so treat a workspace as private to people, not sealed off from the server.
Can other people or agents use my workspace?
People you add as co-owners can work in it with you, each in their own chat. Other people use what you share from it, such as a Crew, through its dashboard or from their own AI apps. Your workspace can call your own Crews and workflows.
Give your team AI they can work with. In the context of your company.
We connect your company’s AI plans, knowledge and tools, then open the first employee workspaces with your team.