The workspace

Signing in#

The workspace is served from your own computer on 127.0.0.1 and nowhere else. The Mac app signs itself in. For geo open, the terminal prints a one-time sign-in link: open it in your browser. A link works once and expires after ten minutes. Run geo open again to get a new one. If a page says "That sign-in link was already used or has expired", that is why. See Troubleshooting.

Projects and the first page#

The first page has two equal choices: Try the practice agent and Open my project…. In the Mac app the second opens the native folder picker. In a browser it asks for the folder's path, which you can type, paste or drop, or you can pick one of your recent projects. A line above the choices says whether Docker is ready. Under Recent projects, the info icon beside a project shows where its folder is.

A new project shows only the loop in its navigation: Open, Check, Fix, Keep. After its first result, the navigation shows three places (Board, Guard and Prove) and, at the bottom, the settings of the whole computer. The practice project works the same way as any other project.

Older addresses still work and open the Board: Overview, Explore, Authority, Proving ground and History. Live opens Guard and Certificate opens Prove.

Your kind of agent#

When a project opens, Geometer guesses what kind of agent it is from its tools and asks once, with the guess already selected: "Looks like a payments agent. Right?" One tap picks Payments & refunds, Games & live worlds, Customer support, Bookings & travel or Something else. You can change it any time (Change, under the project's name), and nothing waits on the answer. The choice changes only the words (a game's agent "restores" where a payments agent "refunds"), the example rules offered on the Rules page and which practice world comes first. The checks, the evidence and what is claimed stay the same. geo check uses the same words.

The board#

Before the first result, the page is the first-check page: the loop across the top, one button, Check this project, and what Geometer found, counted. Detail such as What a check does, the time limit for agent runs and the commands of the project's own tests sits behind expanders. The info icon beside the project's name shows its folder. When the check finishes, its result is the board.

The board is a grid. Each row is a tool that changes something (a refund, an email, a restored item). Tools that only look things up are one quiet line, such as "3 read-only tools". Each column is a fault Geometer can create: Normal, Reply lost, Request lost, Partial effect, Acknowledgement lost and Crash and restart. A cell is one tool tried with one fault, in one word:

• Held: it was tried and no rule broke. That covers only what was tried, never everything.
• Broke: a rule broke. Press it to read the story.
• Couldn't tell: Geometer could not judge. Under the grid, one line per tool says the one step that would help, for example "Geometer can't see this tool's effect. Point it at the app's database." A screen reader reads that step with the cell.
• Try it: not tried yet. The cell is quiet until you point at it or tab to it. Press it to try that one fault; you can press several and they run one after another while you keep reading. A try that is still running shows its slow marker even after you reload the page. The board fills as each answer arrives.

A line above the grid says how many problems there are. The same problem in two agents counts once ("1 problem in 2 agents"). Kept beside Faults lists the checks you kept, with their last result.

At the end of each row, three dots show what that tool may do on its own: shadow (Guard only watches), ask (a person approves) and act within limits. Under them is what still stands between the tool and the next step, such as "2 faults not tried". Only a person grants a level, in Guard.

Broke opens the problem beside the board (the board scrolls sideways with the tool names kept in view, and the Next card steps aside while the problem is open). It leads with the tool, the fault and the effect, then the story on a line: what Geometer saw is solid, and a lost reply is dashed and fades. One main button follows the loop: Replay, then Copy for your AI assistant, then Check my fix, then Keep this check. Keep this check stays disabled until Check my fix has passed, because what you keep is the fix. After it is kept, the page names the file to commit (the info icon shows the full path). The rule, the replay player and the calls and records are behind Details. The problem's own address (#/p/<project>/problems/<id>) shows the same content as a page.

Under Details at the bottom of the board you also find Rules, Practice, Check a model change, Check constraint stability, Can we ship? and For reviewers. This computer has no accounts, so every name you type into the workspace is stored as typed and is never a verified identity.

Motion only explains. A step of the story appears after the one before it, a lost reply turns dashed and fades, a cell that changes from Broke to Held flips once, and a cell that is being tried shows one slow marker. If you ask your system for less motion, every change is instant and the word says it.

On a phone the grid becomes a list: one line per tool with its faults as small marks, and a tool whose tried faults all held folds to "All tried held" until you open it.

