The architecture · 03 / Control

Operators & leaders

Use the same model to verify results, inspect changes and see what deserves attention.

WorkspaceMCP
What it is

The same model that answers agents also drives screens people read. A project shows what changed since your last visit. A repository shows, build by build, what the product started or stopped doing. The work list shows what each closed task promised to touch, set against what actually changed. A separate list shows what the product itself says is worth a look.

What you do
01

Open a project and read the summary of what moved since your last visit.

02

Open a repository and compare any two builds.

03

Open the Work tab to see closed work checked against what it promised.

04

Read the attention list and decide what to act on.

What it does not do

This watches the product, not your agents: GitMir sees the questions an agent sends it — those are on your usage page — and nothing else, no transcript and no record of what it did in your systems. The promised-versus-changed check only runs for work that named what it would touch, and only after the next build. There is no alerting — you look, nothing pages you.

See it on a real product.

Three models are published in full and open without an account. Ask one of them the question this page is about.