DearTech-OS for Codex
DearTech-OS connects to Codex through the Model Context Protocol. Codex agents that run autonomously on coding tasks can pull from your company graph: customer constraints, prior decisions, and product context that lives outside the codebase.
Last updated:
About Codex
What Codex is
Codex is OpenAI's autonomous coding agent. It supports MCP-based tool integrations, letting external context sources like DearTech-OS extend what the agent can reason over during a task.
MCP support
MCP support. DearTech-OS connects through Codex's MCP integration.
Setup
Connect DearTech-OS to Codex
Configuration takes a few minutes. The exact paths depend on your client version, but the shape of the setup is consistent.
Configure Codex MCP servers
In your Codex configuration, add DearTech-OS as an MCP server pointing to mcp.deartech.co with appropriate authentication.
Define the scope of access
Decide which DearTech-OS roles and graph areas the Codex agent should have access to. Typically a viewer or maintainer role scoped to the engineering and product context.
Run a Codex task
Start a Codex task. The agent can now query the graph during its run, pulling customer evidence, decisions, and constraints as needed.
Audit the trace
Codex tasks include traces showing what tools were called. Review which DearTech-OS queries the agent ran and what context shaped its decisions.
Use cases
What you can do with DearTech-OS in Codex
Customer-grounded code generation
Codex working on a feature for a specific ICP can pull customer evidence and constraints before generating code, reducing rework.
Decision-aware refactors
Codex agents reference prior architectural decisions and their reasoning before making structural changes.
Long-running autonomous tasks
Multi-step Codex tasks maintain access to fresh company context throughout the run, not just at task start.
Source-grounded PR descriptions
Codex generates PR descriptions linked to the company nodes (decisions, customers, product areas) the change affects.
FAQ
Common questions
How does Codex authenticate to DearTech-OS?
Codex authenticates as a service identity or as the user who started the task, depending on how you configure the integration. The role-based access on DearTech-OS controls what the agent can see and modify.
Can Codex modify the graph?
If the role of the signed-in identity allows it. Maintainers can ingest. Admins can crystallize. Most teams scope autonomous Codex agents to viewer or maintainer roles to keep the audit trail clean.
Does this work with the Codex CLI and the cloud agent?
MCP integration applies wherever Codex runs as long as the runtime has access to the DearTech-OS MCP server. Cloud-hosted runs need the server reachable from the agent's environment.
Other integrations
Connect DearTech-OS to your other AI tools
DearTech-OS is AI-tool-agnostic. The same knowledge graph serves whichever MCP-compatible client your team uses.
Want DearTech-OS in your Codex sessions?
In a 30-minute call, we'll map where your company knowledge is scattered today and identify the first DearTech-OS layer worth building.