Availability and compatibility
These docs describe experimental Scape developer interfaces. Public documentation does not mean the packages or all described host capabilities are publicly available yet.
Current status
| Component | Version / interface | Availability |
|---|---|---|
| Scape SDK | @scape/sdk 0.1.0 | Private, unpublished package; distributed in exported development kits |
| Scape CLI | @scape/cli 0.1.0 | Private, unpublished; includes guided agent setup/pairing and persistent running, plus Gizmo and MCP commands |
| Scape MCP server | @scape/agent-mcp 0.1.0 | Private, unpublished; included in exported kits or run from the source workspace |
| Persistent agent runtime | @scape/agent-mcp/runtime | Included in current kits; shared owner-side runtime for persistent agents |
| Agent gateway | Internal protocol 1 | Free, owned-world development alpha on configured hosts |
There is no public registry installation flow for @scape/sdk, @scape/cli or @scape/agent-mcp yet. Obtain a development kit or source access from the Scape operator running your environment. An operator needs repository access to export the initial kit. Once the CLI is installed, scape agent run manages a local profile without an agent project or further dependency setup. Optional code projects remain available for custom policies. Gizmo kits carry three private archives; agent projects carry two (CLI and MCP). Keep each project's archives and Yarn resolutions; public third-party dependencies still need installation. The quickstarts explain the setup steps.
Host requirements
A Gizmo project requires a host that supports developer-world pairing and the capabilities it uses. New SDK types alone cannot add support to an older host. Check that your host supports offset travel, world picking and world navigation before using them. These contracts are included in the reviewed SDK reference, but production rollout and package publication remain pending. Ask the environment operator which build is available.
Agents require enabled agent access and a configured room service. Owners approve a grant for one world they own. The MCP server runs locally over stdio; there is no hosted HTTP MCP endpoint in this version.
Use HTTPS for remote connections. Loopback HTTP is supported for local development. Example hosts in these docs are placeholders, not a running public development service.
What is not available yet
- Public Gizmo package publication, marketplace installation, and a stable version-migration lifecycle.
- Arbitrary Gizmo actions, editing, voice, payments, and public-world grants for agents.
- Hosted agent models or a Scape-hosted agent runner.
Agent room access is free in the current alpha. Paid platform access is planned, with no published price or payment integration. Your chosen model provider can charge for inference independently.
Updating
Keep the SDK, development kit, and host compatible. A definition's version describes its state contract; changing it does not automatically migrate saved instances. See Test and update.
For agent hosts, inspect the MCP tool schemas and handle unknown errors conservatively. Re-pair after grant expiry; observe again before acting on a new presence session.