Why deliberate is underrated
The conversation about agentic coding tools in 2026 is dominated by capability metrics: tasks per hour, lines of code generated, PR throughput. Claude Code scores poorly on all of these relative to Codex. It does not run parallel tasks. It does not operate autonomously while the developer has coffee. It does not queue work overnight. It sits in the terminal and waits to be asked.
From a throughput perspective, this is a limitation. From a human oversight perspective, it is a design choice the HHI™ framework rewards. The per-command approval model is not friction. It is the human oversight mechanism working as intended. Every consequential action requires a deliberate yes from a human who understands what they are approving. That is the closest any current agentic coding tool comes to what EU AI Act Article 14 actually envisions.
The question is not whether Claude Code is more capable than Codex. It is whether the oversight posture it creates is more defensible, and whether that defensibility has value in the regulatory environment that enterprise AI teams are now operating in.
The CLAUDE.md governance opportunity
CLAUDE.md is Claude Code's primary mechanism for persistent team instructions. At most organisations it functions as a productivity tool, encoding preferences, style guides, and recurring patterns so developers do not repeat themselves. But CLAUDE.md has a more significant governance use that is largely untapped: it is the only native location in Claude Code where an organisation can encode its human oversight policy.
A CLAUDE.md that includes explicit escalation thresholds (always ask before modifying authentication logic), documented permission boundaries (never write to production databases without explicit confirmation), and correction records (previous attempts at X produced Y issue, require human review for this pattern) is doing governance work, not just productivity work. It is creating a documented oversight mechanism per use case, which is exactly what Article 14 and Article 26(2) require.
Most teams are not using CLAUDE.md this way. The gap is not a product gap. It is a governance awareness gap. And it is closeable with a half-day of deliberate work by anyone who has read the EU AI Act's human oversight obligations.
What the EU AI Act requires, and where Claude Code stands
EU AI Act Article 14 requires that high-risk AI systems include human oversight measures that enable natural persons to monitor, intervene, and override the system's outputs. Article 26(2) requires deployers to implement those measures. Article 26(6) requires six months of log retention.
Claude Code's per-command approval model satisfies the spirit of Article 14 more directly than any guardian-agent architecture currently on the market. A human natural person is making a deliberate decision before each consequential action. That is not a proxy for oversight. It is oversight.
The Article 26(6) log retention gap is real and requires deployer action. Git history provides timestamped, attributable records of every AI-authored change, but git is not a centralised audit log system. Enterprise teams need to instrument a log aggregation layer that captures session-level activity, command approvals, and CLAUDE.md governance decisions in an exportable, SIEM-compatible format. This is deployer-built infrastructure, not a platform feature.
The honest assessment: Claude Code is closer to Article 14 compliance by product design than any alternative currently assessed. It is further from Article 26(6) compliance by infrastructure than Codex Enterprise. The right choice for a regulated organisation depends on which article they are more exposed on, and which gap is cheaper to close.
The D6 ceiling and why it matters for 2027
Claude Code's D6 (Agentic Readiness) score of 50 reflects a product that handles current agentic complexity well: sequential task execution, per-command approval, explicit permission management. It is not yet designed for the multi-agent, long-horizon workflows that are already entering enterprise production environments.
The gap is specific. In a Claude Code session, the developer sees what Claude proposes and approves each action. In a multi-agent workflow where Claude Code is one agent among several, receiving instructions from an orchestrator and passing outputs to downstream agents, the per-command approval model breaks down. There is no mechanism for the human to see the orchestrator's plan before execution begins. There is no visibility into sub-agent activity. There is no checkpoint architecture for long-horizon tasks that span hours or days.
This is not a current failure. Most Claude Code users are not running multi-agent workflows today. It is a forward-looking gap. The NIST AI 600-1 agentic controls (AGT-021, AGT-012, AGT-017) provide the framework for what this architecture needs to look like. Teams selecting Claude Code for agentic work that will scale should be asking Anthropic's roadmap questions about multi-agent oversight before they are locked into a workflow that outgrows the product's current oversight model.
What moves the score from 50 to 65
Three changes would materially lift Claude Code's HHI™ from 50 toward 65 and above. None of them require a fundamental product change.
First, a centralised log aggregation layer. Git history is necessary but not sufficient for enterprise governance. A lightweight integration that captures session-level approval events, CLAUDE.md change history, and command execution records into an exportable JSON format would close the D5 gap. This is a deployer-built component, not a product request, and it can be built in a week by a team that knows what they need.
Second, a systematic CLAUDE.md correction pipeline. The current pattern has developers updating CLAUDE.md reactively when a recurring error becomes frustrating. A practice of weekly CLAUDE.md review, where teams audit recent correction patterns and encode them proactively, would close the D2 gap and create a self-improving oversight layer. The product supports this. Most teams are not doing it.
Third, an explicit trust calibration practice. Session-level permission grants, where developers batch-approve categories of commands, are the primary trust-drift mechanism in Claude Code deployments. A quarterly audit of granted permissions, with explicit decisions about which should be revoked or narrowed, is governance hygiene that takes two hours and materially reduces the D4 risk. No product feature required.