Technology · Apps
Apps you use, change, create — and share.
Everything on Zaelar's canvas is an app — the agenda, the music player, the browser, your lists. Each one is a self-contained folder with its own UI, its own data and its own logic. Your agent opens them, operates them, and some keep working quietly while you're not looking.
Three ways to get an app
- Use a built-in one. Zaelar ships with native apps — agenda, music, video, browser, messaging, files, photos, maps, markets and more — ready from the first minute.
- Fork one and make it yours. Ask for a change to any built-in app and you get your own fork: it shadows the original, while the original keeps receiving engine updates underneath it — so going back is always one step away.
- Create a new one. Describe what you want by voice or text — a tracker, a dashboard, a tool for your job — and a Brain Worker writes it, validates it and puts it on your canvas.
Your apps are yours to share
An app is a plain folder: a manifest that declares what it can do, a UI script and its logic. Nothing ties it to your account — hand the folder to someone else, they drop it into their apps folder on a self-hosted install, and their agent discovers it on its own and drives it by voice exactly like yours. The data stays behind: it lives in a separate folder, so sharing an app never shares what you stored in it.
Three separate things happen to an app, and Zaelar never confuses them. Operating its data — adding a task, marking something done — is instant, handled by the FlashBrain calling a declared action. Creating or modifying its code — a brand new app, or changing how one works — is real engineering work, done by a Brain Worker that writes and validates code. Opening, closing or deleting an app on the canvas is a lightweight, deterministic action — deleting always asks for confirmation first.
Nothing is built or rewritten without your explicit yes, and the gate sits at the single door every background worker starts from — not in the voice turn, not in the text channel, not in any of the paths that can reach the generator. A rule each caller has to remember to apply is not a rule.
Refreshed by events, never polling
An app's card re-renders exactly once when its data actually changes — pushed over a live event stream, not a timer. Nothing on the canvas polls.
Some apps keep working while closed
An app can declare a background cycle — a periodic tick that runs whether or not its card is open. That's how messaging stays triaged and memory stays current even if you never opened the app: it keeps reading its connectors, deciding what matters, and writing it to memory, isolated from everything else so a stuck app never affects voice or another app.