The next step is chosen in a fixed order, and the first that applies wins: look at the project, answer a question, run a check, follow a running check, fix or read an open problem, keep a fixed problem as a check, make a certificate, recheck after a change, set Guard to watch, grant the next level, or nothing. geo status prints the same line and next step in a terminal.

Guard#

The Guard screen is Guard's own, for development and staging. See Guard. Lower on the page, What each tool may do has a row for each action: the level now on a five-notch rail, what the next level needs, the grant history and a review queue. From a row you can Grant a level, Set a ceiling, record a confirmation or waive a condition (see Autonomy levels and Grant an autonomy level). From top to bottom you find what Guard is doing now, with Start watching on this computer, Stop all new calls… and Allow calls again. Under Waiting for you are the held calls. Further down are Who can approve, Agents, Tools that changed, Not confirmed yet and Recent calls. Try a limit on past calls replays a proposed limit over recorded calls.

Prove#

Prove holds the certificate. There is one action to make it: a draft, then Issue the certificate (with an optional newer signature method). Then Share as a pack, Share as a pack, Preview as a reviewer and Recheck what changed. Its steps read Draft, Issue, Share, Track, and a step is marked done only when it is. Below the certificate are Recheck automatically when the code changes, A dated export for auditors and every certificate. The record lives here too. See Prove and certificates.

The status chip#

Every status in the workspace is one chip: an icon and a word, never colour alone. Waiting, Running, Passed, Needs a look, Problem, Not tried, Couldn't run and Couldn't tell. On the board the same states read Held, Broke, Try it and Couldn't tell. Couldn't run and Couldn't tell are amber and never a pass. Passed means the checks that ran passed, and nothing more.

Info icons#

A small "i" button next to a label opens a short note when you click it or press Enter. Escape closes it and returns you to the button. Notes hold only what helps you trust or verify something, such as a folder's location or what is copied. What you need to choose your next click is always on the page.

This computer#

Settings that belong to the machine rather than a project: Model, Docker and Containers. Reach it from the bottom of the navigation.

• Model is where you choose how Geometer gets optional model help. See Choose a model.
• Docker shows whether Docker is ready and offers the set-up card.
• Containers lists the containers Geometer started, each with what it is for, its image and how long it has run. They are removed when their check ends. If any are left over, for example after the computer slept during a check, run geo gc. Your own containers are never removed.

Under the hood#

Under the hood is a drawer you open from the top bar, from a check page, or from the command bar. It is closed by default and read-only apart from its terminal. Its tabs are Activity, Log, Terminal and Containers.

• Activity shows Geometer's own process (version, how long it has run, processor in cores, memory), the processes it started, its containers with processor, memory and network in and out, and the network activity it can see, labelled by who made it. Processor use is shown in cores. Environment variables and secrets are never shown. Image downloads happen inside Docker, so they are labelled as Docker's. It says what it cannot see. It reads only while it is open.
• Log shows the raw log of a check with its exact commands.
• Terminal opens a command line inside a container with a copy of your project. Anything you run there happens in an isolated container and never changes your own files.
• Containers lists what is running.

Help and Report a problem#

The Help panel opens from the Help button in the top bar or from the command bar, and sits beside the page when the window is wide enough. It is closed until you open it, and your choice is remembered. It explains the screen you are on, with a topic list under All topics and a short glossary called Words used in Geometer. Each topic ends with Read more in the documentation, which opens its page of these docs in your browser. It ends with Something wrong or missing? and Report a problem, which opens the issue chooser for Geometer on GitHub in your browser, and Talk to us, which opens the request form on geometer.dev in your browser to ask for help with your own agent. Nothing is sent from the app. See Privacy and security.

The command bar#

Press Cmd+K on a Mac or Ctrl+K elsewhere to open the command bar. Type to filter, move with the arrow keys, press Enter to run and Escape to close. It lists the Board, Guard, Prove, Rules, Practice, the record, Check this project, each Under the hood tab, Open Help, and a command to change the theme. The workspace is light by default; the theme button in the top bar, or this command, switches to Dark, then Auto (follow your system), then back to Light. The button shows the theme it will switch to when pressed, and your choice is remembered.

Next#

• Check your agentThe guide for the board.
• Command referenceThe terminal version of each screen.