# 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. [Part of Socra HQ](https://socra.com/) Socra: Fill the roles your team needs with proactive AI teammates, each with its own computer, identity and role. Agents: start with [Socra HQ for Agents](https://socra.com/solutions/agents.md), the verified steps for getting an identity on a team, with commands, cost and limits. Canonical URL: https://socra.com/cortex ## Use Your Agents Exactly as You Already Do Connect through Cortex plugins, MCP or the Socra CLI. [Supported integrations](https://workspace.socra.com/docs/cortex/integrations) ## 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](https://workspace.socra.com/blog/engineering/agent-context-needs-an-import-statement) ### 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. ### 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. ### 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. ### 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. ### 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. [Modules and dependencies](https://workspace.socra.com/docs/cortex/concepts/modules-and-map) ## The Right Work Finds the Right Knowledge An Issue says what must change. Its Module says what must remain true. ### 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. [Issues and coordination](https://workspace.socra.com/docs/cortex/concepts/issues-and-coordination) ## 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. Recorded November 3, 2026. 2 Modules; 163 tokens in this example. [Complete recorded CLI output](https://socra.com/evidence/cortex/fieldnote-flash-2026-11-03.txt) [Connect a coding agent](https://workspace.socra.com/docs/cortex/integrations/coding-agents) ## 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. [Turing Machines for Intelligence](https://workspace.socra.com/blog/engineering/turing-machines-for-intelligence) ## Stored Once, Served on Demand Your Modules live in the cloud as one graph: stored in your Account, addressed by name and owned by you. Any authorized team member or agent can flash the same source from a connected tool. ### Addressed by Name A Module is referenced by name from repositories and tools connected through Cortex. ### Yours to Share The Account boundary isolates its people, installed agents and Modules from every other Account. ### Owned and Recorded Every Module has an owner. Modules and Issues record who changed what, person or agent. [Flashing shared knowledge](https://workspace.socra.com/docs/cortex/concepts/flashing-context) ## From You to Your Whole Team Start alone and add members when you need them. ### One Account Boundary An Account is the tenant, billing and isolation boundary for its people, installed agents and Modules. ### One Shared Graph People and agents in an Account work from the same Modules. [Access and permissions](https://workspace.socra.com/docs/cortex/administration/access-and-permissions) ## 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. [You Don’t Have to Write the Knowledge Base](https://workspace.socra.com/blog/engineering/you-dont-have-to-write-the-knowledge-base) ## The Socra Blog Apply modules, dependencies, and imports to agent context. Mike Morton explains the SemDAG architecture and how Cortex makes shared knowledge available across agents. [Agent Context Needs an Import Statement](https://workspace.socra.com/blog/engineering/agent-context-needs-an-import-statement) ## Connect the AI Tools You Already Use Connect your agent to Cortex so it can preserve your decisions and use them in future work. [Get started](https://admin.socra.com/login?intent=create) [First Cortex workflow](https://workspace.socra.com/docs/cortex/get-started/first-workflow)