See Compass at work

Navigate and organize the workspace

The Explorer is the workspace as a tree: domains, the subdomains nested under them, and the services inside those. What you pick in it is the scope, and the rest of Compass works on it: search looks there, new issues and notes are filed there, and its policy says how its work runs. One search reaches everything in the scope — its functions, its issues and the text of its files — as well as every service and domain, and command mode opens any of them in the Viewer without leaving the keyboard. In edit mode, folders you already have join a domain where they sit; nothing on disk moves.

A modal editor built for reading code

Files open read-only in normal mode, so reading never edits by accident. The keys are Vim's: find in the file, change a line, and write it with :w. A tab dragged onto the code splits it into two files side by side, a folder or domain opens on its Overview, the AI press over the code asks the file's own AI about it, and under the code the Actions panel holds a terminal, problems, output and the outline.

Architecture generated from the code

Each service and domain has a Topology, built from its code: a Tree of every function by file, and a Map of the services, the calls between their functions and the events that pass between them. A function's card shows what calls it and what it calls, traces a parameter through the code, opens the models it uses, and scores how hard it is to follow.

Slots define the architectural viewpoint. A slot is a one-line comment in the code that marks a point worth drawing — where a request enters, an event is published or received, a step, a call or a branch. Slots only draws exactly those points: the architecture of a specific flow, at the level of detail the team chose, kept in the code and redrawn whenever it changes.

Compare diagrams side by side

A resizable grid for several diagrams at once — maps, sequences and domain overviews. Viewer Search opens any service or domain as a pane, as a map or a sequence, beside the ones already open; each pane has its own filter, fit, maximize and rotation, and panes rearrange by dragging their headers.

Issue tracking, with an agent beside every issue

Each scope's Workspace is a complete issue tracker: issues and sub-issues as a list or a board of swim lanes, projects planned as goals, labels, priorities, assignees and due dates, and filters that group the same issues by lane, project, priority or service. Every issue has a page of its own — and its Work: with the issue's branch checked out, an agent does the work there in one conversation, and every answer that changes the code is a commit, opened beside the conversation in the Work's version control.

Notes that live with the code

A level's notes, gathered in notebooks as a list or a board: markdown written where it is read — headings, checklists, colour and figures — labels and sub-notes, the issues they are about, and an AI to research them with. A note links the maps it talks about — a service's, a domain's, a folder's — and draws them under its words, live, from the branch each was linked on, so a diagram never drifts from the code.

Talk the work through, beside it

The team chat is where the people in a workspace talk: one teammate or a group, every message in markdown with code that reads as code, an emoji on any of them, and your own edited or deleted. An issue's or a note's id in a message becomes its card — open it, claim the issue, or use its menu right there. It is one press on the status bar from anywhere in the app — a small window over the page, its conversations a dropdown in its head — or a tab of its own. Team chat comes with a Pro subscription — not the free trial.

Terminals where the code is

Terminals run in the workspace: Tools ▸ Terminal at its root, and one under each service's code that starts in that service's directory. Sessions keep running when you navigate away, and a session splits into as many as four terminals, two to a row.

Governance, inherited down the tree

Policy decides which AIs run a scope's work, how its services build, what new services are made from, what Commit does and how work merges, and how its issues are planned — set once at the top and inherited by every domain, subdomain and service below. It is one page, a tab for each part; each level overrides only what differs, and every section says whether it is inherited or set there.

Review, commit and merge

The working tree as git reports it, with each file's diff beside the list. Stage and commit, read the history, create and switch branches, and merge — with a resolver for conflicts. The status bar's git segment opens it from anywhere.