Help Center

API keys are stored only in your browser's localStorage. There is no backend, no account, and no telemetry — keys are sent only to the provider baseUrl you configured, as part of the requests you make. See our privacy policy.

In Settings → Tools, add a YAML entry with a name, a description, and a JavaScript implementation. When the model calls it, Zod runs the code in a sandbox exposing sandbox.args and sandbox.ctx (persistent state, fetch, timers). Custom tools work in chat, the scheduler, and agent steps. Read the tools docs.

Declare MCP servers in Settings → MCP as YAML: a name, an HTTP url, and optional headers. Zod uses a built-in MCP-over-HTTP client (JSON-RPC initialize / tools/list / tools/call), so connected servers' tools appear in the agent loop. Read the MCP docs.

Yes. A service worker mirrors your state into IndexedDB and runs due crons — prompts or whole workflows — through the full agent loop even when the tab is closed, up to three concurrently. Results are written back and appear when you reopen Zod. One caveat: the browser itself must be open; fully closing the browser suspends the worker until it's next woken. Read the scheduler docs.

Go to Settings → General → Data. Export data (JSON) downloads your full zodagent state — sessions, memory, providers, tools, MCP, and scheduled tasks. Import data restores it and reloads the app. This is also how you move your setup between machines or between the web app, extension, and desktop builds.

If the docs don't cover it, the community forum is a great place to ask. Drop your question there and other users — and often the Zod Agent team — will help you out. Visit the forum.