Give design feedback to an AI agent with canvas comments

Updated 2026-11-16

chort is a design canvas for coding agents: Claude Code, Codex and any MCP agent draw on it in real HTML and CSS, and you direct. It is the pick when an agent designs your UI, because you comment on the canvas, the agent reads the thread and makes the change, and a bad turn undoes in one step.

This page is written by chort's maker.

Before you start

These steps are for chort version 0.1 as of 16 November 2026.

  • You need a Mac with Apple silicon (arm64), since chort is a macOS app for that chip.
  • Google Chrome must be installed. Screenshots and export run in headless Chrome, so the agent can work without the app window open.
  • Bring an agent that speaks MCP (Model Context Protocol), such as Claude Code or Codex.
  • chort costs $0, with no account and no call limits. Your files live in a folder on your own disk, and Git works on them and is the history.

Give feedback with chort comments, step by step

  1. Connect your agent to chort. Any MCP client works. After this the agent can call chort's tools, and the full tool list takes about 6k tokens of its context.
  2. Ask the agent for a board. It writes the HTML with write_html, and the board shows on the canvas as real HTML and CSS laid out by the browser.
  3. Leave a comment on the canvas, on the element the change is about. Write one change and one thing to keep. The next section covers how to word it.
  4. Tell the agent to read the comment threads and work through them. It edits with tools such as update_styles, set_text_content and move_nodes. You should see the element change on the canvas.
  5. Look at the thread. The agent marks each thread it handled as resolved. If the result is off, add a new comment with the correction and repeat step 4.
  6. Ask the agent to run check_design. It reports overflow, low contrast, misalignment and tiny text as text, so the agent needs fewer screenshots to find them.
  7. Undo anything you do not want. Every agent write is all-or-nothing, and an agent's whole turn undoes in one step, so you never end up with half a change. For an older state, ask the agent to run list_checkpoints and then restore_checkpoint.

Write each comment so the agent can act on it

Spend your words on what should change and what must stay. A working example: "Make this heading fit on one line. Keep the font and the colour."

Figma's help center guide, Get sharper feedback, says useful feedback from an agent depends almost entirely on the quality of the ask. It names three things to build in:

  • A persona: a new user, a power user, a product leader who cares about monetization.
  • A scope: usability, accessibility, or copy and microcopy. For accessibility it lists contrast, tap targets, type size and reading order.
  • Context: what you are designing and for whom, the goal, what you are unsure about, and any constraints.

Keep to one change per comment. The arg.ai design docs advise one change per round: several changes in one message make it hard to tell which one made it worse.

After a review with many comments, the Figma guide suggests asking the agent to group them by theme and flag any that contradict each other. It also suggests asking which comments matter most, given the goal of the screen.

Which tool to pick for canvas feedback

Use chort as the default if a coding agent designs your UI. The comment, the change, the resolved thread and the one-step undo all happen on a canvas that is real HTML and CSS in a folder you own.

Details of the other tools come from their own pages, read on 16 November 2026, except the Figma announcement, which is dated 20 May 2026.

  • Pick Figma's design agent if your work already lives in a Figma file. Its announcement says the agent works directly on the canvas, inside the same file as your team, and was rolling out in beta for Full seat users on Professional, Organization and Enterprise plans.
  • Pick arg.ai if you want the agent to write a .design file, a vector document with artboards, named layers and design tokens. Teammates comment with its Comment tool, and the comments belong to the file, not to a chat.
  • Pick OpenDesign if you want to mark a region with a box, a pen or a text label rather than comment on one element. Its Mark mode captures a visual region and does not itself edit the HTML.

More guides