DGC v0.47.2 is out
Navigate
Install DGC
Editor VS Code · Cursor · VSCodium

Go deep. Keep the thread.

Send a specialist after one question and read its findings in full, without losing the conversation that asked. The work comes back as a change you can review, in the editor you were already in.

extension 0.32.1CLI v0.47.2 or newerprotocol v14 required
05 · The context stays together

Scripted product illustration · no live model or repository.

05 · The context stays together
01 Work surface

Tool calls that look like work.

Goals and changes recorded in this chat stay above the composer. Existing workspace changes have a separate review. Read concise final answers, expand tool details, copy highlighted code, and review native editor diffs. Model and reasoning controls follow your selected route. Type / or $ anywhere in a draft to choose commands and skills; attach MCP reference text to a chat or goal without losing your work.

FIG.3 · Editor surfaceActual extension · 0:31 · real timeVS Code · Cursor

Actual extension surface · deterministic protocol fixture · real disposable-file edit and unittest run · not a live model session · real time, no speed adjustment.

DGC · actual extension surface · 0:31

Actual extension surface · deterministic protocol fixture · real disposable-file edit and unittest run · not a live model session · real time, no speed adjustment.

02 Install matrix

Pick your editor and channel.

Install the DGC CLI first, then choose a one-click listing or the self-hosted VSIX with its published SHA-256 checksum.

EditorOne clickRegistrySelf-hosted
VS CodeOpen editorMarketplace ↗dgc.vsix · SHA-256
CursorOpen editorMarketplace ↗cursor --install-extension dgc.vsix
VSCodium—Open VSX ↗codium --install-extension dgc.vsix
03 Current release

0.32.1 speaks typed protocol v14.

Native DGC plans, permission decisions, tools, and images are correlated with the CLI backend instead of reconstructed from terminal text. Goal evidence, lifecycle controls and prompt acknowledgements stay typed across routes. Selected skills, saved drafts and shared plan/review workflows keep work moving between terminal and editor. Vendor CLIs retain ownership of their internal tools and permissions.