CraftBot with Living UI

The local-first approach is underrated. I run Puppeteer-based automation agents locally on my PC specifically because cloud execution doesn't work for browser automation that needs persistent sessions and real Chrome profiles.The "Living UI" concept is interesting — having the agent build its own dashboards instead of you predicting what you'll need. How does it handle tasks that need to run on schedules rather than on-demand?

The shift from reactive to proactive is a much harder design problem than most agent products acknowledge. Reactive agents fail silently, you just don't get a good answer. Proactive agents fail loudly, wrong actions on your behalf, noise surfaced as priority, the things that actually mattered missed while chasing the things that didn't. Curious how CraftBot calibrates when to act vs when to ask, and whether that threshold adjusts based on how often the user overrides it.

One more thing. Is this about dashboards or apps on the device?

Would the UI change based on how the user interacts with their device?

How CraftBot connects different Living UI seems really cool use of agentic workflows. So, I am curious if it is mainly one agent doing everything, or do you use multiple agents with different roles that work together in some kind of orchestration?

The 3AM memory consolidation is the most interesting architectural decision here. Love it. Most local agents treat memory as a simple append log (which means the context gets bloated or stale fast). This one is different.

Wishing good luck with today's launch :)

Looks amazing. How good is it with integrations? I am thinking about connecting it to some existing Notion databases to make use of it as internal dashboards.

Another impressive thing about Living UIs is that the agent can mix and match to perform complex tasks. For example, if you ask the agent to gather data from your CRM Living UI and Financial Tracker Living UI and then create a Ticket on your Kanban Living UI (which has user and role authentication built-in so your whole team can use it) - the agent will use all these separate Living UIs to perform the task.So the Living UIs aren't only dashboards for you but they are extensive use-able tools for the agent as well.

Most tools still force users to adapt to fixed interfaces and systems, but the idea of an AI agent staying true to context and evolving the UI as needs change feels much closer to how people naturally work. Really interesting direction.

quick question on the "Build from scratch" flow how does it handle complex API integrations? if i want my Living UI to pull data from multiple third-party tools, can CraftBot set up those connections too? checking the demo now.. @tham_yikfoong

The agent era is reshaping the interface.TUI is one direction, and it makes more sense for devs. But I don’t think agents remove the need for UI. Visual interfaces are still one of the best ways to compress state, context, and actions into something humans can understand quickly.@CraftBot’s Living UI pushes this in a useful direction. The interface is no longer a fixed app you buy and adapt to. It becomes something the agent can build, read, modify, and operate based on the current task.This points to a different software shape: not one-size-fits-all dashboards, but interfaces generated around the immediate job, the user, and even the current moment.For agents, UI may become less of a destination and more of a live surface for action.

For context, CraftBot is a self-hosted, proactive AI agent that can control a PC and take actions for you.Today, most software, dashboards, apps, and subscription tools are static. When you need a new feature, you email the developer. If you are lucky, it ships six months later. If not, you may never hear back.Therefore, we are introducing a new concept: 🌱Living UI🌱.Living UI lets CraftBot build, import, and evolve custom software, apps, and dashboards directly inside the agent. The best part is that CraftBot stays context-aware of the Living UI’s state. It can read, write, update, and act on the interface directly.Need a Kanban board with a general AI agent built in?A CRM tailored exactly to your workflow?A company dashboard your agent can actually operate?You can spin all of these up as a Living UI. There are three ways to create one.1. Build from scratch. Just describe what you want, and CraftBot generates the backend, API, and UI, then iterates with you.2. Install from the marketplace. Use ready-to-use apps built by the community.3. Import your existing project or GitHub repo. CraftBot converts it into a Living UI and integrates itself into it.A Living UI is never finished. You can always modify it by telling CraftBot as your needs evolve. So instead of static tools, you get software that grows with you.Try CraftBot and Living UI today. Build and customize your own Living UI, and stop relying on subscription tools that were never built to fit your needs perfectly. 🟠🌱