The situation
The problem addressed, the context, the people involved and the known constraints.
Cortex connects the work you carry out in your AI tools. It preserves the trajectory of situations, decisions and their outcomes, then prepares the context useful for what comes next.
The model can change. The experience stays in your environment.
A history can be re-read. A file can be found again.
But resuming work requires something else: knowing what had been understood, why a decision was made, what has changed since and what remains to be resolved.
Cortex maintains that trajectory across your sessions and your tools.
The problem addressed, the context, the people involved and the known constraints.
What you believed true, what remained uncertain and what still had to be verified.
The conclusion retained, the elements supporting it and the options set aside.
What actually happened after the decision and what that experience allows to revisit.
At the next session, Cortex does not return the whole history. It prepares the material relevant to the present situation.
Cortex does not impose a new chat. It sits beneath the applications and terminals you already use.
→ freeze the contractor access scope
→ rollout in two waves
↩ resumed: SSO does not cover externals
Cortex beneath your applications · on your machine The Workspace defines the boundary of your environment: a company, a product, a client or an activity.
Inside it, Cortex first looks for continuity with existing Subjects. When a new trajectory appears, it can create one. When material is still missing, it waits rather than forcing a wrong classification.
Customisation remains possible. It is no longer required for it to work.
Codex may be the best tool for one step. Claude may suit the next. Another provider may replace them tomorrow. Cortex stays beneath these engines.
Work in the application or terminal you already know.
Continue with the trajectory, the decisions and the open points.
Your environment does not start over because the engine changed.
Cortex does not ask the model to own your experience. It prepares, for each situation, the part of past work that can genuinely serve now.
A RAG can retrieve a document or a passage close to a request.
Semantic search proposes candidates. It does not decide alone what comes back into context.
Information may have been correct six months ago and no longer be so today. An experience may be useful in one team and inapplicable in another. A conclusion may be reinforced, limited, challenged or revoked.
SSO covers contractor access.
revisedExternals remain outside the SSO scope.
A conclusion stays linked to the situations and evidence that produced it.
The former state is not confused with the current one.
A learning stays limited to the context in which it was established.
What is no longer valid can lose its influence without being erased.
Cortex preserves the history without automatically granting every old piece of information the right to influence the present.
A technical session is a constraint of the model. It is not necessarily the right unit for understanding your work.
Cortex connects the sessions that belong to a single trajectory.
Without manually rebuilding everything that had already been established.
You keep writing in Codex, Claude or compatible tools. Cortex operates beneath the surface.
You do not have to manage technical sessions, workers or the graph.
Cortex runs on your machine. Your Workspaces, Subjects, trajectories, decisions and persistent states stay stored locally.
Local storage is not presented as necessarily local inference. The boundary stays explicit.
The problems addressed, the steps crossed and the points still open.
The conclusions and the reasons that supported them.
What actually worked, failed or required a correction.
What can be mobilised, what must be verified and what must no longer influence the present.
The experience stays in Cortex, not in the provider used that day.
Accumulating conversations is not learning. Cortex is designed to connect a situation, a decision, an action and its outcome, so that this experience can change how a future situation is approached.
The goal is simple: after several months in your environment, an agent should no longer work exactly as on day one.
Install Cortex, choose your Workspace and connect the AI tools you already use. Start in one. Resume in the other. Cortex maintains the trajectory.
The beta opens progressively. Just leave your address to be notified when a new access wave becomes available.
We will let you know when a new wave of access to Cortex opens.