Cortex Cloud

Managed cloud execution for secure, durable, project-aware AI work.

Connected Workflows

Choose Where AI Work Runs

Cortex Cloud gives eligible AI work a managed place to continue. Start from the Cortex experience, choose Local or Cortex Cloud, and keep the project state, execution boundary, progress, and result connected from request through review.

Explore CORTEX CLOUD

Local or Cloud

Choose the execution destination that fits the work. Keep eligible work Local when the connected environment is right, or use Cortex Cloud for managed remote execution.

Project-aware Handoff

Ground managed work in a defined project
state, so teams can understand what source revision and workflow context the cloud execution used.

Durable Workflow State

Keep progress, completion, cancellation, and attention states connected even when a browser refreshes, a device sleeps, or the user changes surfaces.

Cortex Cloud Highlights

Product Features

2

Execution Modes – Local, Cloud

4

Invoke from Discover, browsers, IDEs, mobile

3

Works with three Routers

1

Connected Workflow using Cortex Connect

Managed Cloud Execution

Cortex Cloud gives eligible engineering work a dedicated managed environment, allowing tasks to continue remotely while staying connected to the user, project and original workflow.

Local or Cloud: Choose whether eligible work runs in the connected development environment or through Cortex Cloud.

Project Aware: Cloud workflows are grounded in a stable committed project revision for clearer review and repeatability.

Managed Workspaces: Cortex prepares an isolated execution environment associated with the authorized user, project and workflow.

Durable Execution: Work can continue beyond one open editor, browser session or device while preserving meaningful workflow state.

Remote Capacity: Use managed cloud resources without requiring users to configure or operate the underlying infrastructure.

Execution Placement: Cortex coordinates workspace and compute placement within organizational and availability boundaries.

Lifecycle Management: Keep execution, completion, cancellation and cleanup connected to the workflow that created them.

Cross Surface Continuity: Start eligible work from mobile, browser or Visual Studio Code and follow it through the same Cortex experience.

Progress Visibility: See whether cloud work is transferring, active, completed, interrupted or requires attention.

Device Independence: Continue following work even when the originating editor, browser or device is no longer active.

Browser Initiation: Start cloud workflows close to documentation, issue trackers, pull requests and other enterprise context.

VS Code Integration: Keep local development and review central while adding Cortex Cloud as another execution destination.

One Cortex Experience: Keep conversations, project relationships, execution choices and results coordinated across supported surfaces.List item

Connected Workflow

Extends Cortex Connect with durable cloud execution across mobile, browser and Visual Studio Code, keeping project context, progress and results connected as work moves across surfaces.

Controlled and Recoverable

A managed execution layer designed around explicit boundaries, authenticated ownership and durable state, helping enterprise engineering work remain understandable when devices, sessions or services change.

Execution Boundary: Cortex honors the Local or Cortex Cloud choice rather than silently moving work to another environment.

Enterprise Controls: Apply organizational policies, regional availability and capacity controls behind the Cortex product layer.

Revision Awareness: Keep remote work tied to the committed source state selected for cloud execution.

Ownership Controls: Associate workflows and managed workspaces with the correct authenticated user and project.

Clear Failure States: Distinguish preparation, availability, cancellation and execution failures instead of returning generic errors.

Recoverable Workflows: Restore durable progress after interruptions without requiring users to resubmit the original task.List item

Operational Visibility: Track workflow state, timestamps, outcomes and lifecycle events without making customer code the monitoring surface.List item