Build an app just by describing it.

A "describe it and it builds" tool — bounded so it can't go off the rails.

Think of it as a private, on-brand version of tools like Base44 or Lovable, but living inside the OS. You describe a small app — a planner, a tracker, a checklist — and it generates one that reads your actual CTOx data and runs right in the portal. The difference from a generic app-builder is the important part: every app it produces can only ever do what the OS allows. It runs in a sealed sandbox and can only reach a small, approved set of your data. That boundary is the whole point — it's why we can let apps go live automatically without a person reviewing the code each time.

Staff dashboard, Operations section.

Go to: Dashboard→Operations→Mini-apps  (os.ctox.com/operations/mini-apps).

Building is staff-only — it's for the internal team, not our members. Any employee (marketer, consultant, facilitator, admin, superadmin) can build. Members and prospects never see it. The one page does both jobs: the box at the top is where you describe and build; the table below lists every app and its recent activity, with controls to pause or stop any of them.

Please actually do this by hand — build one, open it, use it, then stop it.

1. Open Operations → Mini-apps
   Sign in to the dashboard and head to the Mini-apps page. You'll see the "Describe the app you want…" box.
2. Describe an app (or click an example)
   Type what you want in plain English — a sentence is plenty. There are one-click example prompts under the box if you'd rather start from one.
3. Hit "Build it" and wait ~1–2 minutes
   Behind the scenes it writes the app, checks it against the sandbox, and fixes its own errors (up to three tries). The build log shows how many attempts it took. Don't refresh.
4. When it says it's live, click "Open the app →"
   The app opens right there in the portal, running in its sandbox.
5. Actually use it
   Poke at it like a real user. Does your real CTOx data show up? Do notes save — and are they still there after a reload? Does anything feel broken or confusing?
6. Find it in the table and try the controls
   Back on the Mini-apps page, your app is in the list with its 24-hour activity. Try Pause then Resume. Kill removes it for good — that's expected and fine for test apps.

Copy one, tweak it, or write your own. Small and specific works best.

Run through this for each app you build, then send us the rundown.

• Did it build? If yes, how many attempts did the build log show? If it failed, what did the error say?
• Does it actually work? Real data shows up, actions do something, and saved notes survive a page reload.
• Does it look right? CTOx orange, clean, readable on your phone (open it on mobile too).
• Anything broken? Dead buttons, empty lists that shouldn't be, confusing wording, or an error message.
• Do the controls work? You could Pause, Resume, and Kill it from the table.
• If you asked for email: it arrived, went to you (never anyone else), and carries the [Mini-app] subject + the "automated message" banner.

The boundaries, in plain terms. This is why it's safe to let apps go live on their own.

Known limits while it's new — set expectations: the data it can use is exactly the list above (events, your RSVPs, your profile, a private notes store, email-to-self). No SMS, payments, or Slack yet. Any staff member can open any live app, though the data it shows is still only ever the opener's own — per-app audience limits are coming. And it's brand new, so expect rough edges. That's what this test round is for.

Every app has a stop button. You're never stuck with one.

Two more safety nets run automatically: a global kill switch can dark-frame every app at once if we ever need it, and an hourly watchdog auto-pauses any app that starts throwing an unusual number of errors or running up cost. There's also a soft cap of 12 builds per person per hour so a stuck loop can't run away.