Two ways in: the dashboard for a guided flow, or your IDE over MCP for full control. Both write to the same governed brain.
Every agent has a governed brain: a scoped vault of approved workflows, rules, and escalation conditions. The agent acts only on what a human on your team approved.
You put knowledge into that brain two ways, and both land the same place: as proposed memory that governs nothing until you approve it.
Sign up, create an agent, and its brain is provisioned. From the dashboard you add memory, import a starter brain as JSON, and review what’s pending, all governed.
Agents include IDE access. Connect your coding agent to your brain over MCP and manage it from the tools you already use.
Through MCP you use the same memory tools the dashboard calls (add, propose, approve), writing to the same governed brain. Available on Developer and Team plans.
Seed a brain in bulk with a JSON file of workflows. Each workflow needs a name and use_when conditions (in the vocabulary real tickets use) so the agent can match against it.
Imported memory lands as proposed: it governs nothing until you approve it in the dashboard.
Whether knowledge enters through the dashboard or MCP, the rule holds: the agent proposes, a human approves, and only then does it govern. Rejected memory never governs anything, and every decision is audited.
Read the governance model →Programmatic access to run classification and execution against your agent is rolling out with early access.
The agent execution API is in early access. Request access and we’ll onboard you directly.
For the memory layer beneath conxtagents, the full API is documented on conxt.dev.
conxt.dev memory docs →