{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/diagramming.revise-diagram/",
    "json": "https://www.anchorterminal.com/niches/diagramming.revise-diagram/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/diagramming.revise-diagram/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/diagramming.revise-diagram/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 4 | 10 | 18 | 10 | 5 |\n\n## What counts as done\n\nThe same diagram, at the same path or document id, with only the requested elements changed, every other element and id kept, and an image re-exported, with comments read in place where they exist.\n\nHow agents ask for it: update the architecture diagram for the new service; address the comments on the diagram; rename this box everywhere; move the database into the private subnet\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **D2 (The Hack Foundation (Hack Club), fiscal sponsor of the D2 project)**: The diagram is a text file edited in place, so ids and untouched elements stay, and d2 re-renders the image; d2 fmt normalises the source.\n- **Kroki (Yuzu tech, a French software firm. No registered legal form found)**: The diagram stays as text in the repo, edited in place, and re-rendering the same source gives the new image; nothing in Kroki replaces content.\n- **PlantUML (No legal entity found. Copyright Arnaud Roques)**: The source is a text file edited in place and re-rendered; nothing else is replaced.\n- **Whimsical MCP (Whimsical, Inc.)**: edit adds, updates or deletes shapes, text and connectors on the same board, comment_read reads threads and comment_edit replies and resolves, and fetch returns a fresh PNG.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Diagrams.so API + MCP (RedHold LLC)**: import_diagram takes an existing draw.io file and edit_diagram changes it by id with versions and revert, then export_diagram re-exports. Edits are by natural-language instruction, so keeping every other element isn't guaranteed, and comments aren't read.\n- **draw.io + MCP (draw.io Ltd)**: list_pages, get_page and set_page read and change one page of a local .drawio file, keeping ids. Files in Google Drive, OneDrive or GitHub can't be edited, and the maintainers won't add it (acc-18).\n- **Eraser API + MCP (Eraser Labs, Inc.)**: get_diagram reads a diagram's code and manually_update_diagram replaces it in place, or update_diagram edits by instruction, then export_diagram re-exports. No comment tools are listed.\n- **ExcaliClaw (ExcaliClaw)**: update_design, arrange_elements and auto_layout edit a saved drawing by element id, versions keep the state before each agent change, and export re-renders. No comment tools are listed.\n- **Excalidraw (Excalidraw s.r.o.)**: edit_scene_content deletes, updates and adds by persisted id, and take_screenshot re-renders; PUT content replaces the whole scene. Comments exist for scenes but no MCP or API tool reads them (acc-24, open, on the MCP App).\n- **Lucid API + MCP (Lucid Software Inc.)**: Get and Update Mermaid Diagram read and replace one diagram's markup by id in the same document, threads and comments are listable, and export re-renders. Comments aren't shown tied to a shape, and update replaces the markup whole.\n- **Mermaid Chart MCP (Mermaid Chart Inc.)**: get_mermaid_chart_diagram and update_mermaid_chart_diagram rewrite a stored diagram by id; as Mermaid text, untouched lines stay. Comments on diagrams aren't exposed.\n- **Mumble (tiny space)**: update_node changes a node in place, ids never change, files serialise deterministically so an edit is a small diff, and get_canvas reads it back. Image re-export is only in the app, and the server can't be obtained without early access.\n- **Structurizr + MCP (Structurizr Limited)**: The DSL file is edited in place and server-update merges the server's layout into the new version. No comment access, and storage needs a self-hosted server.\n- **tldraw SDK + MCP (tldraw, Inc.)**: Passing the same canvasId to exec keeps editing one canvas with checkpoints stored by the server, but only inside an MCP Apps host, and acc-34 reports replay could break the canvas.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Mural MCP (Tactivos, Inc. (d/b/a Mural))**: The page says agents respond to changes on the canvas, but the tool list and update semantics are in a script-rendered help article that couldn't be read.\n\n- not this job: AI Diagram Maker MCP (AI Diagram Maker (Rajasekar Elango)): Every tool generates a new diagram; none edits an existing one by id.\n- not this job: Cloudviz API (SIA Cloudviz Solutions): Each call regenerates a fresh snapshot; it can't patch an existing diagram or read comments.\n\n## What stops agents finishing\n\n- tool only edits local files, so a cloud-stored diagram is duplicated\n- full-replace write drops elements left out\n\n## Around it\n\nBefore: code.diff. After: code.open-pr, docs.embed.\n\n## Where this comes from\n\nWeight 10 of 100 in Diagramming: 5 of 37 accounts (draw.io and Excalidraw issues)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/diagramming.revise-diagram.json, or the MCP tool get_use_case with id diagramming.revise-diagram. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Update an existing diagram after a change or a comment",
        "url": ""
      }
    ],
    "description": "Update an existing diagram after a change or a comment: 4 companies fully do it, 10 with a limit, 18 carry the tag. Every listing in Diagramming with the reason and a source.",
    "facts": null,
    "h1": "Update an existing diagram after a change or a comment",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/diagramming.revise-diagram/",
    "published": "",
    "section": "agents",
    "title": "Update an existing diagram after a change or a comment | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/diagramming.revise-diagram/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
