SophosAIA real workspace, not a prettier prompt box.
The assistant can work inside visible surfaces — browser, files, documents, and panels — instead of pretending everything fits in a text reply.
visible work surfaces, not magic claims
SophosAI Studio gives an AI agent a real place to work: files, browser panels, documents, small apps, and a protected Workspace Shell that keeps chat, status, snapshots, and rollback in reach. Ask for a panel, a workflow, or a different layout — the sandbox can change without losing the way back.
The product direction is a protected Workspace Shell around a mutable sandbox: chat stays reachable, files live in a workspace root, apps open as panels, and agent work is supposed to leave visible status behind.
Most tools give you one fixed interface and make you work around it. SophosAI starts with a stable shell, then lets the inner workspace become more useful as you ask for what you need: a file view, a meal planner, a dev run panel, a document editor, or something specific to your day.
The assistant can work inside visible surfaces — browser, files, documents, and panels — instead of pretending everything fits in a text reply.
If the workspace needs a checklist, fridge scanner, status board, or document tool, describe it. The sandbox is designed to take shape around the job.
Navigation, chat, status, snapshots, and rollback stay outside the messy part so experiments do not strand you.
Instead of hunting through settings, you ask for the workspace you need right now: a wider editor, a saved run log, a fridge-planning panel, a file drawer that stays open on mobile. The interface becomes less generic as you use it.
The assistant should be able to create small, useful tools inside the workspace — then show what changed, what checks ran, and where the result lives. The goal is visible work you can inspect, not a confident paragraph.
The shell — chat, rollback, status, and navigation — stays protected. The sandbox can be edited by the agent. Every meaningful change should be visible, checked, and recoverable before it becomes part of your workspace.
Panels and layouts can change while the protected shell stays available.
Describe the tool you need; SophosAI turns it into a visible workspace surface.
Changes should be reviewable, reversible, and tied to a visible run.
Workspace files and runtime live away from your personal machine.
Chat, status, and rollback stay reachable while the sandbox changes around them.
Start simply; advanced users can bring their own provider later.
The agent can work across visible workspace tools, not only chat history.
The long-term runtime should pause workspaces when they are not in use.
SophosAI is being built for the moment after the prompt — when an agent needs files, state, tools, visible progress, and a safe place to make changes.
Teams should see what the agent changed, what checks ran, and how to roll back. The workspace model puts that control in the product surface instead of hiding it in logs.
We are opening SophosAI in stages. Join the beta if you want to test the protected shell, mutable sandbox, and early workspace apps before they are public.
Request beta accessTell us what you would actually use a protected AI workspace for. We will use beta feedback to decide which apps, shell controls, and hosted Studio features ship first.