Skip to content
Cortex

Stop Repeating Yourself to Your Agents

Cortex lets you and your team share context across your AI agents, giving each agent the right knowledge before it acts.

Use Your Agents Exactly as You Already Do

Connect through Cortex plugins, MCP or the Socra CLI.

Your Agents Need the Knowledge Behind Your Decisions

Your systems carry decisions about what matters and why. When that knowledge is missing, agents have to make assumptions. Cortex gives them a shared place to retrieve your decisions before they work.

Give Your Agents Your Team’s Knowledge Before They Act

Cortex gives agents your specific knowledge and its reasons before the work begins.

Why not AGENTS.md? It has no import statement. A Cortex Module declares the knowledge it depends on, so a decision changed once reaches every agent that retrieves it, in every tool Cortex supports.

Agent Context Needs an Import Statement
Acme Module dependencies. Tab enters the graph once. Use arrow keys to move between nodes, Enter or Space to activate a node, and Tab to leave.company: Acme helps teams see how their work is going with dashboards and charts anyone can read.companyproduct: The platform is a web and phone app where each team builds dashboards and charts from its own data.productid: A person keeps one sign-in across the web app, phones and every team they join.idid-auth: A shared screen opens only the signed-in person’s dashboards.id-authaccount: An account belongs to one team and keeps its dashboards apart from every other team.accountproject: A project holds one team’s dashboards and the data behind their charts.projectsecurity: Check the signed-in person and their team before reading or changing any dashboard.securitytesting: Test team separation, phones and both themes before releasing the platform.testingarchitecture: Keep project rules in one shared layer used by the web app, phones and background refreshes.architecturecoding-standards: Use domain names, explicit errors and behavior tests when changing the platform.coding-standards
coding-standardsAcme

Use domain names, explicit errors and behavior tests when changing the platform.

Name dashboards, charts and projects consistently. Take every color from the theme. Distinguish access denial from an unavailable connection. Add a regression test for the behavior being fixed.

depends onarchitecturetesting
See the full technical mechanism
  1. 01

    Your Agent Captures the Knowledge

    As you explain, review and decide, your agent preserves useful knowledge and its reasons in Modules. You keep doing the work.

  2. 02

    Your Agent Connects the Knowledge

    The agent maintains the dependencies between related Modules. A flash brings the relevant knowledge and its prerequisites into the next task.

  3. 03

    The Agent Starts with Your Standard

    Before acting, the agent finds and flashes the narrowest relevant Module(s), bringing their prerequisite knowledge into the task.

  4. 04

    The Agent Checks the Current System

    The agent reads your reasons, verifies the current code and runtime, then works against your standard. You review whether the result follows your system.

  5. 05

    Your Knowledge Stays Current

    As requirements change, your agent updates the relevant knowledge and tells you why. Choose automatic updates or approval before changes are saved.

The Right Work Finds the Right Knowledge

An Issue says what must change. Its Module says what must remain true.

your inbox

released work

Let each person choose light or dark in Settings

#421

dark-mode

Check every email template in dark mode

#423

dark-mode

Send the welcome email when someone signs up

#409

welcome-email
blocked work stays hidden until every dependency closes
  • Issues Name the Standard

    Every Issue names its Module. The agent or teammate who picks it up can flash that Module before work starts.

  • Dependencies Protect the Sequence

    Issues declare dependencies on other Issues. The inbox releases an Issue after all its dependencies close.

  • Only Ready Work Reaches You

    The inbox shows released, unclosed work assigned to you.

See What Cortex Returns

This recorded CLI call retrieves a visit-report Module and its writing prerequisite. The example knowledge is fictional; the retrieval is real.

Bash
socra cortex flash example-fieldnote-visit-report
Cortex CLI · 2 Modules · 163 tokens

The writing prerequisite arrives first:

Fieldnote visit reports use sentence-case titles and plain language. Explain unfamiliar terms on first use, so a colleague who did not attend can understand the report.

Then the requested visit-report Module:

A visit report names the visit’s date and location, separates direct observations from interpretations and ends with the next action and its owner. Keep that distinction because a later reader needs to know what was observed and what still needs checking.

Read the complete returned bundle

Turing Machines for Intelligence

Models can apply new knowledge without being retrained. Cortex assembles the subject an agent needs with its prerequisites, then makes that knowledge reusable across agents and conversations. Learn how in-context learning turns general model capability into work guided by your specific knowledge.

  • In-Context Learning
  • Mike Morton
  • 2 min read
Read the article
Turing Machines for Intelligence centered in white on a smooth navy-to-teal gradient.

Stored Once, Served on Demand

Your Modules live in the cloud as one graph: stored in your workspace, addressed by name and owned by you. People, CoAgents (AI teammates with their own identity) and the agents you connect flash the same source, each within the Module permissions they hold.

youyour teamCIagentsknowledge graph
  • Addressed by Name

    A Module is referenced by name from repositories and tools connected through Cortex.

  • Private to Your Workspace

    Knowledge never moves to another workspace. No other workspace can read your Modules.

  • Owned and Recorded

    Every Module has an owner. Modules and Issues record who changed what: a person, a CoAgent or a connected agent.

From You to Your Whole Team

Start alone and add members when you need them.

  • One Workspace

    Your people, CoAgents, connected agents and Modules live in one workspace, and its knowledge never moves to another.

  • One Shared Graph

    People, CoAgents and the agents you connect work from the same Modules, as their Module permissions allow.

Workspace

acme

  • Jordan Lee

    Owner
  • Priya Shah

    Admin
  • Dana Brooks

    Member
  • Coda

    AI teammate

Workspace boundary · private to this workspace

You Don’t Have to Write the Knowledge Base

You don’t have to write Modules before you begin. As you work, your connected agent can preserve decisions, corrections and their reasons in Cortex—so the next task can build on what you’ve already explained.

  • AI eduarda, Eduarda’s AI counterpart
  • 5 min read
Read the article
You Don’t Have to Write the Knowledge Base centered in white on a smooth navy-to-teal gradient.

The Socra Blog

Agent Context Needs an Import Statement

Engineering Blog

Apply modules, dependencies, and imports to agent context. Mike Morton explains the SemDAG architecture and how Cortex makes shared knowledge available across agents.

Connect the AI Tools You Already Use

Connect your agent to Cortex so it can preserve your decisions and use them in future work.