Figma, in the Covens That Need It

A coven already reads a client's brand where it lives: the repo, Google Drive, Notion. The designs were the gap. They sat in Figma, and the agent had to take my word for what the screens looked like, which nobody should rely on.

Figma is now a connected app. An agent can list a coven's Figma files, read their structure, look at a frame, and read or add comments, only in the files and projects that coven chose.

Available in AICoven 3.1.0, out next week.

---

Signing in, or a token

In Settings → Connected Apps, Figma is listed as "Files and projects you choose". Connect offers two ways in: Sign In with Figma and Use a Personal Access Token…. The app says what each reaches: "Signing in reaches the files a coven chooses. A personal access token also reaches its projects."

Sign In with Figma opens Figma's own sign-in in your browser, as the other apps do, and asks for what the agent tools use. AICoven renews the sign-in on its own. If Figma refuses it anyway, Settings shows Sign In Again.

Use a Personal Access Token… opens a sheet that says what to do: "Create a personal access token in Figma under Settings › Security." Below that, Give the token these scopes lists them, with file_comments:write only if agents may comment.

The sheet also says the token "works until the expiry you set there, and you can revoke it in Figma at any time. AICoven stores it encrypted and never shows it again." AICoven checks the token with Figma first, so a token Figma refuses is turned away and nothing is kept.

Why keep the token at all? Figma closes the endpoints that list a project's files to public OAuth apps. A signed-in AICoven can reach files one by one, never a project. A token you create yourself can. So a coven on a signed-in account says "Projects need a personal access token", with Use a Token Instead…, and any project it chose is listed as "Not reached while this account is signed in". A token from the same Figma account keeps every choice the coven made, and so does signing in over a token.

The token has a cost. Figma doesn't tell AICoven when a token expires, so AICoven finds out the first time Figma refuses it. Settings then shows Replace Token, which takes a new token from the same Figma account and keeps every coven's choices.

Each coven chooses its files

Figma grants an app everything you can see. So the coven names what it reaches.

Open the coven, then its Connections, and choose the Figma account. Paste a link into Paste a Figma file or project link, and the file or project joins the coven's Files or Projects, by its name in Figma. A project needs a token account; on a signed-in one, its link is turned away with "Projects need a personal access token." Each can be removed. A project shows "Includes files added to this folder later", and it means it: its files are read from Figma at every request, so a file moved out of it stops being reached too.

A coven with nothing chosen says so: "Nothing is chosen, so agents in" that coven "can't open any Figma file." That is the default, and the point. Your client's designs stay in your client's coven.

Every request an agent makes is checked against the coven's choice right before it is sent. Remove a file, or switch back to Read, and the next request already knows.

What agents can do

Under Agents can, a coven starts on Read: "agents can look in the files and projects chosen here but change nothing there." Five tools:

• List files: the chosen files, with their names, last edit, and version, and the files in each chosen project.
• Read a file: its pages, frames, and layers, or one node's subtree, up to four levels and 400 nodes at a time. When more was left out, the agent is told and can read deeper.
• Render a frame: up to three frames, rendered as images and shown to the model, so it describes the screen instead of guessing from layer names. A run renders at most twice.
• Read comments: open ones by default, newest first, up to 200, each with its author and where it sits on the canvas.
• Add a comment: a new comment or a reply, posted as your Figma account, then read back to confirm it landed.

The last one needs Read and make changes, and the app is plain about the trade: agents "post comments in those files as you, without asking first." There is no per-comment approval, as with Notion's comments, and the switch back to Read is in the same place.

In a shared coven, each member chooses their own Figma account, and an agent works as whoever's turn it is.

Where the frames show

Figma traffic goes through AICoven's API: the tools run there, with your stored token, on every route that runs AICoven's tool loop. That's BYOK cloud providers, the Mac local agent, and Hermes and OpenClaw in compatibility mode. Native Hermes and native OpenClaw Gateway runs bring their own tools and aren't offered these.

Rendering needs a route that sends images to the model as images: Anthropic, OpenAI and Codex, Google and Vertex, Mistral, and Azure deployments of OpenAI models. Elsewhere the agent is told images aren't supported, and the other four tools still work. A text-only model on one of those providers refuses the request with the image, and the turn fails. Honest, if not graceful.

Turning it off

Disconnect in Settings removes the account and its coven choices, and says what AICoven can't do for you. For a token: "AICoven deletes its copy of the token; revoke the token in Figma too." For a sign-in: "AICoven deletes its tokens; you can also remove AICoven from your connected apps in Figma's settings."

What it doesn't do (yet)

• A signed-in account doesn't reach projects. That takes a token, because Figma doesn't let apps you sign in to list a project's files.
• It doesn't edit the canvas. Figma's REST API can't change layers, so neither can AICoven.
• Not built yet: frames saved as a coven's assets, Figma mentions in On me, these tools in Workspace MCP, and Figma previews for saved links.
• Figma's rate limits apply. When Figma says to wait, the agent is told how long and doesn't retry in the turn.