Give each bot a job.
Create bots for the work you return to. Keep the brief, files and conversation together instead of starting from scratch each time.
Give your bots a brief, the tools they need and a computer to work on. Follow their progress, steer the details and review what comes back.
Sign in to check your account’s access and get started.
Checking Windows download availability…
Your model providers. Windows and web.
Sign in to check your account’s access.
Watch a task unfold, or choose another bot. This interactive demo uses fictional tasks and never connects to your accounts.
Research has sources to check. A reply has context to read. A fix has files to change. Give a bot the whole task and keep the conversation alongside the work.
Create bots for the work you return to. Keep the brief, files and conversation together instead of starting from scratch each time.
Follow browser and computer work from the bot’s screen. Ask what changed, add context or redirect the next step.
Open the draft, inspect the change or read the research. A task ends with something you can check and a decision you still own.
Connect the inbox, repository or workspace the job depends on. Manage connectors from Windows or the web. The account’s computer keeps the shared configuration.
Provider availability and authorization requirements vary. The preview shows examples, not a live connection.
Gmail
Find threads and prepare a reply.
Choose a category, then explore an example connection.
Connect Sphere Bot to another app that supports remote MCP. Send a brief to one of your bots, follow its progress and return to Sphere to review the work.
Choose read access or permission to send tasks. Your account’s routing and usage limits still apply. Disconnect the app whenever you want.
Connect with MCP“Ask my research bot to compare these options.”
Sphere Bot
Work runs on your Sphere cloud computer
You approve the connection. Questions and approvals stay in Sphere Bot.
Becky · Research
Check our saved sources. Note what changed. Leave a short brief with links and the questions worth following up.
Routine enabled
Example schedule: weekdays at 08:30.
A morning brief. A weekly check. A reminder to follow up. Give the routine a task and schedule, then come back to the work in the same bot conversation.
Adjust the schedule or pause it when priorities change. Available computer time and account access still apply.
Set the shared model providers and computer defaults. Decide where members can choose their own setup. Allocate model tokens and computer time, and see usage against each member’s allowance.
Use Sphere’s cloud computer, a permitted shared E2B key or a desktop Docker computer. Personal Codex access belongs to the member’s desktop login and needs owner permission.
Research
Example allocation: 1.0M tokens · 10h computer. Illustrative values.
Model routing
The member follows the owner’s shared provider settings.
Keep the providers you know. Try another model when the task calls for it. Set up your own routing, or share your team's choices with the people doing the work.
Choose your providersConnect directly with your API keys
GPT models
Claude models
Gemini models
Grok models
Hosted open models
DeepSeek models
Mistral models
Use direct provider keys, OpenRouter or your own endpoint. Choose a model for the main conversation and another for supporting work. Your bots and files stay together.
Open your bots in a browser or the Windows app. The account’s cloud computer and connectors belong to the same workspace.
Cloud Agents can take repository work into a separate computer and return a change for review. Connect GitHub and use the access your account permits.
Save separate provider keys in your dashboard. Available models and capabilities vary by provider. Personal Codex uses a login picked up by the Windows app. Local computer options need that desktop connection. API provider routing can be configured from the web.
Sign in to check trial access for your account. Paid plans are being prepared. Prices and usage allowances will be announced before subscriptions open.
Planned subscription
A place to start handing work over.
Pricing to be announced
Planned subscription
More ways to run the work.
Pricing to be announced
Planned subscription
Shared defaults. Clear permissions.
Pricing to be announced
| Compare the plans | Starter | Plus | Teams / Business |
|---|---|---|---|
| Sphere cloud computer | Included | Included | Available |
| Model routing | Your providers | Your providers | Owner defaults & member permissions |
| Docker or equivalent computer | Not included | Desktop required | Owner controlled · desktop required |
| Video generation | Not included | Included | To be announced |
| Transcription | Not included | Included | To be announced |
| Future voice feature | Not included | Included when available | To be announced |
| Shared routing & member controls | Not included | Not included | Included |
| Additional team member slots | — | — | One free · further seats priced later |
Using your own E2B key requires explicit account permission. Team owners can choose a permitted shared key or Sphere’s cloud service. Personal overrides require permission too.
One additional team member slot is free. Further seats will have a subscription charge when billing launches. Team media entitlements have not been announced. Future voice is not available yet.
Create an account with your name, email and password, or use Google. Configure model routing in your dashboard, then open the web app or sign in to Sphere Bot for Windows.
Yes. The web app can use the Sphere cloud computer and your account’s connectors. Local Docker and personal Codex access require the Windows desktop app. Computer and routing permissions depend on your account or team.
Choose OpenAI, Anthropic, Google Gemini, xAI, Groq, DeepSeek or Mistral with your own API key. You can also use OpenRouter, a custom endpoint or personal Codex through the Windows app. Select providers and models in your dashboard. Team members use the owner’s defaults unless the owner permits an override. Sphere does not require one model provider.
The conversation records the work, and the computer preview shows its screen. Open a bot to inspect its progress, give feedback or change the task. Check the files and results before you rely on them.
The trial runs for seven days. At its end, we ask for feedback and sign you out unless your account has separately granted access. Paid subscriptions and prices have not launched.
Bring a brief. Connect the tools it needs. See what a bot can take off your list, then tell us what worked and what needs work.
Sign in to check your account’s access and get started.
Checking Windows download availability…