Flexible layouts
Arrange frames with free, flex, grid, block, and inline layouts, plus Fixed, Hug, and Fill sizing.
What you can use locally, what needs more work,
and the possibilities we’re exploring next.
Implemented and exercised within the scope described.
A working foundation with important limits or validation still pending.
A parity direction. Not available, scheduled, or promised for a release.
42 directions
A precise canvas, with space for experimentation.
Arrange frames with free, flex, grid, block, and inline layouts, plus Fixed, Hug, and Fill sizing.
Style typography and individual text ranges inside a layer.
Build gradients, image/custom masks, and advanced mask treatments. On-canvas mask handles and editable mask stops remain gaps.
Use independently authored WebGL presets, including a 13-preset family with expanded parameters. Shader fills can sit beneath layer content and export with it; picker previews remain static.
Resize proportionally and control stacking, opacity, and clipping. Flip layers horizontally or vertically and rotate them in 90° steps.
Position layers with smart guides, equal-gap snapping, alignment, and distance indicators.
Create color, dimension, number, font-family, and font-weight variables with bindings and CSS export. Folder-aware MCP tools support typed variables; direct agent edits to bound properties can still be reset by binding sync.
Drag layers to reorder them or move them into and out of frames, including multiple selections. Locked layers are respected and each move is one undo step.
Pick colors with alpha, HEX, RGB, HSL, or OKLCH controls and an eyedropper. Choose installed or Fontsource fonts, then export artwork at 0.5×–4× or as PDF through a native save dialog.
REST import, clipboard paste, .fig decoding, and encrypted PKCE OAuth are implemented against local fixtures. Real Figma credentials and clipboard payloads remain unverified; encrypted .pen files are deliberately refused.
Generate agent-authored SVG, connect configurable image providers, and trace bitmaps into smooth Bézier paths. Provider APIs have fixture coverage but no live-credential validation; harness asset generation does not invoke image models.
Direct manipulation of vector points and Bézier handles is not currently available.
Move between the canvas, your files, and a running app.
Search project text with ripgrep, import template packs, reuse shared components, and move files while preserving workspace history. Public discovery and arbitrary live code components are separate future directions.
Switch from the canvas to a full-window Code workspace with repository chats, All/Changed file trees, a file editor, project memory, and a dev-server preview. The active project follows the selected chat.
Inspect file diffs, confirm discards, commit changes, and push without force from the Changes panel. Local Git workflows are tested; GitHub pull-request creation uses a test stub and is not live-verified.
Import HTML and JSX with external stylesheets, cascade, and CSS variables. Supported document round trips have schema coverage. Scripts are not executed; pseudo-elements, floats, relative offsets, and some backgrounds produce warnings.
Capture supported remote pages or local apps, select a region, and retain embedded fonts, images, and source mapping. Shadow DOM, iframes, pseudo-elements, keyframes, and off-viewport content are not captured; interaction states remain metadata.
Detect and start npm, pnpm, Yarn, Bun, or plain HTML projects. Navigate, stage text edits, capture elements, and open an expanded preview tab. Responsive presets and setup/error/paused states are exercised; the embedded terminal is read-only.
New chats in repositories with a commit get their own Git worktree and Verynize branch. Older chats and repositories without a commit can use the project root. Files, diffs, previews, and the agent follow the active chat.
Authored canvas icons and icon tools are available. A complete library for organizing, swapping, and reusing icon collections is not established.
Using arbitrary application components directly as live canvas elements is a future direction.
Connect agents and people while keeping control of your work.
Cloudflare, VPS/Docker with Node and SQLite, and Vercel with Redis/libSQL adapters share backend scenarios. Deployment paths are implemented; production infrastructure remains unverified. Self-hosting has no Verynize license fee.
A session-authenticated hosted MCP endpoint reads and edits account rooms without an editor open. Its 31-tool subset is locally tested, with role checks; OAuth, desktop tools, and production deployment are not available.
Room images are deduplicated and uploaded through signed URLs, with raster-export embedding. Tested with local R2 emulation, not a real bucket; image URLs are not revoked with membership changes and SVG/MCP image embedding has gaps.
Previously opened rooms can be edited offline and replay unacknowledged operations after reconnect or restart. Desktop flows are exercised; the shared web implementation has only been exercised in Electron, and images may depend on cache.
Email sign-in, verification/reset, workspace creation, invitations, and roles connect desktop and cloud files. Local D1/workerd tests cover the flows; real email, live D1, production sign-in, and device passkeys remain unverified.
Composer indicators show design files, runtime tool status, provider limits, context, and generated-layer activity without an AI-layer quota. Claude live tool status and detailed context categories have unit-test coverage only.
Saved preferences accompany each chat, with limits shown in Settings. Claude uses per-call approval; Codex write gating in allowed access modes relies on persona instructions and has not been live-verified.
Choose from 31 named style guides and twelve styled starter briefs. The harness includes 12 design skills and structured fundamentals; checks cover contracts, contrast, and fonts, not a judged guarantee of design quality.
Both integrated runtimes passed a real smoke-test turn. Named provider accounts, tool permissions, and per-chat autonomy controls are implemented; real browser sign-in and account plan limits remain unverified.
The current catalog contains 55 MCP tools, including 16 desktop-only shell tools. Design tools edit the live canvas with undo or saved documents headlessly; screenshots and desktop shell actions require the running app.
Sixteen desktop-only tools cover preview setup, dev servers, interaction and capture, terminal commands, and editor actions. Execution follows approval/access controls. Codex main threads still require approval, and a preview-click test is known to be flaky.
Rewind can fork a provider session at a kept turn, with a transcript fallback. A second opinion sends the latest answer and diff to the other provider read-only. Neither flow has been run live from inside the app.
Shared rooms support presence, server-sequenced operations, reconnect, and collaborator-safe undo. Local clients exercise these flows; merging is not peer-to-peer CRDT, and production infrastructure is unverified.
Build and publish static apps with version history, rollback, and unpublish. Locally exercised apps run sandboxed without cookies or localStorage; a separate apps domain and production publishing remain unverified.
Agents continuing remotely after your computer goes offline are a future direction, not an available service.
Public profile pages can list published designs and static apps. Account/profile flows are tested locally; production sign-in and real email delivery remain unverified.
Keep room files private or publish frozen snapshots with access checks and revocation. Signed-in cloud files reopen connected and belong to workspaces; the service has not been deployed to production.
Owner, editor, commenter, and viewer roles, invitations, token rotation, and recovery are implemented. Organization role changes reach live rooms in local tests; production identity flows remain unverified.
Room comments and live feedback updates are implemented and covered by local desktop/cloud tests. Production collaboration has not been validated.
File, page, layer, and global project text search are implemented. Finding designs through natural-language meaning remains a future direction.
A local template gallery accepts JSON/ZIP packs and a shared component library supports reuse. A public creator marketplace remains a future direction.
Any future paid offerings are limited to optional cloud and AI services. Self-hosting stays free of Verynize license fees; your infrastructure and AI providers may charge for usage.
Start with your next idea