added 2026-09-28
Comment on an issue (key) or on a page (project and page number) in Markdown. quote (exact description or page text) starts an inline thread anchored to it; reply_to (a comment id) replies. Threads nest at most 3 levels.
bodystringrequiredComment text in Markdown;  = sysdraw view link; a ```mermaid block is drawn as a diagramidempotency_keystringoptionalOptional, 1–128 visible ASCII characters (a UUIDv4 is fine). The same key and arguments within 24 h return the original result and create nothing; the same key with different arguments is rejected. The key is scoped to you and to this tool, and shared with the HTTP Idempotency-Key header.keystringoptionalIssue key (or project + page)pageintegeroptionalPage number in projectprojectstringoptionalProject key, with pagequotestringoptionalExact text from the description to anchor an inline thread toreply_tostringoptionalId of the comment to reply to
Returns
deletedbooleanoptionalReplay only: the comment created by the first call has since been deletedidstring (uuid)requiredThe comment id (reply_to of add_comment, edit_comment, delete_comment)keystringrequiredThe issue key as you sent itkindstringrequiredcomment, inline or replyreplayedbooleanoptionalTrue when the idempotency_key had been used before: no comment was added
- 2026-10-01 — Comment Markdown follows the same round-trip rules as descriptions: in a blockquote a line holding only is an empty paragraph, and spaces at the edges of bold/italic move outside the mark.
- 2026-10-03 — New optional idempotency_key argument: a retry with the same key and arguments within 24 h returns the original answer and adds no comment.
- 2026-10-06 — A sysdraw diagram can be embedded in a description or comment: write its view link as an image line,  (a bare link stays a link); get_issue_details shows it the same way. Only view links anyone can open are accepted; a comment, edit or signed-in-only link is refused with the reason, and a new diagram is saved only after sysdraw confirmed it (a person can add about 60 new links per 15 minutes; when sysdraw cannot be asked the call fails and can be retried). Diagrams already in the text are not checked again.
- 2026-10-09 — A Mermaid diagram can be written in a description or comment as a fenced code block: ```mermaid, the diagram source, ```. The web app draws it as a diagram (with a Show source toggle); the source stays in the text and get_issue_details gives it back unchanged. Not drawn (the source is shown instead): config directives (%%{init: ...}%% lines), front matter (a leading --- block), image shapes (img:), and diagrams over about 20 000 characters or 500 lines; one over about 8 000 characters or 150 lines (a mindmap: 80 lines) is drawn when the reader presses Draw.
- 2026-10-08 — Comments on pages: project and page (a number) instead of key, exactly one target; quote then matches the page body, and reply_to works too. The answer's key then reads "SPD page 4".
- 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
- 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.