Lucidos

Lucidos builds and runs the apps and automations you describe. Describe one in chat and you are using it seconds later, in the same window, wired to your own data. Ask for a change and it changes while it keeps running. No build step, no deploy, no separate service to stand up.

If you can describe it, it exists

Everything you make lives in one workspace on your own machine: the apps, the automations, the files, the data, and the memory. They share all of it, so the twentieth thing you build costs less than the first, because it already knows what the others learned. Researching a topic, keeping the findings, building an app around them, and pulling in data from an outside API on a schedule is one flow, not four tools.

Chat sits beside the work in a split view on desktop, and as a pane you swipe to on mobile. You never leave your work to talk to it. So the loop that makes an app better runs while you are using it: you spot the thing, you say it, the app changes under you and keeps running. That loop is the same on a phone. It asks for no editor, no build, no redeploy, and no permission to read code, though knowing what is going on underneath is still an advantage. The prompt is the main interface, and the models are configurable and swappable.

You own the data. It lives in a local Postgres event store, or as git-versioned artifacts you can read without Lucidos. Nothing happens without your intent: you can automate anything, on a schedule or on an event, but Lucidos does not act on its own.

Get started

• Quickstart — install Lucidos on a clean machine and pick an LLM provider.
• Concepts — events, artifacts, intents, knowhow, apps, triggers, and the prompt-first model.
• Tutorials — build your first app, then automate with a trigger.
• Develop Lucidos: run from a source checkout and let Lucidos work on its own code.

These docs stay in sync automatically

Every page here that describes something defined elsewhere in the repository (the README, the glossary, the taxonomy) is transcluded from that canonical source at build time — never copy-pasted. When the source changes, the docs change with it.