Blog / Product

The Mythex Agent Now Knows What Mythex Can Build

Ask Mythex for an iPhone app or an always-on bot and the agent now says plainly it isn't available, offers the closest thing that is, and waits for a yes.

Mythex Team · 2026-09-29 · 3 min read

Mythex's agent now knows what Mythex can and can't build and publish. If you ask for something it can't run — a native iPhone or Android app, a desktop app, a browser extension, a bot that has to stay connected all the time — it tells you plainly, offers the closest thing Mythex does, and builds that only once you agree. Before, a request like "make me an iPhone app" could get a project scaffold you could never run, publish or put in a store.

What it does

The agent's instructions now include a short, factual description of the platform, in Build, Plan and Ask modes alike.

What Mythex builds and publishes: things that run on the web.

  • Websites and landing pages
  • Full web apps: dashboards, stores, SaaS products, internal tools, browser games
  • Backends: APIs and servers in Node, Python, Java, C# and more, published from a Dockerfile
  • Any of those with a database, file storage, or a website and an API together

All of it works on phones through the browser. Scripts and command-line tools are fine to write and run in your workspace; only web apps and servers can be published.

What isn't available:

  • Native mobile apps (coming soon). No iOS or Android app, App Store or Google Play release, APK, IPA, React Native, Expo, Flutter, Swift or Kotlin project.
  • Desktop apps such as Electron apps or installers, browser extensions, and games built on native engines such as Unity or Godot.
  • Anything that has to keep running with no incoming requests. A published server sleeps when no requests come in and wakes on the next one, and there are no scheduled jobs.

That last point is the subtle one. Bots and integrations work fine on Mythex when they're driven by incoming requests — webhooks, such as a Telegram webhook, Slack events, Discord interactions or Stripe events. A bot that only connects outwards and waits (a Discord gateway bot, a Telegram bot that polls), or a job that runs on a timer, stops once the server goes idle.

Why we built it

A model can't know on its own what a particular platform can run. Without being told, it did what it would do anywhere: asked for an iPhone app, it scaffolded one in Expo or Flutter. That looked like progress and ended at a project that couldn't be run in the workspace, published, or submitted to a store.

The better answer is a straight one, early: this isn't available here yet, and here's what is.

How it behaves

  1. You ask for something that isn't available — say, "build me an Android app for my gym".
  2. The agent says so, briefly, and offers the closest thing Mythex does: for example, a mobile-friendly web app your members open from their phone's browser, a web version of a desktop tool, or a webhook-based bot instead of an always-connected one.
  3. It builds only after you agree. Nothing is scaffolded before that.
  4. Pressing isn't agreeing. "Just do it anyway" or "I need the APK" gets the offer again, not a build. The agent never produces an app binary, a store build or an installer, however it's asked.

If you ask for a website or web app that should look good on phones, that's an ordinary build: the agent makes it responsive, with no detour.

How we checked it

We ran 25 requests covering both sides of the line, plus 3 follow-ups that insisted on the unavailable thing. Nothing native was scaffolded or run in any workspace. Every web app, API, webhook bot, browser game and script request was built normally.

Tips

  • Want an app on phones today? Ask for a mobile-friendly web app. Our guides on building a mobile-friendly web app and native vs progressive web apps explain what that gets you.
  • Want a bot? Ask for one that works through webhooks. What a webhook is covers the idea.
  • Need something on a schedule? That isn't available on Mythex today. If your task can be triggered by an incoming request instead, the agent can build it that way.

Limits

  • Native mobile apps are coming soon but aren't available yet, and neither is submitting to the App Store or Google Play.
  • The agent follows these instructions, but it's still a model. If it ever starts building something from the "not available" list, tell it to stop, or email support.

The full picture, with a guide for each kind of project, is in the docs under what you can build.

Keep reading

  • A Landing Page for Every Kind of Business — Search for a booking system for a dental clinic or a website for a bakery and land on a Mythex page written for that business, with a prompt ready to build it.
  • A Private Workspace and a Live Preview for Every Project — Every Mythex project runs in its own private cloud workspace with a live preview beside the chat. How it works, how to use it, and what to expect.
  • Auto-Reload: Keep Your Published App Running When Credits Run Low — Auto-reload buys Mythex credits when your balance runs low, so a long build or a busy published app does not stop at zero. How to set it up, and its limits.
  • Build Mythex Apps from Claude, Cursor or Codex — Mythex runs a remote MCP server: connect Claude, Cursor or Codex, and they code in your Mythex cloud sandbox with a live preview, database and publishing.
  • Checkpoints: Undo Any Change the Agent Makes — After every successful turn, Mythex saves a checkpoint of your project. Revert to any of them in two clicks, or edit an earlier message and try again.
  • Connect Gmail, Google Sheets and Slack to Your App Builder — Mythex Connectors link Gmail, Google Sheets, Slack, Notion and more to the chat agent, with no API keys in your code. How it works, setup, and limits.

Start building free · Templates · Docs