Dezin

Dezin is an early desktop-first design tool. A project is an infinite Canvas of typed Nodes—Pages, Components, Design Systems, Research, Tokens, Documents, Layouts, Knowledge, and imported media. Agents can plan the Canvas, generate one Node at a time, and rebuild selected immutable versions into an implementation project.

Project state, Canvas history, generated versions, assets, Agent threads, jobs, and exports stay on local disk. Dezin operates no servers: there is no hosted account, telemetry, or model router. Everything that leaves your machine is listed under [Network egress](#network-egress) and happens with credentials you supplied.

Current product contract

• Canvas-first projects. There is one primary Design Canvas workflow. The former Prototype/Standard mode selector, project variants, and Files/Versions workspace are not part of the current UI.
• Typed Nodes and immutable Versions. Generated HTML is published as immutable, checksum-bound Node Versions. Imported media is content-addressed. Canvas mutations use revision compare-and-swap, and undo/redo never rewrites published bytes.
• Main and Node Agents. The Main Agent can discuss a request, apply bounded Canvas commands, and dispatch scoped Node Jobs. A Node Agent can publish only its target Node. Ordinary conversation remains text and causes no Canvas mutation.
• Bring your own Agent. Dezin discovers installed provider CLIs and custom commands and exposes their available models. Claude and CodeBuddy receive the strongest tool/argument and execution-identity policy; every provider is still restricted to an exact daemon-owned pending working directory and a narrowed environment. Windows Design execution remains unavailable until its confinement can be proven.
• Local, explicit assets. Frozen context is byte-copied into eac