ctx vs MDV

ctx is an Agentic Development Environment (ADE) that solves the proliferation problem every developer hitting multi-agent workflows faces: you want to run Claude Code on one task, Codex on another, and Cursor on a third — but you end up with three terminal windows, three context streams, and no unified way to review what any of them did. ctx provides one controlled surface for all of them, with containerized disk and network isolation, durable transcripts, and a merge queue system that keeps parallel worktrees from colliding. The security model is where ctx gets interesting for teams. Platform and security teams get a single controlled runtime instead of hoping developers are running agents responsibly. Agents operate with bounded autonomy rather than requiring constant approval — you set the disk and network controls upfront, then let them run. All tasks, sessions, diffs, and artifacts land in one review surface you can search and audit. Shown on Hacker News today and currently free with an open-source GitHub repository (github.com/ctxrs/ctx), ctx is positioning itself as the layer between developers and their AI agents — the place where you actually manage what the agents are doing rather than just talking to them one at a time. With 23 supported CLI agents including Claude Code, Codex, Hermes Agent, and Amp, it's already broad enough to be genuinely useful.

MDV (Markdown Data Views) is a markdown superset that extends standard .md files with embedded live data, interactive charts, and presentation-ready slides. The goal is a single document format that serves simultaneously as developer documentation, a live dashboard, and a shareable slide deck — without requiring a separate tool for each use case. MDV files can embed SQL queries, API calls, and data transforms directly in markdown, with results rendering as tables, charts, or visualizations on the fly. The syntax extends frontmatter conventions that markdown users already know, keeping the learning curve minimal. Output can be previewed in a local server, exported as HTML, or converted to a slide deck — the same source file serves all three outputs. MDV surfaced on Hacker News with 44 points and active discussion around the concept of "living documents" — reports and runbooks that stay current because their data sources are live queries rather than screenshots. For developer-heavy teams who live in their editors and resist adopting heavyweight BI tools, MDV offers a markdown-native alternative that slots into existing documentation workflows.