Nexa AgoraNexa Agora
Platform DocumentationAll the documentation →
  • Getting started4 guides
  • Connect your tools6 guides
  • Run your workspace9 guides
  • Talk4 guides
  • Build5 guides
  • Focus3 guides
  • Knowledge3 guides
  • Help2 guides
AI Solution AdvisorAdvisorDescribe one task your company would like to improve: you get, right away and free, a preliminary solution and an indicative cost range.Nexa AcademyAcademy
Sign inJoin for free
Nexa Agora© 2026by NexaEthos S.L.A shared workspace for people and AI teammates, under your rules.EnglishItalianoEspañolFrançaisDeutsch
The productHow it worksProduct tourAgents
How it's builtTechnologyNexa BridgeGovernancePrinciples
Getting startedUse casesQuestionsPricingDocumentationNexa Academy
The companyAbout NexaEthosPrivacyTerms
Nexa AgoraTerms of SaleTerms of UsePrivacy Policy
Platform DocumentationDocs
Documentation home
Set up your workspace
  • Mailboxes and calendars
  • GitHub and Discord
  • Your external agent
  • Your models
  • Nexa Bridge
  • Physical AI
Work in Nexa Agora
DocumentationConnect your toolsPhysical AI

Physical AI

Link the machines in your real spaces, read what they report, decide the commands they propose, stop one, and follow a mission in its discussion.

For everyoneConnect your tools · page 10 of 36

Physical AI links the machines in your real spaces to the workspace: lab boards, robots, and the gateways that command machines. They report what they notice and propose what to do next. A person decides, and only then does a machine carry it out and report back. This page helps you link a device, read what it sends, decide its commands, and choose who manages it.

Before you start#

  • Open Governance › Integrations › Physical AI.
  • Everyone in the workspace sees this page. Owners and admins approve, revoke and remove devices.
  • The device runs Nexa Bridge, the same app that links a computer for Nexa Bridge.

The page opens on the cycle every device follows: They notice, They propose, A person decides, The machine carries out, It reports back, each with today's numbers, for example 0 reports today or Nothing waiting.

Link a device#

  1. 1

    On the device, start Nexa Bridge and choose to link it to a workspace.

  2. 2

    It opens the approval page in your browser, with a short code. Check that it matches the code on the device.

  3. 3

    The page Approve a device shows Type, Runs on, What it can observe and, for a gateway, What it can command. Check what the device says it can do, and click Approve this device.

    The page says Approved; waiting for the device to check in…, then It checked in. What it observes now reaches … with your workspace's name, and See it in Integrations › Physical AI.

If it's a gateway, what you approve is everything it may command. To change it later, the device must be linked and approved again.

A member who starts the link sends it to an owner or admin. Didn't start a link? Close the page: nothing is approved, and the code expires on its own. A device isn't on a bridge connection and doesn't count against your plan.

Read the list of devices#

Devices come in two groups:

  • Command machines — gateways. Approving one of their commands makes a machine move. They are marked Commands machines.
  • Observe only — lab boards and robots. They report and can propose a look; nothing moves. They are marked Observes only.

Each device shows its name, its type (Gateway, Robot or Lab board), when it was last seen, and its latest report. A gateway that inspects with a robot also shows the robot's route, for example dock, press-1, drying-rack, dock.

Under the list, a line counts the devices online, offline, approved · not seen yet and revoked. Online means seen in the last 90 seconds.

Click a device to open it in place. It shows State, Platform, Software and Managed by, then its tabs: Commands, Journal, About and access, Record, Agents and Discussion.

01A command running, the cycle, and the workspace's two kinds of device.

Read what it sent#

  1. 1

    Open the device and click Journal.

  2. 2

    Reports come newest first, grouped by day, and are kept for 31 days. Each one has its kind, such as Change of state, Diagnostic, Alert or Anomaly, the sentence the device wrote, and Warning or Critical when it matters.

  3. 3

    Click a kind, or Warnings and critical, to show only those. Everything shows them all again.

Decide a command#

A device proposes a command, for example taking a camera capture or sending a robot to inspect a panel. Nothing runs until a person says yes.

  1. 1

    The person who manages the device receives a card in Pending Actions. The same decision shows on the device, under Commands, as Your decision · also in Pending Actions.

  2. 2

    Read Proposed because: and If you approve:. For a gateway, the decision reminds you that approving makes a machine move, and that the device carries it out as it declared and reports how it went.

  3. 3

    Click Approve to run it, or Refuse to run nothing. From the card, Open Physical AI shows the device.

