Local console
Watch the robot, send tasks and manage instructions and recordings.
The local console runs on the computer connected to your robot. Complete installation and coordinate calibration, then open http://127.0.0.1:8080/. Under Settings → Devices, check that the camera is updating, devices are connected and control is enabled.
Send and stop tasks
Enter a task at the bottom of the camera view, then send it or press Shift+Enter. Enter adds a line break. Instructions accept 1–1000 characters. Use the up/down arrow on the first/last input line to recall historical instructions into the draft.
During a run, the top of the view shows the instruction, elapsed time and inference latency, and the input area offers Robot Stop. The task continues until stopped or interrupted by a fault. A successful inference does not mean the task is complete.
You can draft another instruction during a run. Sending it stops the current run, waits for the stop to finish, then starts a new task. Editing text or selecting a preset alone does not execute it.
| Action | Effect |
|---|---|
| Robot Stop | Interrupts the policy or controlled motion and ends the run. |
| Home | While idle with control ready, opens the gripper and returns to the calibrated Home pose. |
| Recover & Home | Recovers the device and returns Home. This moves the arm. |
After stopping, send with an empty input to continue the current task. Continuing appends to its recording, omitting the stopped interval. Closing the browser tab does not stop the backend run.
Reuse instructions
Saved instructions appear above the input. Select one to fill the draft, or use ＋ on the left to add, edit or delete instructions. A workstation supports up to 20 presets, each with 1–1000 characters.
Presets are stored on the control computer and shared by its browsers. Selecting a preset or historical instruction still requires sending before execution.
Connect a model and adjust runtime settings
Select the model name on the right of the input to open Settings → Model & runtime. Stop the task, then:
- Confirm the Base URL. It defaults to
https://api.pokebot.com/v1; compatible custom services are also supported. Enter an API key, or leave it blank to retain a configured key. - Select Connect to retrieve the models available to that key. The current model stays selected if it is available; otherwise choose a model from the list.
- Adjust runtime settings as needed, then select Save to apply the model and connection settings.
Changing the address or key requires connecting again and selecting a model. Connect only retrieves the list: it does not save entered credentials or create a task session. A failed connection keeps saved settings and your current input, allowing an explicit retry. Newly entered keys are hidden by default. The service must meet the local runtime requirements.
Chunk wait (s) controls the wait after an action chunk before the next observation and inference. It defaults to 0.5 seconds. Setting it to 0 does not change the 30 Hz action execution rate.
Set the motion range
Open Settings → Devices → Motion range. The range is enabled by default and extends 60 cm from Home in both directions on each X, Y and Z axis. The UI accepts distances from Home in centimetres. Stop the run and finish calibration before saving; saving does not move the robot.
The range limits commanded flange-centre positions. Out-of-range targets are clipped to the boundary and the task continues. It does not limit rotation, describe the whole arm's reach or define obstacles. External forces, compliance and tracking error can still place the measured pose outside the range.
If the arm is outside the range before starting, continuing or moving manually, use Home first. An explicit Home return can start outside the range. Coordinate calibration is unaffected by this limit. See the local HTTP API for programmatic coordinates and units.
View the camera and run information
- Drag to inspect the edges, use Show full frame to see the entire image, or Center view to reset the view.
- The camera icon only hides or shows the preview. Panning, cropping and hiding do not change model input or the full frame recorded to video.
- The preview attempts to reconnect after a stalled stream or when you return to the browser tab. If device status also reports the camera unavailable, follow camera troubleshooting on the control computer.
- The top shows the latest inference latency. Run information and filterable Logs provide activity and request IDs.
Manage tasks and recordings
Task history retains instructions, ratings, notes and recordings. Under Settings → Recording & storage, control recording for subsequent runs, inspect usage and clean up local storage.
| Action | What remains |
|---|---|
| Clear recordings | Deletes videos and keeps instructions, ratings and notes. |
| Delete tasks | Deletes instructions, ratings, notes and videos together. |
Batch cleanup skips tasks that are running or saving video. Individual deletion also rejects these tasks. Task records, feedback and video stay on the control computer; ratings and notes are not sent to the model service.
Share devices with an Agent
An Agent connected over MCP can use the same robot. Agent-owned runs are read-only in the browser except for Robot Stop. Stop the current run before switching entry points.
Sending a new instruction in the browser stops and starts a new task. The HTTP API and MCP also offer pause, resume and active-instruction updates. An active-instruction update takes effect at the next inference without interrupting the current action chunk.