NanoClaw

Availability

The pinned release documents this integration once listed; it does not establish that the catalog entry is available. Confirm the listing in the platform before using a catalog installation route. The upstream integration guide describes the submission and its constraints.

Prerequisites

NanoClaw agents run in containers without the binary, so this route needs a self-hosted server reachable over HTTPS and its API key. A local-only inbox is not sufficient.

Setup when listed

ncl groups create --template engineering/agentfeedback

In the generated mcp.json, replace https://agentfeedback.example.com/mcp with your server HTTPS URL plus /mcp. NanoClaw refuses host.docker.internal, gateway.docker.internal and 172.17.0.1.

Supply Authorization: Bearer <key> through OneCLI gateway injection for the server host, or replace the generated placeholder header privately. Never commit a real key.

Verify

Start the group and confirm its AgentFeedback MCP tools connect. File a labelled setup report and read it from a client configured for the same server. A 401 points to the missing or incorrect bearer header; a connection failure calls for checking HTTPS reachability from the container.

If the listing is missing

Do not substitute a similarly named package. Follow the upstream guide for the integration's current submission path, or use a directly supported harness. Remove catalog packages through the platform that installed them, not agentfeedback uninstall.

Source and verification

Documented on 2026-10-09. This is upstream's recorded verification level, not a claim that every setup above was live-tested by this site.

Source: integration registry and operating guide, pinned at c7573e1.