To-dos

✅

No to-dos yet

✨
What can I help you with?
Documents, open-source deployments, new apps — all start here
Ctrl+Enter to send
🖥️

No apps yet

Use the “+ New app” button at the top left to create your first one.

New here? Open the official default app from the sidebar or from Chat and just ask how to build and publish an app from scratch.

Ask default →

Published apps

🖥️

No apps released to production yet

Explore

Shared experiences
Posts filed under “App”: the app that came out, together with the process and attachments.

Schedule

At the time you pick, we start a new chat for you and send your prompt into it — exactly as if you had typed it and hit send.
Spread your scheduled tasks across the day rather than stacking them on one moment — that is what keeps them clear of the 5-hour usage limit.
ID Title Status Runs at History Prompt review Actions
⏰

No scheduled tasks yet — create one

App settings

Basics
Repository
Domain
Database
Special accounts
Deployment
Android app
Basics
Required — how your app is described.
Private by default. Once enabled, apps successfully released to production become visible to other users.
Used on the app card — a 3:2 landscape image works best. You can also paste an image file or screenshot here.
Repository *
Required — add at least one repository.
Domain *
Required — pick from the domains managed by admin; ones reserved for you come first, then shared ones. The same root domain serves both test and production.
Database
Optional. Multiple entries are supported — pick an environment, then configure it.
Special accounts
Built-in / reserved accounts such as admin. A new app gets an admin account automatically, with a random 16-character password; edit it or add more. These are environment-independent and ship alongside the apiserver’s official special_accounts config at deploy time.
Deployment settings
Optional. Set deployment parameters for your app; multiple services (apiserver, web, …) are supported. These are environment-independent.
Android app
Read-only. The Android project is created by AI in chat; the package name and signing key are generated and kept by the platform, so they cannot be edited here. Preview builds a debug APK you can install by scanning the QR code; publishing builds a signed release APK.
The app identity on the device. It is fixed at the first build and cannot change afterwards — a different package name means a different app, and the old version will not be upgraded in place.
A lost signing key cannot be recovered: a package signed with a different key is treated as a different app and refuses to upgrade, forcing installed users to uninstall and lose local data. The platform keeps a copy — keeping your own backup somewhere safe is strongly recommended.
Build history
Android packaging runs triggered by preview or publish. Successful runs offer a direct APK download; failed ones show the reason.

API keys

Name API keys Last used Created Actions
🔑

No API keys yet

My MCP servers

Paste an mcpServers JSON config, optionally with Python scripts as the implementation. Every MCP server is loaded automatically inside this account’s chat container. Inside the worker container an MCP server runs commands as you — never import a config you don’t trust.

MCP servers
Name Description Content Created Actions

My skills

Import your own Claude Code skills, one at a time. Every skill is loaded automatically inside this account’s chat container. Scripts inside a skill package run with your own permissions — never import something you don’t trust.

Skills
Name Description Content Created Actions

Store

Pick the plan that fits you — upgrade any time, or activate with a redeem code.

Support tickets

Something wrong? Open a ticket and we’ll take it
For platform issues, account and quota problems, or anything that needs a human.
My tickets
support_id chat_id status type desc detail Created
Other ways to reach us

Purchases

Order Item Amount Type Status Expires Purchased Details

Works

Assets, reference sheets and progress live in the work, so any chat can pick it up

Cloud drive

Every file you generated or uploaded across your chats, newest first.

Marketing channels

Record the marketing accounts you run on each content platform. When building a campaign or writing a LinkedIn post, an X thread, a TikTok script or a newsletter, the agent reads this directly instead of asking you again about positioning, audience and conversion path. It comes in two layers: the shared setup is filled in once and used by every platform, and each platform card below only holds what actually differs there. Platforms you leave blank get no plan — fill them in first, then ask. One account per platform for now, all entered by hand.

OKR