From specialized intelligence to connected execution across every work surface
Enterprise AI is becoming part of how modern teams understand, build, secure, and improve software. But the way people work has never been limited to a single screen.
An idea may begin on a phone between meetings. Research may happen in a browser. A production question may surface while reviewing an issue or reading documentation. The implementation itself may need to happen in Visual Studio Code, where the code, development tools, and project context already live.
Until now, those moments have often been disconnected. AI can answer a question on one surface, but the user must carry the context and the work back to another. Conversations become fragmented. Intent gets lost. Progress becomes difficult to follow. The user is left acting as the bridge between insight and execution.
Cortex Connect changes that experience.
Cortex Connect allows a user to begin with Cortex on mobile or in the browser and securely continue the work in a connected Visual Studio Code workspace. The request, progress, and outcome remain part of one coordinated Cortex experience, helping enterprise AI move beyond isolated conversations toward useful, governed action.
It is a natural next step in the evolution of the Cortex AI Model Ensemble and the planning capabilities introduced with Cortex Planner. The Ensemble brings together specialized intelligence. Cortex Router helps direct the request. Cortex Planner organizes the work. Cortex Connect closes the distance between those capabilities and the development workspace where the work can be completed.
Enterprise AI should not stop at the edge of the screen
Most enterprise AI experiences still assume that the place where a request begins is also the place where every part of the work must happen.
Real work is more fluid.
A developer may notice an issue while reading a report in a browser. An engineering leader may want a project update while away from a desk. A security professional may identify a concern on mobile and want it investigated in the connected development workspace. A team member may start a task in one environment and expect to see its current status in another.
The important question is not, “Which device owns the conversation?
The important question is, “Where can this work be completed with the right context, tools, permissions, and human control?”
Cortex Connect is designed around that question.
It gives users a consistent way to engage Cortex across mobile, browser, and Visual Studio Code while allowing development work to remain grounded in the connected workspace. The user can move between work surfaces without reducing a meaningful engineering task to a disconnected series of copy-and-paste interactions.
This is more than synchronized chat. It is continuity of intent, continuity of progress, and continuity of control.
The next chapter of the Cortex Ensemble
The Cortex Ensemble was built on a simple principle: enterprise AI should not ask one general-purpose model to perform every responsibility equally well.
Privacy awareness, prompt protection, security analysis, safety-aware decisions, broad coding assistance, validation, routing, and planning are different problems. They require different strengths, different context, and different levels of control. Cortex coordinates specialized capabilities so the right intelligence can contribute at the right point in the workflow.
Cortex Connect extends that principle from models to work surfaces.
Just as one model should not be responsible for every kind of reasoning, one interface should not be responsible for every moment of work. Mobile is ideal for access and responsiveness. The browser is ideal for research, enterprise context, and the many systems in which modern teams operate. Visual Studio Code is where developers can work directly with their project and development environment.
Cortex Connect brings those strengths together.
The user does not need to reconstruct the task each time they change devices. The Ensemble does not lose sight of the objective when the interaction moves between surfaces. The development workspace can remain the trusted place for workspace-aware execution, while mobile and browser become connected points of access, visibility, and control.
Two stages that create one connected experience
Cortex Connect brings together two foundational stages. Each solves a different enterprise problem. Together, they make cross-surface AI-assisted work feel dependable and coherent.
Stage 1: Durable workflow continuity
The first stage establishes dependable continuity for longer-running and multi-step AI work.
Enterprise tasks do not always fit inside one short interaction. A meaningful request may involve understanding the objective, reviewing available context, organizing steps, waiting for user input, coordinating specialized capabilities, tracking progress, and validating the result. Users should be able to leave a screen or move to another Cortex experience without losing sight of that work.
Cortex Connect preserves workflow continuity across the user experience rather than treating each open window as an isolated interaction.
This enables Cortex to provide:
- A consistent view of workflow progress across connected work surfaces
- Reliable progress visibility as work moves through meaningful stages
- Continuity when a user changes devices, closes an interface, or returns later
- A clearer record of requests, progress, decisions, and outcomes
- A more dependable experience through ordinary interruptions
- A stronger foundation for approvals, review, and user-directed control
For the user, the benefit is simple: the work does not disappear because the screen changed.
A request started in the browser can remain visible when the user opens Cortex on mobile. Progress associated with a connected Visual Studio Code workspace can be reflected across the Cortex experience. A completed result can remain part of the same conversation rather than appearing as an isolated response in one place.
Continuity is more than a technical quality. It is a product promise. If enterprise teams are going to trust AI with more meaningful work, they need confidence that progress can be understood and that control will not be lost when normal interruptions occur.
Stage 1 provides that confidence.
Stage 2: Connected execution in Visual Studio Code
The second stage connects a Cortex request from mobile or browser to the user’s connected Visual Studio Code workspace.
This is where continuity becomes action.
A user can express an objective from the work surface that is most convenient. Cortex can interpret the request, apply the appropriate specialized capabilities, and organize the work. When the task requires project-aware action, Cortex Connect can carry that intent to the connected development workspace, where the relevant project context is available within user-controlled boundaries.
The workspace remains central. Cortex Connect does not ask users to duplicate their development environment somewhere else merely to continue a conversation. It allows the Cortex experience on browser and mobile to work with the connected Visual Studio Code environment already being used by the developer.
Consider a few examples:
- A developer identifies a documentation gap from a browser and asks Cortex to update the project documentation in the connected workspace.
- An engineering leader reviews a feature summary on mobile and asks Cortex to prepare a focused implementation in the active development project.
- A security professional discovers a concern while reviewing enterprise context and asks Cortex to investigate the relevant area of the connected codebase.
- A developer starts a change from another work surface, then returns to Visual Studio Code to review the result, inspect the project context, and continue working.
In each case, the user starts where the need appears and the work proceeds where the right development context exists.
That is the core of Cortex Connect: access anywhere, connected execution where the code lives, and one coordinated experience throughout.
Not screen sharing, but intent sharing
Cortex Connect is not about recreating a desktop interface on a smaller screen. It is not a remote-control metaphor built around clicking through another device.
It is a higher-level connection between user intent and a trusted workspace.
The user communicates the outcome they want. The Cortex Ensemble helps understand and organize the request. The connected workspace provides the project-aware environment in which permitted actions can occur. Progress and results return through Cortex so the user can remain informed across work surfaces.
This approach is important because enterprise AI should simplify work rather than make users operate complex development tools through an unsuitable interface. A phone should not need to pretend to be a desktop IDE. A browser should not need a full copy of the developer’s environment. Each surface should contribute what it does best while Cortex maintains continuity across them.
Human control remains part of the experience
Connected execution does not mean unchecked execution.
Cortex Connect is designed to preserve user control as work becomes more capable. Requests remain aligned with the connected workspace, available context, and permitted actions. When a workflow requires review or approval, that decision remains visible rather than being hidden inside an opaque automation.
This gives organizations a practical path toward more agentic AI-assisted development:
- Users can initiate work from more places without surrendering oversight
- Developers can keep workspace-aware execution grounded in their development environment
- Teams can follow progress and outcomes across the Cortex experience
- Review and approval can remain part of consequential workflows
- AI assistance can become more useful without becoming less accountable
The goal is not autonomy for its own sake. The goal is useful, dependable execution with people in control of the boundaries that matter.
One conversation across mobile, browser, and Visual Studio Code
Cortex has steadily expanded the idea of where Enterprise AI belongs.
- It belongs in Visual Studio Code, close to the code and development workflow.
- It belongs in the browser, where research, documentation, enterprise applications, and operational context shape decisions.
- It belongs on mobile, where users need access, awareness, and the ability to move work forward when they are away from their desks.
Cortex Connect turns those surfaces from separate destinations into parts of one experience.
A conversation can begin on one surface and continue on another. A request can originate away from the development environment while remaining connected to it. Progress can be visible without requiring the user to stay anchored to a single open interface. Results can return to the places where users naturally engage with Cortex. For individuals, this reduces friction. For teams, it improves continuity. For enterprises, it creates a stronger foundation for AI that can operate across the real shape of work while maintaining visibility and control.
From answers to outcomes
The evolution of Cortex reflects a broader shift in Enterprise AI. The first generation of AI assistants focused on producing answers. The next generation helped produce code. The Cortex Ensemble added specialized intelligence for the different responsibilities surrounding secure software delivery. Cortex Router helped understand where work should go. Cortex Planner added structure to what should happen next.
Cortex Connect carries that progression forward by linking coordinated intelligence with the work surface where an outcome can be completed.
This creates a more complete path:
A user expresses intent. Cortex understands the request. The Ensemble contributes the right specialized intelligence. Cortex Planner organizes the work. Cortex Connect reaches the trusted development workspace. The user follows progress and remains in control across mobile, browser, and Visual Studio Code.
The result is not just a better answer. It is a more connected path from idea to action.
Enterprise AI for the way work actually happens
Enterprise work is distributed across devices, applications, teams, and moments of attention. AI must adapt to that reality.
Users should not have to remember where a conversation started. They should not have to manually transport context between a browser, a phone, and an IDE. They should not lose visibility because they stepped away from a desk. And they should not have to choose between convenient access and a development environment grounded in the real project.
Cortex Connect is designed to remove those compromises.
It combines durable workflow continuity with connected, workspace-aware execution. It brings the Cortex Ensemble closer to the moments when users need it. And it strengthens the broader Cortex vision of an Enterprise AI Control Layer that is available across work surfaces, specialized where precision matters, dependable over time, and governed when action matters.
Cortex Connect is the next step toward Enterprise AI that moves with the user, stays connected to the work, and helps turn intent into trusted outcomes across mobile, browser, and Visual Studio Code.
