What you can do
Connect to devices
Organize hosts, attach multiple protocols, and authenticate through personal or organization-managed Key Chain entries.
Operate from one workspace
Keep terminals, remote desktops, browser sessions, files, diagrams, dashboards, and conversations in the same workbench.
Work with AI
Choose a response mode, attach exact context, review tool activity, and use approvals or Autopilot according to the task’s risk.
Coordinate in channels
Separate operational context by team and channel, then organize conversations on a searchable chat board.
Build dashboards and apps
Turn connector data and operational results into live dashboards or capability-gated generated apps.
Turn work into procedures
Capture a repeatable workflow with arguments, tool access, schedules, triggers, and an execution history.
Operate away from your desk
Pair an iPhone with the desktop app to continue chats, review activity, and answer approvals while Studio remains the execution bridge.
Administer the organization
Manage members, integration readiness, tool policy, credential mode, usage, billing, and feature access.
How an investigation flows
1
Identify the target
Add a host or select an existing host, channel, conversation, file, connector, or other Studio object.
2
Gather live evidence
Open the appropriate terminal, remote desktop, browser session, diagnostic tool, connector, file, or dashboard.
3
Choose the AI posture
Use Ask for read-only help, Planning to research before execution, Default for normal tool use, or Autopilot only for a deliberately bounded task.
4
Review the work
Follow tool activity, inspect proposed external effects, and approve or reject calls according to your trust posture and organization policy.
5
Keep the useful result
Save durable facts as memory, keep generated files and apps as artifacts, or promote a repeatable path into a procedure.
6
Share at the right scope
Keep work private or place it in the appropriate organization, team, or channel context. Never paste a secret when a Key Chain reference can be used.
Understand the trust boundaries
Studio can reach production systems, external integrations, a local browser, and—with permission—the desktop interface. Different surfaces have different approval and credential boundaries. Before granting broad access, review:- Security and privacy for operator guidance.
- Human in the loop for tool approvals and Autopilot.
- AI provider and data flow for model regions and what enters model context.
- Known limits and roadmap for boundaries that still require operational controls.
Get started
Install and sign in
Install the correct desktop build and prepare network and OS access.
Tour the workspace
Learn the sidebar, conversation surface, artifact area, activity stack, and shortcuts.
Add a host
Build inventory, attach a protocol, and choose a credential reference.
Configure AI
Set the model, context window, mode, approvals, and follow-up behavior.