Extensions

An extension is a surface built into the workspace, opened over the pane the active tab is standing in. Two ship today:

Both buttons sit together at the right end of the tab strip — one group, because each opens the same kind of errand. They are compiled into the binary, not installed; Ctrl+O → Extensions lists what is there.

An extension never draws and reaches nothing it was not handed: it describes a view, and the workspace renders it. Running Git, reading a file, resolving $HOME all arrive through a host it is given, which is why an extension is a different trust class from plugin bytes a harness reads (ADR-041).

Every Git read they make runs on a thread and answers through a channel, so nothing waits on a repository — a large history never blocks a keystroke.

Code

Three halves of one checkout, and one selection that survives the switch between them. That is the whole reason it is one extension and not three: the flow is agent first → diff → and only last, touch the real file, so "I see it in the diff, let me fix that line" is the most-crossed seam there is.

The fourth thing it draws is not a half but a section of the workspace's own sidebar: the commit timeline, saying what has landed in the target and what is still ahead, with any commit openable in detail.

Scope is the checkout the tab is in, and nothing else. An agent uze isolated works in .worktrees/<name>, and listing linked worktrees here would put every other agent's diff inside a tab that owns exactly one of them.

Keys

Reading is what it is for; e and d are the two things it writes, and they are the only callers of the host's two writing capabilities.

Architect

A project's architecture, drawn in cells. Mermaid source — flowcharts, C4 views, sequences — becomes a diagram a terminal can show without a graphics protocol, and owning the layout buys what an image cannot:

• every box is addressable, so a click selects it and lights what it connects to;
• a box carrying a link opens the code surface on that path;
• a box whose alias another C4 view draws the inside of is a level to walk into.

It is a board, not a document: the drawing is larger than the screen in both directions, so it is moved rather than scrolled, with a minimap saying where the view is.

What the project declares

One directory, in agents.yaml:

artifacts:
  path: docs/architecture

Everything else is read off the files themselves — the area from the diagram's first word, the name from a title: front matter, the levels from which C4 boundary carries which alias. There is no index beside the files to keep in step with them. See artifacts for the full rules.

Keys

Proving a diagram still draws

A diagram that stopped routing is a real regression and nobody sees it by looking. The check draws every file the project declares the way the surface would:

$ uze agent artifacts check          # --format text | json

Three verdicts: drawn, unrouted (the boxes are there but an edge found no path — the relation is simply absent), and undrawable. Both failures exit non-zero, so it belongs in a project's gate. Writing one of these is the subject of the uze:architect Skill in the official plugin.