{"slug": "vincent-0-7-0-the-control-plane-now-runs-its-own-development", "title": "Vincent 0.7.0: The control plane now runs its own development", "summary": "Vincent 0.7.0 has been released, marking a milestone where the project now uses its own workflows for all development tasks, from GitHub issues to release preparation. The release adds workflow input declarations, a workflow-authoring skill that prioritizes deterministic automation over AI agents, and expanded CLI capabilities for task management and integration. The project is MIT licensed and aims to be a local, inspectable, vendor-independent control plane for coding agents.", "body_md": "I just released **Vincent 0.7.0**, and this release marks an important milestone for the project:\n\n**Vincent now builds Vincent.**\n\nAll development on the project now goes through Vincent workflows — from creating an approved GitHub issue through planning, implementation, verification, human gates, merge, and release preparation.\n\nThe journey from 0.4.0 to 0.7.0 added quite a bit.\n\nWorkflows can declare their expected inputs, including:\n\nVincent also gained a workflow-authoring skill designed around a principle I care about quite a lot: **don't use an AI agent when deterministic automation can do the job better.**\n\nCommands and native control flow come first. Agents are used where reasoning is actually required.\n\nReal automation fails.\n\nSo Vincent now has mechanisms for continuing rather than throwing work away:\n\n`vincent doctor`\n\n0.7.0 significantly expands the CLI.\n\nTasks can now be started idempotently, created from GitHub issues, populated through JSON/stdin, queried through `vincent status`\n\n, limited with `max_cost_usd`\n\n, and integrated with notifications.\n\nLogs, transcripts, approvals, retries, repairs and task answers can all be handled without entering the TUI.\n\nThe TUI hasn't been neglected either — tasks now open into a dedicated workspace containing steps, attempts, metadata, output and file-grouped diffs.\n\nThis is the part I'm most excited about.\n\nMy own development workflow now uses Vincent itself:\n\n```\nGitHub issue\n    ↓\nplanning\n    ↓\nimplementation\n    ↓\ndocumentation\n    ↓\ncross-platform verification\n    ↓\nhuman gates\n    ↓\nmerge\n    ↓\nrelease audit\n```\n\nClaude Code, Codex or Cursor can provide the inference.\n\nVincent owns the durable workflow, state and verification around them.\n\nThat's the architecture I've been working toward: **a local, inspectable and vendor-independent control plane for coding agents.**\n\nVincent is also **MIT licensed again**.\n\nI wrote a deeper overview of everything that changed between 0.4.0 and 0.7.0 here:\n\n[https://blog.lezli01.is-a.dev/blog/vincent-0-7-release/](https://blog.lezli01.is-a.dev/blog/vincent-0-7-release/)\n\nFeedback and contributions are very welcome.", "url": "https://wpnews.pro/news/vincent-0-7-0-the-control-plane-now-runs-its-own-development", "canonical_source": "https://dev.to/lezli01/vincent-070-the-control-plane-now-runs-its-own-development-1m84", "published_at": "2026-08-30 09:24:37+00:00", "updated_at": "2026-08-30 09:52:35.886735+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Vincent", "Claude Code", "Codex", "Cursor"], "alternates": {"html": "https://wpnews.pro/news/vincent-0-7-0-the-control-plane-now-runs-its-own-development", "markdown": "https://wpnews.pro/news/vincent-0-7-0-the-control-plane-now-runs-its-own-development.md", "text": "https://wpnews.pro/news/vincent-0-7-0-the-control-plane-now-runs-its-own-development.txt", "jsonld": "https://wpnews.pro/news/vincent-0-7-0-the-control-plane-now-runs-its-own-development.jsonld"}}