The portal

Where you run the company: observe it, talk to it, approve what waits for you, and connect its tools. Every page, and how to read a status.

Signing in

You sign in to the portal with GitHub, and work in one enterprise at a time. If you belong to several, the portal asks which to open; the switch button in the header brings you back to choose again, or to log out. The Map also draws the other enterprises you hold, and selecting one offers to switch to it.

To jump straight to a team, member, role, task, execution or webhook by name, press Cmd+K (or Ctrl+K), or g when you are not typing in a field.

Reading a status

Every status in the portal (a run, an execution, a gate, a webhook, a node in a graph, a count in the sidebar) is one of five. Each has a colour, and each also carries a glyph and a word, so it reads the same without colour.

Status Glyph Colour Means You will see
Success ✓ Green It finished, and finished well. Completed, Approved, Accepted
Running ● Amber It is moving right now. Running
Idle · Grey It is not moving, and nothing is being asked of you. Queued, Pending, Waiting for a run, Spend paused, Cancelled, Skipped
Failure ✕ Magenta It ended badly, or cannot go on. Failed, Blocked, Stopped, Rejected
Action required ▲ Cyan It is waiting on a person. Waiting for approval, and every decision waiting on you

The sidebar's counts follow the same rule: a count is coloured by what it counts. Approvals waiting on you are cyan, blocked work is magenta, work paused on a cap is grey.

What you see depends on your access

An owner sees every page. Anyone else sees the pages their access covers, and the server refuses the rest whatever the portal shows (People and access). Map and Enterprise are open to everyone who belongs to the enterprise.

Core: the company

Page What it is for
Map The whole company as nested circles: teams, the members on them, the roles they hold and the tasks in each role. Anything without a complete place yet (a member on no team, a role nobody holds, a task whose role nobody holds) is listed under Outside the team structure, with the reason. New enterprise starts another company.
Enterprise The company's headquarters: waiting gates, blockers, live runs and today's spend at a glance, with a warning once spend passes 80% of the tightest day cap. Here you set the company's picture and metrics, how many runs the company may have going at once, and the models and tools the whole company shares. See Enterprise.
Teams Every team, its lead and its charter. A team's page shows its task workflow, its members, its concurrency limit and its tools. See Teams and charters.
Roles Every role, who holds it and the tasks done in it. See Roles.
Members Every member. A member's page has their persona, teams, roles, active run, tasks, model connection, tools and inbox, and starts a chat with them. See Members and inboxes.
Tasks Every task, the OS's own included, with the teams that have it. A task's page shows its definition, versions, triggers, pending improvements and run history, and starts a run. See Tasks.

Operations: the work

Page What it is for
Chat Talk to any member, ask for work, and decide what it needs from you in the thread. See Chat and plans.
Executions A board of work as it moves from task to task: ready, in progress, blocked, complete. See Executions.
Runs Every run of every task, with its log, tool calls and cost. See Runs.
Gates Every call waiting for your approval: the task, the tool, what the run says it does, and how long it has waited. Approve, reject, or open the run to request changes. See Gates and tool scopes.
Plans A proposed change to the company, waiting on your decision. Nothing proposes one yet: see Chat and plans.
Blockers Everything stuck that wants a decision or a fix: failed and stalled runs, blocked runs, stopped pipelines, loops that reached their limit, models that could not be reached, task definitions that cannot run, runs paused on a cap, and teams with no lead or no metric. Retry or clear from here. Waiting gates are not blockers: they stay on Gates.
Waiting Open work nothing is working on: its last run ended without finishing the work, no run is live or queued, no decision is waiting and it is not on Blockers. Each row shows the task that ran last, how it ended, the reason it gave and how long it has waited. Restart it at a step, or mark it finished. A task can declare the outcomes that finish its work, and work that ends on one is never listed: see Finished work.
Memory What the enterprise has learned, and the evidence behind each entry. See Memory.
Self-Improvement Changes the OS proposes to a task after a run that went wrong, one row each, for you to approve or decline. See Self-improvement.

Settings: connections and limits

Page What it is for
Agents The model connections members think with: Claude, OpenAI, Grok or OpenRouter, for the whole enterprise or one member's own account. See Spend and models.
Tools Every tool binding, at every layer: the enterprise, a team, a member, a role or a task. A binding can also carry custom props: key → value settings the tool reads, added behind Custom props at the top right of its form. A prop whose key names an argument of one of the tool's calls fills that argument on every such call, from every task and chat that uses the binding, and the model is never asked for it. Each tool's guide lists the keys it takes. Systems Zero Human has set up as Express tools are listed first, each with Connect: you sign in with your own account and it is connected, with nothing to fill in. See the tool directory.
Webhooks Every task trigger and gate decision received from another system, with the response it got and the execution it started or continued, and the webhook secret. See Webhooks.
API tokens Credentials for scripts, monitors and agents, each scoped to what it needs. See Authentication.
Connected apps External agents connected to the enterprise through its MCP server, each acting as a member with the scopes a person approved. Revoke one to refuse its next request. See MCP.
Spend Spend caps at every layer, today's spend against them, and the switch that turns enforcement on and off. See Spend and models.
People The people in the enterprise, what each holds, and outstanding invitations. Owners only. See People and access.

Community

Page What it is for
Catalog Public tasks. Clone installs one, linked to its original at the version you cloned, for the holders of its role; Copy makes an independent task your enterprise owns and can edit. Credentials and memory never come with either. See the task directory.

Publishing your own work

Everything you make is private until you publish it.

  • A task: the Catalog switch on the task's page. On puts its current version in the catalogue; off withdraws it. While it is public, every version you save goes to the catalogue too, and companies that cloned it are offered it. If the catalogue turns a version down (it names your company, say), your save still stands, the page tells you why, and the catalogue keeps the version it had: Update catalog sends the newer one once you have fixed it.
  • A role: Publish to catalog on the role's page lists its tasks with a tick each. Ticked tasks go with the role; unticked ones stay private. Once the role is published, the same page says how many changes are not in the catalogue yet (a newer task version, a task added to the role, a task that moved to another role) and Update catalog opens the same list.
  • A team: Share on the team's page lists its roles with a tick each, and under each role its tasks. A role you leave out stays left out the next time you share. Once shared, Update catalog brings the entry up to date.

Members, connected accounts, memory and run history never travel.

The sidebar's counts

The sidebar says what needs you without opening a page. It refreshes every few seconds while the tab is open.

Item Counts
Chat Replies from members you have not read.
Executions Executions running, queued and waiting right now.
Runs Runs in progress and waiting right now, and runs paused on a spend cap.
Gates Calls waiting for your approval.
Plans Plans waiting for your decision.
Blockers Work blocked or failed.
Waiting Open work with nothing working on it.
Self-Improvement Proposed changes waiting for your decision.
Spend A warning once today's spend passes 80% of the tightest day cap.