Architecture Dissector

Architecture Dissector shows maps that your coding agent writes from your source code. Start with one project you know well, so you can check the first map against what the app does.

Install and connect your agent

After buying, connect your GitHub account in Polar and accept the repository invitation. Download the Mac app from the customer releases, unzip it, and move it to Applications. You need macOS 15 or later.

Open Architecture Dissector, then use these commands in its application menu:

1. Install Command Line Tool… makes blueprint available to your agents.
2. Install Agent Skill… installs the instructions they need to write a map.
3. Set Up Agents… shows the setup steps again whenever you need them.

Drop your project’s folder on the window, or press ⌘O and choose it. Tracking a folder reads its files; it does not change the project.

Map your first project

Suppose you have a small recipe app. Open your coding agent in its source folder and send this request:

Add this app to Architecture Dissector and map it, including its workflows and stored data. Run blueprint guide and follow it.

The agent reads the project and saves a structured map through blueprint. Architecture Dissector draws that map as soon as it arrives. It does not infer the architecture by itself.

Start in Overview, which groups the app into a few plain-language blocks. Click one to see what it contains. Take the Tour walks through the map’s explanation and moves the canvas to each relevant part.

Switch to In Depth for individual components and connections. Technical adds details such as files and the information traveling over each connection. Select a component to read its inspector.

Explore workflows and data

The view controls show different parts of the same saved map:

View	Use it for
Architecture	Components, connections and the overall explanation
Flows	A workflow’s steps, decisions and people or systems involved
Data	Stored entities, fields and relationships
Explainers	Agent-authored scenes played over the diagrams

A missing view usually means the agent has not mapped that part yet. Ask it to add the recipe-saving flow or the database entities, then save the updated map.

Scroll or drag to move around. Pinch or use the zoom controls to zoom. ⌘1 fits the diagram. ⌥⌘1, ⌥⌘2 and ⌥⌘3 switch architecture levels. The palette changes the diagram theme.

Save and compare versions

Save a map at a meaningful milestone, such as your first release. Press ⌘S and name the version. The same operation is available from the project’s folder in Terminal:

blueprint snapshot --version 1.0.0

The timeline lets you compare saved versions. New components appear in green, changed ones in amber and removed ones in red. Data comparisons show changes to fields as well.

After changing the project, ask the agent to run blueprint status, update the affected map sections and save them. A changed-file indicator means the source moved on since the map was saved; it does not rewrite the explanation automatically.

Use the CLI

Run these from a tracked project’s folder to inspect its map:

blueprint show --json
blueprint show --data --json
blueprint status
blueprint versions

blueprint guide explains the map format. blueprint capabilities lists tasks and examples. Use blueprint help for command help.

Maps and saved versions stay in ~/Library/Application Support/Blueprint. Include that folder in your backups. The project source stays in its original folder. Download app updates manually from the customer releases page and replace the installed app.