Skip to content
cloudtifact

Your agent reads the feedback, fixes the doc and closes the thread.

Every command answers in a format an agent can use: compact tables, exact follow-up commands, and a record of what it did and for whom. This site reads the same way: add .md to any page outside the docs, or start from /llms.txt.

Comments as a table

Your agent pulls open comments as TOON, a table format that costs about half the tokens of JSON. Eight real comments came to 617 tokens as TOON and 1,250 as JSON.

$ cloudtifact comments --toon
space: "https://app.cloudtifact.com/s/itbnp1xzhi"
howToAnswer:
  reply: "cloudtifact reply <thread> \"<what you changed>\""
  resolve: cloudtifact resolve <thread>
comments[2]{id,thread,file,version,author,from,at,via,edited,status,quote,body}:
  k3x9,k3x9,launch-plan.md,1,maria,"Singapore, SG · 203.0.113.7","2026-09-27 15:40",null,null,open,QA runs Thursday.,Friday is tight. Can QA move up?
  p7w2,k3x9,launch-plan.md,1,sam,"Singapore, SG · 203.0.113.9","2026-09-27 15:53",claude-code,null,open,null,Moved QA to Wednesday.
Maria's comment and your agent's reply, one row each. The reply shares the comment's thread id, and the output opens with the exact commands to answer. Where a comment came from is shown to members only.

Signed for the person it acted for

An agent acts as you, so its comments, replies, resolves and edits are yours. Each one also names the agent. Editing keeps every earlier version, and nobody can edit a comment they didn't write.

$ cloudtifact edit p7w2 "Moved QA to Wednesday, launch stays Friday."
Edited p7w2 on launch-plan.md (version 2, via Claude Code).

$ cloudtifact history p7w2
v1  2026-09-27 15:53 UTC  @sam via Claude Code
    Moved QA to Wednesday.
v2  2026-09-27 16:06 UTC  @sam via Claude Code
    Moved QA to Wednesday, launch stays Friday.

Set it up once

cloudtifact init --hooks adds a hook to Claude Code, Cursor or Codex, so docs publish the moment the agent saves them. cloudtifact skill install teaches agents the rest: read comments before editing, reply and resolve after, and share the link when they publish a page.