Where is my AI application's code stored? Your tool wants to keep it too

In August 2026, Cursor became the host of the code it writes and removed the final preparation step before launching an agent. The missing step is paid for elsewhere: where your software lives stops being a neutral choice.

Where is my AI application's code stored? The answer depends on the tool and has just changed. Cursor opened its own hosting platform, Origin, on August 17, 2026, then on August 27 enabled starting an agent from nothing, with the tool creating the place where code would live (Cursor release notes).

The last hurdle disappeared

Until now, even the most automated tools required preparation: opening a code-hosting account, creating an empty location, connecting it to the tool. This stopped nontechnical project owners cold, understanding neither the vocabulary nor the purpose. Origin's beta is open to paying subscribers except organisations whose administrator disables it: the default favours the host. Cursor removed that step, and its release notes document other accelerations that month: agents starting three times faster, subagents on their own machines, a dedicated command for long goals. The tool targets professionals, but the direction applies across the market: first-day technical friction is disappearing everywhere.

What the publisher gains alongside you

When the tool creates the location, it becomes its host. Your software is born with whoever writes it, deployment integrations already connected. Nothing illegitimate about that, and leaving remains possible. But the exit question, previously asked before starting, now comes afterward: when you want to leave, you need to know the door. Summer 2026 reminded us that doors matter, with two platforms closing within weeks and users told to export within imposed deadlines. A tool hosting your code concentrates two dependencies, writing and storage, in one place, and that concentration costs you when leaving.

Three questions before the first line

First, locate the copy you control, the one with you or in an account in your name, accessible without the tool. Second, count the clicks and conditions between you and that copy, noting whether the free plan permits it. Several mobile application builders reserve export for paid accounts, leaving a free-started project captive at the worst moment. Third, describe what happens to the running application if the account closes, code on one side and customer data on the other, since they do not always leave together. Those answers fit on a sticky note and decide what remains if the tool disappears.

The opposite choice

Maestro takes the opposite approach: your project lives on your Mac, code and documents in a folder you open without us, with version history on the same machine. Online backup exists, is optional, and points to your own GitHub account, not a Maestro server. None of our servers sees your projects. This choice costs something: setup requires installing a desktop application where a browser tab suffices elsewhere, and you are responsible for your backups. We detail what the machine keeps and what leaves on our data page. The choice is hard to defend in a demonstration and easy two years later when the tool that wrote your software changes hands, price, or name and your work does not move a byte. When you want a developer to take over, you hand them a complete folder they open on their machine.

Check in ten minutes

Open your current tool and find the export button without triggering it. If it exists, note which plan it requires and what it produces: a compressed file, a push to your hosting account, or a page asking you to contact support. Perform a real export once while the project is small and store it with your accounting documents. An export tested in month one is worth more than a guarantee in terms of service. Repeat twice a year, and when the tool changes owner or price, you will leave without negotiating.