The value is in the order of operations. An agent asked to diagram a project usually invents the structure; here it has to list the files and read them before it can draw, so the diagram describes what is on disk. The read boundary is worth setting deliberately, since the configured project root is what stops a glob from wandering up the filesystem.
A three-step pipeline for diagramming a project: list the files that match, read the ones that matter, then render the Mermaid the model writes into an image through Kroki. Local reads are confined to a configured project root, and GitHub repositories are read by URL and ref.
- Files listed from a local folder or a GitHub repository, narrowed by root and glob and optionally recursive
- File contents read from either source, up to a configurable character limit
- Mermaid text rendered through Kroki, returned as image content and saved to disk as a PNG
- Local reads confined to the configured project root, with the output directory and maximum file size configurable
A project root the server is allowed to read, and network access for the Kroki render and for any GitHub source. Reads outside the configured root are refused.