Agent guide
Registration, packing, upload, receipts, evolution, errors and fallbacks.
FOR CREATORS
Bring your apps to cool*
cool* on thatscool.app accepts existing app source through its public submission workflow. Your agent prepares and uploads it, then returns playable public previews.
The .app address does not identify a hosting provider. You do not need a Vercel deployment or hosting account to submit.
Tell your agent:
Go to https://thatscool.app and follow its instructions to submit our apps.STEPS
Your agent leads. You stay the owner.
- 1 · Ask your agentIt prepares, uploads and submits your apps. No sign-in is needed first.
- 2 · Preview your appsAfter a successful complete batch, you get a private claim link to a page of public app previews. Share only the public preview links.
- 3 · Sign in to claimSign in with Google and explicitly claim the creator to save, manage and see private analytics. Your builder gets no automatic access.
Your agent may ask once for an owner email, or use one it is confident is yours; it is optional and never a prerequisite. The email is only an unverified delivery hint for an attempted provisional welcome with your private link, not proof of ownership or a delivery guarantee. The dashboard shows observed play time from your apps; no observations means unknown, not zero. Advanced: set up a creator while signed in
REFERENCE
Details when you need them
Hosting boundary and capabilities
Supported
Self-contained HTML and JavaScript, Canvas, WASM, and packaged media inside an opaque sandbox.
Needs a fallback
Declare device capabilities: motion/fullscreen and brokered microphone are supported; camera/location need review. External network calls and embedded frames/forms remain unavailable. Managed room services use the trusted player; premium saves and phase rooms require an app grant.
Editable source stays private to platform review. The accepted build and declared public metadata are public. Validation confirms the transport contract; it is not a security, quality or Main-promotion certification. See the manifest for current capabilities and limits.
Likes, sharing and profiles
Share the exact public preview link from your receipt or dashboard. Like and share actions are owned by the host and the optional read-only profile SDK; provisional previews do not show invented counts. Read share links and identity rollout for what is connected today.
Premium app capabilities
Opt-in apps can use larger asset packages, private save slots, counts-only analytics and sealed multiplayer phases. Give your agent an early-access subscription key to request the app upgrade automatically; existing grants also work. Paid model budgets remain separate.
Agent tools and helpers
Dependency-free submitter
Download the submitter, trace helper and validator together for batch preflight; premium items also need the streaming helper and an existing grant or owner-provided subscription key.
Manifest and schema
Endpoints, capability declarations, limits and the upload packet shape.
Example package
A complete small packet and a local preview tool.
Reference library
These documents explain the canonical format and approved implementation patterns. The agent submission guide governs public provisional transport; historical Git steps apply only to repository collaboration. Current spec version: see the manifest.
Port likes, sharing and profiles
Actual host integrations, uploaded-app profile/activity hooks, and the current social-count limits.
Creation debugging and agent tracing
Correlate attempts, request IDs and safe failure reports; mark builder tests.
Creator quickstart
Let your agent upload apps, preview them first, then sign in to claim them.
Microphone and device permissions
Declaration, trusted player consent, microphone and motion bridge, local and hosted test recipes.
Optional creator email reports
Opt-in cadence, ownership and privacy contract; delivery is disabled unless runtime capabilities explicitly enable it.
Conditional verified-destination report pilot
Disabled pilot implementation, finite limits and activation prerequisites; configuration is not a delivery guarantee.
Education invitation and public challenge sharing
Explicit parent consent, exact revision public-target review and compact links; activation remains separate.
Private group reporting
Bounded member reports and authenticated operator disposition; no private content exposure.
Education integration starter
Exact SDK, standard fallback, private board round and offline parity acceptance guide.
Education platform services
Private class groups, exact collection grants, capability policies and bounded offline contracts; discover runtime availability.
Retained menu alias correction
Exact-baseline minimal source patch; preserve existing Main graphs and verify candidate behavior.
Identity backend architecture
SDK presence, live capability discovery and staged backend controls.
Creator account authorization
Creator ownership and premium mutation requirements; current availability and enforcement come from runtime capabilities.
Profile SDK 1.8 integration
Implemented optional read-only client contract; check runtime availability before hosted acceptance.
Exact current curated build discovery
Pinned public retained build manifests, source limits and candidate publication boundaries.
Identity onboarding and runtime discovery
Optional SDK integration, live capability checks, guest fallback and acceptance gates.
Shared profile contract
Published projection schema, exact preference values and privacy boundaries.
Authentication direction and rollout
Guest-first Google linking, capability discovery and separately gated creator ownership.
Builder model provenance
Per-revision model claims, known model registry, unknown identity and self-reported attribution across upload transports.
Agent interfaces: WebMCP and MCP
Shared tools, browser fallback, authentication, protocol versions and engineering boundaries.
Testing without model dispatch
Local fixtures, hosted no-dispatch configuration and separately authorized live acceptance.
Room recovery, rematches and departures
SDK 1.5.0 room discovery, same-room rematches, explicit departure semantics, generation guards and engineering review invariants.
Image rooms v2
SDK 1.7.0 parallel chains, private missions and daily async rooms; additive versioned contract.
Image room dynamics
SDK 1.6.0 recovery, authoritative turns, private awards and opted-in reminders.
Image room snapshot examples
Complete sanitized engine fixtures for both games, active/waiting players, generation and reveal.
Managed image calls
Public capability discovery, the selected phone image profile, the versioned SDK, exact grants and request shapes, private media, budgets and error behavior.
Existing party/1 room trace
A sanitized real local Worker trace confirming event, acknowledgement and moderation version semantics.
Premium app services
Opt-in resource profiles, sealed rounds, private saves, count-only analytics, larger streaming uploads and activation boundaries.
Compact public sharing
Short app-scoped links, saved settings and checkpoints, readable invitations, expiry, resource limits and migration.
Share-link migration audit
All 40 public Rifflets, legacy formats, migrated producers, compatibility and test scope.
Realtime rooms and party games
Managed shared rooms, host/projector and phone controllers, isolated transport, limits and reconnect contract.
Submit with one agent prompt
The authoritative no-Git workflow for registering, packaging, publishing, tracking and evolving public provisional Rifflets.
Upload transport reference
Package a complete experience, use a private creator key, and publish its provisional isolated preview.
Contributor start here
Choose your path, follow the agent reading order, and understand repository access and review.
Rajeev’s agent onboarding
Inventory and submit all apps through RCF, a validated pilot, and automatic public provisional packages; named repository access is optional.
Repository collaborators
An agent-ready prompt and contribution workflow for approved builders with named repository access.
Third-party contributions
An agent-ready prompt for adapting and publishing new Rifflets or existing apps through the public provisional route.
Canonical Rifflet Spec
The versioned contract: experience quality, discovery metadata, common components, analytics, security and hosting.
Content onboarding
Turn existing content into a Rifflet, verify its behavior, and package a focused public provisional submission.
Platform merge plan
A proposed path for bringing the Rifflet lab and the original Riff platform together, with clear responsibilities.
Agent merge runbook
A step-by-step reference for evaluating compatibility, coordinating changes and preserving release and data integrity.
Platform coordination
The questions, interfaces and decisions to resolve with Riff platform maintainers before integration.
Rifflet framework
Approved shared lifecycle, runtime and common-component patterns for playable experiences.
Rifflet protocol
Public version, content and lineage semantics used by the platform.
Analytics contract
Meaningful event semantics, traffic classification and privacy boundaries.
Illustrated covers
Cover generation, animation, accessibility and reduced-motion requirements.
Advanced content starter
A practical starting contract for building an interactive experience.
Run a platform tool
Platform tools · browser and agents
The same tools are available through WebMCP here and MCP at /mcp. Read the testing contract before testing model features.
Loading tools…