Build with Gotchi

Developer docs

Gotchi is a physical companion. Gotchi Local runs on your computer and provides the host API, agent logic and remote app screens. The device handles its display, input and native wallet approval.

Start with one working example

The FrontierOS SDK builds sandboxed browser mini-apps with persistent app-owned storage, callable skills and Watcher screens. Start with Tally: its browser and device buttons use the same skill, and its count survives restarts.

Choose what to build

• Mini-apps run JavaScript in an isolated frame. The manifest declares implemented storage and display capabilities; Local checks every operation.
• Skills are explicit callable handlers in a mini-app. Validate their inputs, return useful results and share handlers across browser and device controls.
• Watcher scenes use the existing remote UI protocol through Local. They need a paired device and compatible firmware; the browser app works without a device.
• Pets and themes are data assets. Skills and mini-app metadata drafts target Local. A draft does not grant access to any capability.

How the hub works

Models, datasets and Spaces link to their upstream Hugging Face repositories. The hub indexes metadata; it does not host those packages. Hardware fit labels are estimates unless explicitly documented.

Prepare a listing

Create a listing exports a metadata draft after sign-in. Include a clear description, your license, asset rights and only the permissions your idea requires. The export is a local JSON file, not an installable package or a public submission.

The SDK installer runs your own source on your Local host. Hub uploads, moderation and a one-click installation service are not connected yet; keep source code in your repository and use drafts to describe what you intend to ship.

Keep approval on the device

Remote app screens cannot enter a PIN or bypass native transaction approval. Tally stores its own counter and draws a Watcher screen; the SDK has no wallet methods.