Documentation Index

Fetch the complete documentation index at: https://docs.leapter.com/llms.txt

Use this file to discover all available pages before exploring further.

​

The Blueprint Editor

The Blueprint Editor is the main workspace in Leapter. Every project opens directly into the editor, and the editor shows the entire project at once: the type definitions, the project’s inputs and outputs, every Blueprint in the project, and the dependencies between them. The Blueprint Editor is a single page. There is no separate “diagram” page or “spec” page — you work in one place that combines a structured document view (Specification view) with the interactive diagrams embedded inline. When you want to focus on a single Blueprint’s diagram, you maximize it in place — see Diagram view.

​

Editor layout

The editor is divided into four areas: a top toolbar, a Contents sidebar on the left, the document area in the center, and a tabbed sidebar on the right.

​

Top toolbar

The top toolbar runs across the top of the editor:

• Toggle sidebar — collapses or expands the main app sidebar (the narrow vertical strip with Projects, Profile, and API keys).
• Live — toggles Live mode. When on, your Blueprints re-execute automatically every time you change inputs or logic, so the Outputs footer in each section stays current.
• Maximized blueprint pill — when a Blueprint is maximized to its diagram, its name appears here. Click to switch which Blueprint is maximized; click the X to leave the maximized view.
• Trace controls — Jump to first / Previous / Step counter / Next / Jump to last, plus Step into and Step out for Call nodes, and Exit trace. These are active after you run a Blueprint and let you replay the execution step by step. See Test your Blueprint.
• Share — opens the Share menu with deployment options (Connect, n8n, Code, Embed) and the Share with people option for public read-only links.

​

Contents sidebar (left)

The Contents sidebar shows everything in your project as a navigable table of contents:

• Type Definitions — reusable Value Types and Data Types defined at the project level. Double-click to open the Type Definitions editor.
• Inputs and Outputs — a shortcut to the project’s external interface, which is the signature of the active Execution Scope. See Inputs and Outputs.
• Blueprints — every Blueprint in the project, listed with its name. Each Blueprint shows its numbered sections (1, 1.1, 2, …) when expanded. Double-click a Blueprint or section to maximize it.
• Dependencies — at the bottom, a graph showing which Blueprints call which. Useful for navigating large projects and spotting circular dependencies.

Click any entry to scroll the document to that location. Double-click to maximize a Blueprint to its diagram.

​

Execution scope and the main Blueprint

A green spark icon (⚡) next to a Blueprint name marks it as the active Execution Scope — the entry point that runs when the project is invoked from outside. Its signature is the project’s external interface (and what the Inputs and Outputs shortcut at the top of the sidebar points to). You can change which Blueprint is the active Execution Scope; the others remain in the project and can still be called via Call nodes.

​

Parameters and Quick Run

Each Blueprint in the Contents sidebar has a # N badge — the count of its inputs and outputs. Click it to expand the Blueprint’s parameters in line:

• Each input shows its name, description, and a control to set a value (e.g. not set dropdown for an enum, a number field for a number)
• Each output shows its name, description, and the most recent value (after a run)

This is the Quick Run entry point: set values on the inputs, then run the Blueprint manually or turn on Live mode to re-run automatically as you edit. See Test your Blueprint.

​

Document area (center)

The center area shows the project as a structured document. The top of the document shows the project’s name and description, followed by Type Definitions, Inputs and Outputs, and then each Blueprint as a section with:

• A heading with the Blueprint name and description
• An interactive diagram showing the Blueprint’s logic
• An Outputs footer (when Live mode is on or after a manual run) showing the current output values

This is the Specification view — see Specification view for details on navigating and editing inside it. To focus on a single Blueprint’s diagram, double-click its entry in the Contents sidebar or click its maximize icon. The diagram fills the canvas and the rest of the document is hidden — see Diagram view.

​

Right sidebar

The right sidebar is collapsed by default. Click any tab to open it:

• Tests — manage test suites for the active Blueprint. Create them manually or auto-generate with AI.
• Suggestions — review proposed changes from AI sync. When you ask Leapter to reconcile your descriptions with your logic (or the other way around), the diff lands here for you to apply or reject.
• Prod Runs — execution logs from when your Blueprint runs in production via the REST API or MCP.
• Comments — leave comments on Blueprints, sections, or nodes for team collaboration.

​

Editor toolbar (right edge of a diagram)

When a Blueprint is maximized, a small vertical toolbar appears on the right edge of the diagram canvas:

​

What to do next

• Specification view — navigate and edit the project as a document
• Diagram view — work inside a single Blueprint’s diagram
• Inputs and Outputs — define what data flows through your project
• Sync & Suggestions — keep the spec and the logic in sync with AI