ROBOT.md + Amazon Q

What's blocked today.

The blocker is architectural — Q CLI's MCP stdio transport is compiled for x86 only as of 2026-04-29. There is no workaround on aarch64 hardware short of cross-architecture emulation (not recommended for production robotics). When AWS ships a universal binary or aarch64 build, the integration is a one-line config change identical to the Codex and Gemini setups.

OpenAPI bridge fallback.

The same robot-md-http bridge used by ChatGPT Custom GPT Actions works with Q's web and chat surfaces. It exposes your robot manifest as an OpenAPI endpoint that any HTTP-capable agent can call.

Start the HTTP bridge

# Install and start the OpenAPI bridge:
$ npx -y robot-md-http ./ROBOT.md

# Bridge starts at http://localhost:4000
# OpenAPI schema: http://localhost:4000/openapi.json
# Point Amazon Q's plugin/tool config at this endpoint.

Full walkthrough for the HTTP bridge (including custom GPT Action wiring) is on the ChatGPT page — the setup is identical.

When aarch64 support ships.

Once Q CLI ships aarch64 support, the install is one command — identical in shape to the Gemini and Codex setups. The block below shows the expected form. Do not run it today; the command will fail on aarch64 hosts.

# When Q CLI supports aarch64:
q mcp add robot-md \
  -- npx --yes robot-md-mcp ./ROBOT.md

# Then start Q and ask:
q chat
> what can this robot do?

This page will be updated and the copy button enabled once the integration is verified on aarch64 hardware. Watch robot-md issues or aws/amazon-q-developer-cli issues for status.

What works via Amazon Q.