One Chat Message, a Whole Automation Stack: Inside LiveContext
You've probably been here: you need to automate some internal process, so you spin up a workflow tool, then realize you also need a chatbot for the front end, a dashboard for your team to actually use, and some kind of agent to handle the messy parts in between. Suddenly you're stitching together four different products and writing glue code to hold it all together. LiveContext is a self-hosted platform that tries to collapse that entire stack into one place—and it starts with a single chat message.
What It Does
LiveContext is an AI automation platform where you describe a job in chat and it builds the automation in front of you. That one description produces four things on a single canvas: a workflow you can read as a graph, AI agents with scoped access and budgets, and a small app your team can actually use. The project positions itself as a source-available, self-hosted alternative to n8n, Zapier, and Make—but with AI agents built in rather than bolted on.
The stack is Java 21 on the backend and Next.js 16 on the frontend, and it ships with Docker Compose support. The core idea is that you build it once and it runs as all four pieces: chat, workflow, agent, and app. Agents each get their own model, tools, files, credit budget, and audit trail, so you can see exactly what each one did rather than staring into a black box. The workflow itself is drawn as a readable graph, and you can wrap it in a real interface with forms, dashboards, and live approval screens that either your team or an agent can act on.
Why It's Cool
-
The four-in-one canvas is the actual pitch. Most teams end up wiring together a chatbot, an automation tool, an app builder, and an agent framework. LiveContext argues you don't need four products—you need one canvas where the chat builds the thing and the workflow, agents, and app all live together. That's a real reduction in surface area, and it's the kind of thing that only makes sense once you've felt the pain of the alternative.
-
Agents are scoped and budgeted, not magical. Every agent has its own model, tools, files, credit budget, and full audit trail. That's a meaningful design choice. Instead of one omnipotent agent with access to everything, you get a fleet of scoped agents, one per job. If you've ever tried to figure out why an agent did something weird at 2am, the audit trail alone is worth the price of admission.
-
You can read the workflow. The automation is drawn as a readable graph. That sounds small, but a lot of "AI automation" ends up as an opaque chain of prompts you can't inspect. Being able to look at the graph and see what's happening is the difference between a tool your team trusts and one they route around.
-
Self-hosted and source-available. It's licensed under a Sustainable Use license, which means you can run it yourself. For teams with data they can't ship to a SaaS vendor, that matters. Docker Compose means you're not fighting a deployment pipeline to get started.
-
The app layer is the sleeper feature. Wrapping the workflow in forms, dashboards, and live approval screens is what turns an automation into something your team actually opens every day. Approval screens in particular are a smart touch—human-in-the-loop is often an afterthought, and here it's a first-class part of the interface.
How to Try It
The README points to Docker Compose as the deployment path, and there's a hosted version if you want to poke at it before committing to a self-hosted install.
- Head to the repository: github.com/livecontext-ai/livecontext-ce
- Check the releases page for the latest version and setup instructions
- If you'd rather not self-host first, try the hosted version at livecontext.ai
- Once it's running, describe a job in chat and watch it build the workflow, agents, and app
The README also links to a full-size demo video if you want to see the build loop in action before installing anything. And if it looks useful, the maintainers ask for a star—which is a fair ask for a project like this.
Final Thoughts
LiveContext is aimed at teams who've outgrown duct-taping four tools together but don't want to hand their automation stack to a SaaS vendor. The self-hosted, source-available angle plus scoped agents with audit trails is a coherent answer to a real problem. It's early—the README is still filling out, and the Sustainable Use license is worth reading carefully if you're evaluating it for commercial use—but the core idea of one canvas for chat, workflow, agent, and app is the kind of consolidation that makes sense. If you've been waiting for an automation platform where the AI part isn't a black box, this is worth a look.
Follow @githubprojects for more developer tools and open source projects.