# Tell the Robot What You Want — Sandhya Subramani, AWS

Source: [AI Engineer](https://www.youtube.com/watch?v=S6aSoQ6_u5A)  
Feed7 permalink: https://feed7.dev/p/tell-the-robot-what-you-want-sandhya-subramani-aws-1i532jq  
Published: 2026-08-29T18:30:17.000Z  
Trust: Source Linked (source_linked)

## Why Included

An AWS demo treats a robot as an agent tool: an LLM selects existing hardware policies while separate agents handle thinking, communication, and voice. The live failures expose the safety gap.

## Source Summary

The rover uses **three concurrent Strands agents** for environmental reasoning, text communication, and voice. The agent chooses which existing robot policy to invoke; execution spans cloud training and edge runtime, and the package is said to support **40+ robots across eight categories**.

## Practical Implication

The transferable pattern is to expose constrained hardware capabilities as tools and keep “what to do” separate from the policy that determines “how.” Coding-agent builders should apply explicit tool descriptions, narrow permissions, and guardrails at that boundary.

## Agent-Ready Context

The rover uses **three concurrent Strands agents** for environmental reasoning, text communication, and voice. The agent chooses which existing robot policy to invoke; execution spans cloud training and edge runtime, and the package is said to support **40+ robots across eight categories**.

The transferable pattern is to expose constrained hardware capabilities as tools and keep “what to do” separate from the policy that determines “how.” Coding-agent builders should apply explicit tool descriptions, narrow permissions, and guardrails at that boundary.

The live rover fell from the stage and sometimes spoke without performing the requested action. The demo shows flexible orchestration, but not reliable planning, physical safety, or that untrained motor capabilities emerge from the agent layer.

## Connected Context

Feed7 judgment across 617 accumulated Signals:

This makes the tool boundary concrete in robotics: the agent selects among existing policies, but does not thereby acquire new motor competence or safe physical planning. The failed live behavior reinforces prior arguments for narrow authority, external guardrails, and evidence of execution, while adding that a valid request, spoken acknowledgement, and completed physical action are distinct states that the harness must verify.

- [Give the Agent a Budget, Not a Token — Sachin Malhotra, Anthropic](https://feed7.dev/p/give-the-agent-a-budget-not-a-token-sachin-malhotra-anthropic-1sm80qu) — Bounded write authority becomes bounded physical authority here: policy selection and robot actions need narrow permissions and runtime limits because a valid tool capability can still create an unsafe outcome.
- [IT Admin for the AI Workforce — Sarthak Aggarwal, Decawork](https://feed7.dev/p/it-admin-for-the-ai-workforce-sarthak-aggarwal-decawork-0oxlc5t) — The rover supports the claim that instructions are not a security boundary; identity, scoped capabilities, policy gates, and revocation must sit outside the reasoning agent before hardware actions run.
- [What Does Done Even Mean? Agents and Paperclip's Liveness Model - Dotta, Paperclip](https://feed7.dev/p/what-does-done-even-mean-agents-and-paperclip-s-liveness-model-dotta-pap-0lx8wfc) — The rover speaking without acting demonstrates why completion cannot be an agent-declared Boolean; physical execution needs independent evidence, verification, residual-risk assessment, and clear ownership.
- [In Code They Act, In Proof We Trust — Erik Meijer, Leibniz Labs](https://feed7.dev/p/in-code-they-act-in-proof-we-trust-erik-meijer-leibniz-labs-1lyno2y) — The proposed separation of planning from proven execution is especially consequential for robotics, where an inspectable intent should be checked before a policy produces irreversible physical side effects.

## Context Map

- Layer: agent
- Domains: None
- Topics: multi-agent, tool-use, harness-engineering

## Uncertainty

- The live rover fell from the stage and sometimes spoke without performing the requested action. The demo shows flexible orchestration, but not reliable planning, physical safety, or that untrained motor capabilities emerge from the agent layer.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.