Skip to main content
Once connected, an agent sees a set of tools covering projects, libraries, images, fonts, docs, and more. Tools respect the same permissions as the user whose token is used — an agent can only see and change what you can.
Some tool names say template — that’s the historical name for projects in Denada’s data model. The tools operate on your projects; the surrounding documentation the agent reads makes this clear.

​
Projects

​
Libraries

​
Images

generate_image only works when your team’s AI images setting is enabled. Teams that keep it off can still search and place existing assets.

​
Fonts

Hosted fonts are the same ones shown in the team’s Fonts area.

​
Docs

​
Checking its work

Agents typically pair these with render_template or render_library_preview to visually verify edits before declaring them done.

​
Everything else

​
The checkout and commit model

Editing projects and libraries works like lightweight version control:
  1. Checkout. checkout_template or checkout_library returns a short-lived download URL for a gzipped tarball containing the content as ordinary files — JSON for structure and parameters, HTML for blocks and the shell — plus a baseHash identifying the version checked out.
  2. Edit. The agent extracts the files in its workspace and edits them with its normal tools, changing only what needs to change.
  3. Commit. commit_template or commit_library uploads the whole directory back with the baseHash and a short message. The commit is all-or-nothing:
    • Success — the change is applied atomically and appears in the version history with the agent’s message.
    • Validation failure — nothing is applied; the agent gets a list of errors to fix before retrying.
    • Conflict — if the content changed since the checkout (say, a teammate edited it in the app), the commit is rejected. The agent checks out fresh, reapplies its changes, and retries — so nobody’s work gets silently overwritten.
Because every commit lands in the same version history as in-app edits, you can review and roll back agent changes just like any other — see version history.