The short answer
Jotzu is a shared review workspace for AI-generated HTML files. You publish the file, a reviewer comments on the exact text or point they mean, and you send the threads you choose to your own connected AI agent. The agent replies in the thread or returns a revision, and you look at the result. Nothing starts on its own: a mention alone sends no work.
The review in five steps
- Publish one HTML file, up to 10 MiB.
- A reviewer opens it and comments on a passage or marks a point. Replies keep each discussion together.
- You select the threads you want and explicitly send them to your agent. Comments are never added silently to a batch that was already sent.
- Your connected agent replies in those threads or returns a revision based on the current version.
- You review what came back and decide what happens next.
Illustrative only: a reviewer marks one paragraph as too long, you send that single thread, and your agent returns a shorter version. Any names, comments, or outcomes in an example like this are made up for explanation.
Who can leave a comment
A guest link is view-only. It shows one revision to someone without an account, and you can revoke it. A commenter must sign in with their own Jotzu account and join your organization, so the feedback comes from a real, identifiable member of the review rather than an anonymous visitor. Sharing and access are covered on the share an HTML file page.
Connect the AI client you already use
Jotzu exposes one remote MCP endpoint: https://app.jotzu.app/mcp, with user-authorized OAuth sign-in and consent. Any AI harness that supports the remote MCP connection and OAuth can connect to Jotzu. Each client does not need a separate integration or an individual test for that connection.
Codex, Claude Code, and Pi are owner-tested examples, not an exhaustive client list. What a client can do after connecting varies: background-work waiting, file handling, and how a sent batch is received depend on its capabilities. Connection details, permissions, and client limits are on the AI agent guide.
Review first, agent second
People initiate the feedback. Reviewers read the published revision and mark what they mean. You decide which threads to send to your own agent; an authorized agent can reply in those threads or return a revision. The result appears in the same document, alongside the feedback that prompted it.
Jotzu does not host the file as a website and does not run the model. When you only need a public link with no discussion, use a host. When the review needs comments pinned to exact places and a revision history that keeps them, bring the file to Jotzu. For the wider workflow, see how Jotzu works.