Screenshots

The whole application, as it actually runs.

63 captures across 8 areas - first run, workspaces and live terminals, the Knowledge Markdown surface, every built-in theme, settings, and the dialogs that create work.

From the running app

Each frame was taken from the real desktop build, driven over its automation port. Nothing here is a mockup, a render, or stock art.

Whole window, unedited

Full 1600 x 1000 window captures. No cropping, retouching, or composited UI - the terminals show actual process output.

A throwaway repository

The subject is a demo project created for these captures, so no private path, repository, or account appears in any frame.

First run

A local profile is created before anything else. No cloud account exists at any point in this sequence.

Full size

Profile creation

The very first screen. A profile is a local workspace identity, not an operating-system login.

Full size

Naming the profile

Name, optional email, and a colour used to distinguish profiles in the top bar.

Full size

Straight into the introduction

Once the profile exists the app moves to a seven-step product introduction.

Product introduction

Seven steps that explain the model before any agent is launched: folders, worktrees, terminals, knowledge, accounts, notifications, and continuity.

Step 1 - folder-backed work
A team begins with a real working folder; agents, worktrees, and notes stay organised together.

Step 2
Each coding agent gets a persistent workspace and terminal rather than sharing one shell.

Step 3
Tabs split into terminals, browser views, file viewers, and Knowledge panes while preserving layout.

Step 4 - knowledge inside
Project knowledge lives beside the terminals that use it, as ordinary Markdown in the project folder.

Step 5
Provider accounts are connected once and reused across agents; each provider owns its own auth.

Step 6
Permission, working, and review states surface so attention stays visible after a context switch.

Full size

Step 7 - local continuity

A profile remembers the exact route, tab, and focused pane you stopped at.

Workspace and terminals

The main surface: a team rail, tabbed panes, real ptys running in the project folder, and a file tree. Every terminal below is a live shell, not a rendering.

The workspace
Team rail, tab strip, model bar, a live terminal, the file tree, and the ports panel.

A real shell
git log, ls, and git status executed in the pane - actual process output, captured live.

File tree
The project tree resolves the folder the agent is working in, including nested sources and notes.

Tabs
Terminal and Knowledge live side by side as tabs in the same workspace.

Split panes
One tab holding two independent terminals, each with its own scrollback and process.

Both panes working
Source printed on the left, a diff summary on the right - two live shells in one tab.

Reading code and diffs
Syntax-highlighted source and git diff output inside the workspace, no external editor.

Ports
Ports opened by the workspace are tracked and listed per agent.

Exact resume
After a restart the app returns to the same workspace, tab, and focused pane.

Agents list
Every agent grouped under the team that owns it.

Tasks
The task surface for tracking work across agents.

The manager

One seat leads the rest. A message starting with `task:` goes to the manager, which splits the work across every AI member; anything else goes to the semi-manager, which answers questions once a run is done.

Live preview beside the manager
Clicking a Markdown file opens edit-and-preview in one pane, updating as you type. Here it sits next to the manager desk, and the roster below explains in plain words why a notes seat cannot be handed work.

Knowledge

The embedded Markdown workspace. Notes are ordinary files in the project folder - editor, graph, calendar, and capture all read the same source.

Markdown editor
Live preview with rendered wikilinks. The underlying file is plain Markdown on disk.

Vault graph
Links between notes rendered as a navigable graph, built from the demo vault's own wikilinks.

A working note
Free-form notes sit next to the code they describe.

Structure and quotes
Headings, ordered lists, and block quotes rendered inline while editing.

Vault tree
Folders and notes in the vault, filtered and sorted.

Graph controls
Tag, folder, and neighbourhood filters with 3D, orphan, and unresolved-link toggles.

Start centre
Recent notes and vault actions on entry.

Calendar
Notes placed on a calendar for date-driven work.

Capture
Quick capture into the active vault.

Collaborate
The local-first collaboration manifest, shared as an ordinary file.

Opening Knowledge
Knowledge opens as a pane inside the workspace, sharing the host's theme.

Guided tour
A fourteen-step tour of the Markdown surface.

After the tour
The full Knowledge surface once the checklist is dismissed.

Full width
Collapsing the host panels gives Knowledge the whole window.

Calendar pane
The calendar surface hosted inside the workspace.

Graph pane
The graph surface hosted inside the workspace.

Themes

Eleven built-in themes. Each one restyles the app, the editor, and the terminal together - every frame below is the same workspace under a different theme.