Datarim 2.0: One Workflow, More Than One Runtime

Datarim 2.0 changed where the framework could run without changing what the framework was for. The same task pipeline, quality gates, and project memory became available to both Claude Code and Codex CLI.

The practical change was larger than adding a second installer flag. Datarim introduced an AGENTS.md entry point for runtimes that use that convention, added runtime metadata to its skills, and rewrote imported workflow techniques so they described intent instead of depending on one vendor's tool names.

Shared behavior, explicit differences

Multi-runtime does not mean pretending every assistant exposes the same primitives. Claude Code can dispatch native subagents in ways that differ from Codex CLI. The framework keeps the shared contract in its skills and commands, then documents runtime-specific fallbacks where the underlying tools differ.

Fourteen development skills were absorbed into that model. Some could move nearly unchanged; others needed an intent-level rewrite. Test-driven development, systematic debugging, worktree isolation, code review, and verification became local Datarim contracts rather than references to an external skill namespace.

Installation became part of the contract

The installer gained explicit runtime switches, dry-run support, collision-safe backups, and a project-local mode. Existing Claude installations kept their symlink layout. Codex received its own runtime surface. Later releases added Cursor, but the 2.0 decision established the rule: one canonical repository, adapters at the edge.

That rule matters during review. If the Claude and Codex surfaces describe different safety boundaries, the framework has drifted even when both commands still execute. Datarim therefore tests the generated runtime surfaces as part of the product.

Start with the installation guide, then compare the supported runtimes on the Runtimes page.

Published retroactively from the release archive. Datarim 2.0 originally shipped on May 9, 2026.