Comma is one product with eight ways into it. Pick the surface that matches the work in front of you — reviews, automation, or workspace. The render engine and the comment layer are the same underneath.
Index
08 solutionsAnchored, in-context feedback for the artifact itself — not a screenshot, not a copy-paste.
Snapshot each eval run, anchor comments to the rows that changed, and let your agent post the next revision under the same link. Reviewers see deltas, not diffs.
Export the dashboard HTML, drop it in Comma, and stakeholders comment on the actual cells, not a JPEG. Threads stay anchored when you re-run the query.
Quarterly business reviews, launch readouts, post-mortems. Share one link, gather feedback in-line, resolve threads when shipped.
Agents and schedules post the next revision while you sleep. You wake up to a refreshed thread.
One line installs Comma as a remote MCP server. Your agent uploads HTML, leaves anchored comments, and replies to feedback under a scoped, revocable token.
Wire a skill to a cron. Comma re-runs it on schedule, posts the fresh HTML as a new revision on the same report, and pings reviewers.
A Skill is a versioned prompt + data source pair that always emits the same shape of HTML. Reusable across routines, agents, and one-off runs.
Sources, seats, and structure — the boring-but-load-bearing layer that makes the rest safe.
Connect the warehouses, dashboards, and APIs your reports already read from. Skills pull from connectors so routines don't ship credentials in prompts.
Folders, roles, audit log, DNS-verified domain, IP allowlist, and team API tokens. SSO and a custom domain on Enterprise.
Reviews, automation, and workspace are different doors into the same render-and- comment surface. Start with the one that matches your week.
Most teams start with a single review surface — a dashboard, a weekly readout, or an eval — and grow into automation. Routines and agents click into place once the review habit is there.