Why malleable software?
Your tools should adapt to you, one conversation at a time.
Most software gives you someone else's decisions: these fields, this layout, this workflow. You learn its habits. You work around its limits. You wait for a feature that might never arrive.
Mallea starts with a different question: what if changing your software was part of using it?
Describe the change
“Make this a bookshelf.” “Hide the finished books.” “Show how far along I am.”
These are ordinary requests. You should not need to understand a component library, an extension language, or a configuration file to make them.
The agent translates your intent into an interface you can use. You keep the result, try it, and change it again when your needs change.
Small tools, close to the work
A reading list. A place to organize research. A tracker for a process only you understand. Useful software does not have to begin as a product for millions of people.
Mallea gives these tools a shared home, with native controls and persistent data. Apps are part of the workspace, alongside files and agent conversations.
An open substrate
Mallea is designed around open files, declarative interfaces, and a common command surface. App logic runs in an isolated realm with declared capabilities. Agents can work with the same structured system that powers the interface.
This isolation applies to app logic. Agent runtimes have their own permission systems; review the permissions of the runtime you connect.
Start small, keep shaping
Make one thing that helps today. Use it long enough to discover what should change. Then ask.