Блог

Как създаваме и поддържаме Mythex – включително нещата, които се объркаха – и какво ново има в продукта.

Инженерство

Как е изграден и как работи Mythex, включително какво се счупи и как го поправихме.

  • A Failed Republish Never Deletes a Working Backend — A failed republish could delete an app's live API, or leave its broken new version running. Three fixes to how Mythex undoes a publish that goes wrong.
  • Alerts That Fire Once, Not Once per Server — A once-a-day alert reached us five times in one afternoon. Why in-memory dedupe breaks with two servers and a deploy, and how shared state fixed it.
  • Moving to Bigger Workspaces Without Making Anyone Wait — A quarter of our workspaces were stuck at 1 GB after we moved to 2 GB. Our first fix made one person wait seven minutes. What we changed, and changed again.
  • Billing Databases by What They Actually Use — We used to estimate each app's database cost, and the estimate was wrong both ways. Now every database is billed from measured usage, hour by hour.
  • Catching Apps That Crash Right After Publishing — Three publishes passed our health check while their API crashed seconds into every boot. The cause: counting crashes in a list capped at five entries.
  • Keeping Image-Heavy Agent Turns Within Memory — An agent turn that kept looking at catalogue scans ran out of memory at 952 MB. Three separate causes, each holding images too long, and how we fixed them.
  • Keeping Long Agent Turns Inside the Context Window — Our sub-agents could grow until the model refused them, stop early to save room, or miscount tokens in Russian. Three fixes that let long AI work finish.
  • Keeping the Chat Alive When a Phone Sleeps — Phones sleep, switch tabs and drop networks mid-build. Two bugs made Mythex's chat stall or show half a reply afterwards. How we found and fixed both.
  • How One Heavy Chat Could Take Our API Down — On September 28 both of our API servers ran out of memory at once. The first fix was more memory; the real one was loading chat history by size, not count.
  • Pressing Publish Twice Now Publishes Once — Three publish requests for one app arrived 84ms apart and each ran a full deploy. How we made the database decide who publishes, and told the others the truth.
  • SEO Lessons From Fixing Our Own Site — Duplicate FAQ markup, the wrong thumbnail in Google, template pages nobody clicked and a path our edge refused: what we found on mythex.ai and fixed.
  • Static Sites Now Stay Up While They Republish — Republishing a static site used to empty it before uploading the new build. Now the old site serves until the new one is in place, and changes show in seconds.
  • The Out-of-Memory Crash Hiding in a Progress Label — Our AI agent ran out of memory writing one large file. The cause wasn't the model or parallel sub-agents — it was a status label resent 41,000 times.
  • The Missing Swap File That Froze Our Servers — A production server stopped answering without crashing — no out-of-memory kill, just page-cache thrash on a box with no swap. What happened and what we changed.
  • Waking Up Databases Without Dead Connections — A published app waking from sleep held its first request 10–12 seconds on database connections that died while it slept. How we got it to 2.3 seconds.
  • We Were Rate-Limiting Our Own Services — Our API's per-address rate limit treated our own services like one busy person, and in production they started getting 429s. How we found it and fixed it.
  • Why We Moved Mythex's Servers to ARM — Once heavy work moved into per-project sandboxes, our servers used a third of their memory. Smaller ARM instances cut costs by about 30%. Here's how.
  • How We Got Deploys Down to Zero 502 Errors — A watchdog racing our deploys and a load balancer that noticed too late: how we found both, fixed them, and measured deploys from 10 502s to zero.

Продукт

Какво ново има в Mythex и защо го направихме така.

  • 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.
  • Custom Domains on Mythex: Buy One or Connect Your Own — Pro apps on Mythex can run on your own domain. Buy one inside Mythex or point a domain you own at your app with a CNAME. Steps, renewal, and limits.
  • Dictate Your Prompts with Voice Input — You can speak your prompts to Mythex instead of typing them. Click the microphone or press Alt+V, check the text, and send. How it works and its limits.
  • Fix with AI: One Click When a Publish Fails — When publishing fails, Mythex now says what happened and offers Fix with AI: the agent reads the build output or your app's logs and fixes the project.
  • Generating Images Right in the Chat — Ask Mythex for a hero image, an og:image or a logo mark and it draws one in the chat, then puts it in your app only when you say so. Here's how it works.
  • GitHub Sync and Export: Your Mythex Code Is Yours — Everything you build on Mythex belongs to you. Sync a project to GitHub, download it as an archive, or import one back in. How each works, and the limits.
  • Mythex Now Remembers Who You Are and How You Work — Memory, About you, project and workspace knowledge, and past-chat search: Mythex stops starting from zero in every chat. See, edit or turn off all of it.
  • Plan Before You Build: How Plan Mode Works in Mythex — Plan mode lets the Mythex agent work out an approach before it edits anything. Read the plan in its own tab, then press Build. How it works and when to use it.
  • Publish Errors Now Say What Happened, in Plain Words — When a Mythex publish fails, you now get one plain sentence about what went wrong, plus Fix with AI and Try again — instead of raw hosting output.
  • Your Published App Now Stays Up While You Republish It — Republishing used to take a live Mythex app offline during the build. Now the previous version keeps serving until the new one is ready, plus two more fixes.
  • Secrets and Environment Variables Without Pasting Keys in Chat — When the Mythex agent needs an API key, it asks through a secure card instead of the chat box. How project secrets and env vars work, and how to rotate a key.
  • Start From a Template: A Written First Prompt for Your App — Mythex templates give you a starter prompt tuned for a kind of site or app. Pick one, press Use template, and the agent builds a first version you then refine.
  • Sub-Agents You Can Open and Read — When the Mythex agent splits a complex task into nested runs, each shows up in chat as a row you can open and read. How it works and what you control.
  • 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.
  • Test Your App in the Browser with One Command — Type /test and Mythex clicks through your live preview like a user would, takes screenshots, and reports what broke in chat. How to use it and when.
  • Why Every Mythex App Gets Its Own Database — Each Mythex app that needs data gets its own Postgres database that sleeps when idle. Why we chose one database per app over a shared one, and the trade-offs.
  • Workspaces and Inviting Your Team — Mythex projects live in workspaces. Invite teammates by email, work on the same projects, and pay no per-seat fees. How owners, members and billing work.

Компания

Бележки от екипа.

  • Introducing Mythex Guides and the Mythex Blog — Practical guides on building apps and websites with AI, honest tool comparisons, and an engineering blog about how Mythex is built — including what breaks.
  • Mythex Now Speaks 12 Languages — The Mythex marketing site is now in 12 languages, from Português and Deutsch to हिन्दी, 日本語 and العربية. Pick yours from the footer.

Mythex · Цени · Въпроси · Ръководства · Блог · Приложения · За нас