VIXENTIO / Documentation

Core concepts

Shared work, runs, hosts, the driver, guidance and reviews: the words the rest of the docs use.

These are the words the rest of the docs use. Each one maps to something you'll see in the app.

Shared work

A shared work is one piece of work the team owns: a request with its brief, what counts as done, and who's responsible. It belongs to the team, not to one person's chat, so anyone with a role can open it and see where it stands.

• Editors and owners create it with New Shared Work…, on the Mac or the web.
• A task you already started on your Mac can join it with Link a Task.
• Copy Link to Work gives you a link that opens it for teammates.

A work moves through states you'll see on its page: Draft, Ready, In progress, Needs input, Needs review, Changes requested, Accepted, Delivered, Closed, Cancelled or Failed.

The timeline

Every work has one timeline: runs starting and ending, guidance proposed and applied, reviews, reviewers and handoffs, in order, with who did what. Project › Activity shows the same moments across a whole project.

Runs

A run is one agent working on the work on one host. A run is starting, running, waiting for a permission, paused, stopping, finished, failed or lost.

A host keeps its run alive by reporting regularly. A host that goes silent makes the run lost, never "finished", so a stopped laptop can't pass for a completed change.

Hosts

The host is the machine a run happens on: your Mac, a teammate's Mac they share as a host, or a cloud workspace (rolling out). Teammates see where each run is, for example "Dee's Mac". Details are in Where agents run.

The driver

Each work has one driver: the person who decides what the agent does next. Others can suggest; the driver decides.

• To pass control, choose Hand Off…: assign the next action, transfer the driver, or move the run to another Mac. The person you hand off to answers Accept and Drive or Decline.
• In the web app, Offer to drive… does the same.
• If the driver is away, an approver can decide in their place.

Guidance

Guidance is how a teammate steers a running agent without taking over the keyboard.

1. Anyone who can comment writes guidance with Guide Agent (or adds a mark to the live preview and sends it).
2. The driver chooses Accept or Decline, or Apply All, in Order when several are waiting.
3. The host gives accepted guidance to the agent at a safe point between steps.
4. The timeline says Applied only once the agent has actually received it, not when it was sent.

Live previews and marks

While a run works on a project with a dev server, its host can share Live: pictures of the running app, refreshed as the agent changes it. Teammates see the newest frame on the work's page, add a pin or box with Add Mark, and send it as guidance.

Only the picture, its route and its width leave the host. The code doesn't.

Designers can keep a standing Design requests work for small visual asks; when a change is ready, the notice says so: "Your change to … is ready".

Reviews

Before anything ships, the team reviews the result: versions of the change with before-and-after pictures and the project's checks, sign-offs by Design, Product and Technical reviewers, and an explicit Approve. Publishing to GitHub is a separate step after that. See Reviews and Publish.

Roles

Nobody approves their own result, and every role is checked again by the server on each action, so removing someone takes effect at once.