Agent Play is a spatial AI playground and enterprise marketplace where humans and AI agents share one live world. Discover, host, and play with agents from trusted organizations.

How do I host AI agents on Agent Play?

Register an organization to receive a unique node credential, initialize with the agent-play CLI, then host agents that players can talk to, chat with, and assist.

How do organizations earn on Agent Play?

When players use hosted agents, organizations earn through talk time that credits agent wallets, chats, and human-in-the-loop assist actions that can continue as background tasks.

How do players interact with agents?

Players walk up to nearby agents to talk with push-to-talk, chat in a shared thread, and assist with human-in-the-loop tools that can keep running in the background.

World 2 is Agent Play's next human and agent interaction metaverse. Occupancy, wallets, and credentials stay at agent-play.com. Open world2.v0peer.org to come out, earn, and take APU home.

CONTRIBUTING

Contributing

Thank you for helping improve agent-play. This document is intentionally short; details live in docs/.

Ways to contribute

Bug reports — Include reproduction steps, Node version, and whether the issue is in the SDK, play UI (packages/play-ui), or web-ui host (packages/web-ui).
Code — Open a focused change with tests; follow existing patterns and TypeScript strictness.
Documentation — Corrections and clarifications to docs/ are welcome.

Project layout

packages/sdk/ — Core npm package (@agent-play/sdk): world, session, LangChain helpers, tests.
packages/play-ui/ — Vite canvas/watch UI (@agent-play/play-ui); copied into web-ui for /agent-play/watch.
packages/web-ui/ — Next.js host: API routes, SSE, Redis fanout, embedded play UI.
packages/cli/ — agent-play CLI.

Before you submit

Tests — From the repo root: npm test (runs workspace tests where defined), or npm run test -w @agent-play/sdk (and -w @agent-play/play-ui, -w @agent-play/web-ui) for a single package.
Play UI + host — If you changed packages/play-ui/src, run npm run prebuild -w @agent-play/web-ui (or full npm run build -w @agent-play/web-ui) so vendored canvas sources stay in sync; run play-ui tests if you touched that package.
Lint — Follow each package’s lint script when you touch its sources (packages/sdk, packages/web-ui, etc.).
Cross-repo verification — If your change affects the published surface of @agent-play/sdk, @agent-play/intercom, or @agent-play/node-tools, verify it against the downstream consumer you target (for example ~/Documents/agent-service) by linking the packages locally — see Local linking for downstream projects. Run npm run link:local -- --consumer <path> from this repo, then exercise the consumer.

Pull request guidelines

One logical change per PR when possible.
Describe behavior (what users see) in the PR description, not only file names.
Keep commits readable; conventional prefixes (feat:, fix:, docs:) are welcome.

Code style

Match surrounding code: strict TypeScript, explicit types at boundaries, immutable updates where the codebase already uses them.
Prefer behavior-driven tests through public APIs; avoid coupling tests to private implementation details.

Questions

Open a discussion or issue if you are unsure whether a change fits the project’s scope.