Examples

Introduction

Each recipe builds one working thing from start to finish: the files to create, the code to paste, and a short note on why it works. The code comes from the demo apps in the repository (apps/api, apps/web, apps/desktop, apps/mobile) and from a SaaS app that already has its own login.

Start with the first recipe of your side (server or client), then add the others as you need them.

Server

• Let a tool call your own API: a tool that reaches your REST API with the caller’s identity, opt-in for one agent.
• Sign in with your existing session: reuse the login your app already has, with a cached identity lookup.
• Multi-tenant SaaS: tenant headers, skill layers, config tools, schedules and role variables.
• Borrow server models from a desktop app: lend your server’s models to local backends without lending the key.

Client

• Add chat to a React app: ChatProvider and ChatPanel with your session token, labels and links.
• Embed on any page: mount the whole web chat in a plain page with mountChat.
• Match your brand: map your design tokens onto the kit and switch light and dark.
• Tools that run in the browser: blocking and one-way client tools, drawn as a card.
• Voice in the browser: read aloud and dictation, with every Vite setting and the symptom it fixes.

Apps

• Desktop app with a local backend: a Tauri window that starts its own server.
• Mobile app with Expo: the chat in a React Native app.