Under Commands, follow each one: Waiting for approval, Approved · waiting for the device, Delivered to the device, Running, then Done, Failed, Turned down by the device or Stopped, or Refused by … when a person said no. Each one says who approved or refused it, and when it was delivered, ended or stopped. Settled commands fold to one line; open one to see how it went.

02Your decision on the device, the same one that waits in Pending Actions.

Stop a command#

While a command is running, a band at the top of the page shows it, with Stop.

  1. 1

    Click Stop. Anyone in the workspace can, and a stop never waits on anyone's approval.

  2. 2

    You see Stop asked. The device confirms when it has stopped. The command reads Stop asked · waiting for the device until it does.

Click What Stop does and doesn't do to read its limits:

  • The workspace doesn't steer the machine while it runs, and it isn't the machine's safety layer. The physical stop stays with the people beside the machine.
  • If the device loses its connection, what it does is its own rule. It goes on with its mission and reports when the connection returns.

A command still waiting for approval isn't stopped: it is decided on its card.

Choose who manages it and its team#

Open the device, then About and access. Under People:

  • Who manages it — by default, Owners and admins: any owner or admin approves or refuses its commands, in Pending Actions, and takes part in its missions' discussions. An owner or admin clicks Change to choose one person instead. One person, or the owners and admins — never an agent.
  • Its team — the people who take part in its missions' discussions. They approve nothing. Who manages it, or an owner or admin, clicks Change, ticks the people and clicks Save the team. People only, never an agent: they call agents in by mention.

About and access also lists What it can do: what it Observes, and for a gateway what it Moves a machine to do, with the robot's route.

03Who manages the device, its team, and what it may command.

Follow a mission in its discussion#

When a command that moves a machine is approved, a private discussion opens in Agora for the people who manage the device and its team.

  • The machine writes there on its own while the mission runs, for example On the way to press-1, At press-1: kept 3 fresh frames; one is attached, the others stay on the board, Back at dock, and the outcome at the end.
  • Its messages are signed Device, with a chip in place of a face: a machine reporting, not a person and not an AI agent.
  • A photo the machine took shows in its message. Click it to open it larger.
  • Call an agent in by mentioning it.

Revoke or remove a device#

Open the device, then About and access. Under Access:

  • Revoke — it stops at once: it can't send anything or receive commands any more. What it sent stays readable here for up to 31 days, then it's deleted. To use it again, link it again.
  • Remove for good — deletes the device, its journal and its commands. This can't be undone. Its missions' discussions and their photos stay. To keep its journal, revoke it instead.

What you will see#

Device states: Online, Offline, Approved · not seen yet and Revoked.
Not seen for more than 90 seconds. A stop can't reach it until it's back. — on a device that is offline.
Nothing yet. It hasn't connected since its link was approved. and Nothing sent in the last 31 days. — in an empty Journal.
Waiting for an owner or admin to decide, in Pending Actions. or Waiting for … to decide, in Pending Actions. — on a command not yet decided.
Approved. The device receives it now. and Refused. Nothing runs. — after your decision.
The device said: … — on a command the device turned down, with its reason.
Coming later — on Record, Agents and Discussion. The record of every action on the device, the agents that may use it, and its own room in Agora are not readable here yet.
Machines that ask before they move. — when the workspace has no device yet, with Link your first device.

Good to know#

  • A gateway carries out a command as it declared it. The workspace doesn't steer it while it runs.
  • What a device may command is fixed when its link is approved. Nothing an agent or a person says later widens it.
  • Only a person approves a command or gives a device a manager or a team. An agent never does.
  • Reports and commands are kept for up to 31 days.

Related#

Nexa Bridgethe app the device runs, and how a computer serves a model.Pending Actionswhere the cards for a device's commands arrive.Agora roomswhere a mission's discussion lives.Organizationwho is an owner or admin.
PreviousNexa BridgeConnect your toolsNextOrganizationRun your workspace
On this page
  • Before you start
  • Link a device
  • Read the list of devices
  • Read what it sent
  • Decide a command
  • Stop a command
  • Choose who manages it and its team
  • Follow a mission in its discussion
  • Revoke or remove a device
  • What you will see
  • Good to know
  • Related
Back to top ↑