Some limits are set by whoever runs your Alpha. Those are marked “(default)”, and your Alpha may use a different value. Admins can see the turn length and publishing limits in use on the Server tab of the Admin dashboard. If you don’t see Publish, Routines or the mic in the composer, that feature isn’t turned on for your Alpha, and its limits don’t apply to you.
Sessions, sharing and search
Each session runs on its own machine. These limits apply to each session, and to how you find and share sessions. Sleep, wake and reset explains what a sleeping machine keeps.Chat
These limits shape what you send and how much can wait its turn. Queue, steer or stop and The composer cover the features themselves.Files
Files reach the session’s machine as uploads, and leave it as downloads. Files and uploads and File viewers cover both.Database
The Database tab applies the same limits to your session’s database and to a production database. Browse, edit and query data shows where each one appears.Publishing
Each published app runs as its own service with its own versions. Publish your app and Manage a published app cover the flow.Routines, setups and secrets
These limits count across your whole account, not per session.Routines
Routines covers timetables and runs.Setups
Setups covers building and sharing them.Secrets
Secrets owns the naming rules and reserved names.Skills, MCP servers and agents
Skills, MCP servers and Try it each cover their feature in full.Next steps
Troubleshooting and FAQ
Fixes for the messages above, plus the failures that have nothing to do with a limit.
Sleep, wake and reset
What keeps a machine awake past the idle time, and what survives a reset.
Monitor and troubleshoot production
Spot an app running out of memory or slow to start before your users do.
Admin dashboard
Where admins see the turn length and publish counts this Alpha runs with.

