Give an agent one robot action, not robot control

A caller moves a sandbox robot within local bounds, then reads finite telemetry; Agent or MCP presentation is outside this fixture.

All source cases Inspect the pinned project

The problem

Shell, ROS exposure, or vendor keys grant much more authority than one bounded action.

What gets published

Allow one move from -100 to 100 cm on a bounded track, followed by at most ten samples.

What stays local

Robot handle, validation, lock, battery rules, and device state.

Business data crossing the call boundary

Bounded move request, action result, finite telemetry, caller and invocation ids.

What this shows

A caller can request one recorded move without receiving a general robot-control interface.

What it doesn't prove

The fixture does not implement MCP presentation. Real hardware still requires approval, emergency stop, durable state, and safety certification.

Public source evidence for this case

Evidence level: Source layout and declarations are anonymously inspectable
Pinned public EasyRemote revision: 44c768ca26d0f92a5ab9d1d03342895c29c27dc6
Public inspection: Public inspection
Expected check: Required files, Python syntax, and @node.register declaration are checked without installing dependencies
Runtime invocation: Not established by this source fixture; record separate discovery, Invocation, and terminal Receipt evidence

Run in a compatible source workspace

This Provider/Client walkthrough requires compatible EasyRemote, EasyNet-Cli, and EasyNet-Axon sibling source checkouts, a compatible Hub, and a paired, running Runtime. The source is public; clean installation from public packages is not yet verified. Technical Alpha offers guided setup. Use the pinned EasyRemote revision below; this page does not pin the other components. Runtime admission still determines whether the caller may execute the function.

# From EasyRemote revision 44c768ca26d0f92a5ab9d1d03342895c29c27dc6
cd gallery/projects/07_claude_code_robot_commander_mcp
# Terminal 1
uv sync --frozen
uv run python node.py

# Terminal 2 (same project)
EASYREMOTE_ROBOT_NODE=robot-1 uv run python client.py

Connect your own function

Read the setup first. You need compatible sibling source checkouts, a compatible Hub, and a paired, running Runtime. Technical Alpha offers guided help; public-package clean installation is not yet verified.

All source cases Request technical alpha