New Bring your own storage. Keep your diagrams in your own private GitHub repository, on Pro and Team.Bring your own storage on GitHub, for Pro and Team. Learn more about bring your own storage

examples

Worked examples of agents creating and editing diagrams, each with its scene, operations, revision diff, and rendered output. New here? Start with the Quickstart

Family
API dependency map from OpenAPI specs preview
architecture

API dependency map from OpenAPI specs

Build a diagram of which services expose, consume, and depend on which APIs from OpenAPI specs and SDK imports, then patch it with typed operations instead of redrawing it.

Source: OpenAPI specs / SDK imports
AWS architecture diagram from Terraform preview
architecture

AWS architecture diagram from Terraform

Let an agent draw a team's AWS architecture from its Terraform, as AWS reference diagrams draw it, and record each infrastructure pull request as a revision reviewers see before terraform apply.

Source: Terraform configuration / infrastructure pull requests
Deploy pipeline flowchart from a GitHub Actions workflow preview
flowchart

Deploy pipeline flowchart from a GitHub Actions workflow

A flowchart of how a push reaches production, drawn from the repository's GitHub Actions workflow: jobs as steps, checks as decisions with yes and no exits, and the outcomes. When the workflow changes, the agent records the change as a revision with a structural diff.

Source: GitHub Actions workflow (YAML)
ER diagram from database migrations preview
entityRelationship

ER diagram from database migrations

Build a database schema diagram from migration files (Prisma, Drizzle, Alembic) and apply each new migration as incremental Zindex operations, with a revision diff for every change.

Source: Database migrations (Prisma / Drizzle / Alembic)
Google Cloud architecture diagram from Terraform preview
architecture

Google Cloud architecture diagram from Terraform

Let an agent draw a team's Google Cloud architecture from its Terraform, as Google's reference diagrams draw it, and record each infrastructure pull request as a revision reviewers see before terraform apply.

Source: Terraform configuration / infrastructure pull requests
Layered architecture diagram from a codebase preview
architecture

Layered architecture diagram from a codebase

Let an agent draw a codebase's layers as a stack of rows from its package manifests. It lists each layer and its cards and writes no coordinates. The engine stacks the layers in the order listed, orders each row and runs the lines between them, those that skip a layer included.

Source: Package manifests / architecture layer map
Living architecture diagram from a repository scan preview
architecture

Living architecture diagram from a repository scan

Let an agent scan a repository and build a frame-grouped service architecture diagram: services, databases, queues, and external systems with edge labels. Later scans patch the same scene with typed operations.

Source: Codebase / configuration files
Multi-agent workflow diagram preview
workflow

Multi-agent workflow diagram

Visualize how multiple agents, tools, queues, and human review steps interact in an automated workflow. BPMN-style with start/end events, gateways, and intermediate signals.

Source: Agent configuration / orchestration runtime
PII data-flow diagram with dated history preview
architecture

PII data-flow diagram with dated history

Generate and maintain data-flow diagrams that show where sensitive data moves, what each system stores, and how the architecture changed over time. Every revision is kept with its date and message.

Source: Compliance inventory / data catalog / codebase classification
Public-facing interfaces diagram from Terraform, gateway routes and ingress preview
architecture

Public-facing interfaces diagram from Terraform, gateway routes and ingress

An agent reads a store's Terraform, gateway routes, service specs and ingress files. It saves an architecture diagram of what they open to the internet: who calls in, what each path reaches and how it's authenticated. Asked again after a change, it updates the same diagram.

Source: Terraform, gateway routes, OpenAPI specs and Kubernetes ingress
Request flow diagram from handler code preview
sequence

Request flow diagram from handler code

A sequence diagram of your flagship endpoint's request lifecycle. The agent walks the handler's async/await calls and external integrations, then records each code change as a new revision with a structural diff.

Source: Handler source code (TypeScript / Python / Go)
Visual architecture diff for a proposed change preview
architecture

Visual architecture diff for a proposed change

Let an agent apply a proposed code change to an architecture diagram as a new revision, then share the visual diff (added=green, removed=red, changed=amber) with the people reviewing it.

Source: Proposed code change