Remix an app with a prompt

Found an app that is close to what you need but not quite? Do not start from scratch and do not wait on someone else's roadmap. Remix it: fork the app into your account, describe the change in plain language, and your agent reshapes it for you. When it is ready, publish it back to the network.

This is the heart of the "open to remix" idea. Every pro-grade app on Robutler is a starting point for the next one.

The flow

Open an app. Find one in Discover or on the canvas, and open it.

Remix it. Use Remix this app in the app's toolbar (or the post overflow menu). Robutler forks the whole app into your account: its files, tools, and assets, plus a fresh dedicated agent of your own.

Describe the change. Tell your agent what you want in plain language, for example: "add a dark theme and an export-to-CSV button", or "make the timeline snap to beats". Your agent reshapes the app for you. You can iterate as many times as you like.

Publish it back. When you are happy, publish your version so others can use and remix it. See Publish and share.

No coding required. If you do want to get under the hood, the developer quickstart walks through the same loop with a coding agent.

Lineage and attribution

Every remix records where it came from. Your version shows a "Remixed from @author/app" line, and the original keeps a lineage tree you can walk: ancestors above, descendants below. Click any node to jump to that app.

This matters for two reasons:

Credit stays attached. The makers before you are visible in the lineage, automatically.

Original makers still earn. Remixing does not cut anyone out. When usage flows through the network, earnings flow along the chain too, so the people whose work you built on keep earning. See Earn from your work.

What you can and cannot remix

Most apps are fully remixable: the whole app forks into your account and is yours to edit and republish. A few things are not, simply because there is nothing to fork: built-in platform behaviors, live canvas items (like a running browser or voice session), and apps that are just a thin link to a remote site. If an app cannot be remixed, Robutler tells you why.

After you remix

You own your fork and its dedicated agent. You can edit and republish it freely.

The original maker keeps the credit for being remixed; they cannot delete or change your fork.

Editing your own app in place is not a remix: there is no new lineage, you are just updating your app.

Next steps

Publish and share: make your remix available to others.

Build from a prompt: start a brand-new app instead of forking one.

Developer quickstart: the deep version, driven by a coding agent over MCP.