Durable work units
Kanban tasks and long-running missions with plans, todo state and evidence you can inspect mid-run.
Meet Elowen
One agent that can talk, plan, use tools and carry real work across your projects.
Elowen is ready
Talk to it. Give it a goal.
Let it keep going.
Elowen turns a conversation into visible work. It plans the next steps, calls tools, delegates specialists and returns with evidence — while your models, memory and permissions stay under your control.
One continuous mission Any configured model Durable memory Explicit permissions
01 / CONVERSATION Start by talking.
Start by talking.
Not configuring a workflow.
Ask a question, drop in a repository, or describe an outcome. Elowen keeps the conversation connected to the work: current project, active goal, tools, memory and the decisions already made.
You can stay in the terminal when speed matters, or open the WebUI when you want the whole system in view.
Meet the CLI →
02 / DURABLE WORK
A goal becomes work you can see.
Long tasks do not disappear into a spinner. Elowen frames the goal, builds a plan, updates its todo state, calls tools and records the evidence it needs to finish.
Tasks and missions stay inspectable while they run. You can steer the next step, review a diff, open a commit or stop before a risky action.
FRAMEPLANACTREVIEW
03 / INTELLIGENCE One mission.
One mission.
The right mind for each part.
Elowen can delegate focused work to sub-agents without fragmenting the mission. A coding specialist can inspect the repository, a reasoning model can challenge the plan, and another agent can verify the result.
Each specialist may use a different configured model and a scoped set of tools. Their findings return to one goal, one context and one accountable result.
How autonomy works →GOALOne mission context
CODEClaude RESEARCH
GPT REVIEW
Gemini
04 / MEMORY
The next conversation starts further ahead.
Elowen keeps the facts, decisions, preferences and project context worth carrying forward. Memory is visible and editable — not a hidden profile assembled somewhere else.
Search it, group it, connect related facts, or remove what no longer belongs. The agent remembers because you chose to keep it.
Explore memory and chat →
05 / CONTROL
Autonomy without surrendering the keys.
Projects define where Elowen works. Users and roles define who can ask. Tool rules and approval gates define what may happen without confirmation. Provider credentials stay on the daemon.
The same boundaries follow the agent through the CLI, WebUI and connected channels. There is one runtime and one policy — not a different agent behind every screen.
Read the security model →
Reach the same Elowen from wherever the work begins.
Use the CLI for focus, the WebUI for context, and plugins for the channels and services your team already lives in.
CLIFast conversation, goals, todo state and live tool output.
WebUITasks, projects, memory, sessions, editor, terminal and system control.
ChannelsDiscord and WhatsApp connect back to the same agent runtime.
PluginsAdd skills and integrations without forking the brain.
Everything the agent needs.
One self-hosted daemon.
Scoped specialists
Delegate focused work to specialists on different models — findings return to one mission context.
Graded independence
From ask-first to autopilot, with an overseer gate deciding what may proceed without you.
Facts you control
Decisions, preferences and project context — searchable, editable and deletable, never a hidden profile.
Repository-aware
Registered repositories, inspectable diffs, PR workflow and handoff notes between agent runs.
RBAC and approvals
Users, roles, per-user tools and models, granular tool permissions and approval gates for risky actions.
Channels included
Discord and WhatsApp bridges plus scoped plugin capabilities — one runtime behind every surface.
CLI and WebUI
A chat TUI for speed and a full web workspace: kanban, sessions, editor, terminal and settings.
It already works for a living.
Not a demo, not a toy dataset. These run on Elowen every day.
Patricie runs a hair salon. Clients message her Elowen on WhatsApp — it offers open slots, confirms the booking with an SMS code and sends a reminder the day before. Payments and expenses land in the books on their own. She reads the morning summary and just cuts hair.
The documentation you're reading was written, restructured and deployed by Elowen itself — 28 pages, live on a Sunday evening. The orbital menu up top? Its own idea, ported from its own WebUI.
At J+P Autodíly, a supplier's delivery note gets photographed at the counter. Elowen reads the barcodes, matches the parts against the catalog and stocks them in. What used to take an evening of typing takes minutes.
Built for more than one person.
Most agent harnesses assume one user, one machine, one API key. Elowen assumes a life — and maybe a team.
ELOWENTHE USUAL HARNESS
Everyone gets their own keys Users, roles, per-user tools, models and projects. A teammate sees only what you assign. One user, one shared everything.
Bring your subscription Sign in with your ChatGPT or Claude account and spend the subscription you already pay for — with live 5-hour and weekly limit meters. API keys only, and the bill at the end of the month.
Memory you can open Facts, decisions and preferences — searchable, editable, deletable. A hidden profile assembled who-knows-where.
Autonomy with a gate Graded levels plus an overseer deciding what may proceed unattended. Either babysitting or YOLO.
One runtime, every surface CLI, WebUI, Discord, Telegram, Teams and WhatsApp share one policy and one memory. A different bot behind every screen.
YOUR AGENT. YOUR INFRASTRUCTURE.
Install Elowen and start with a conversation.
One command installs everything — Node.js, the daemon, tmux, the systemd services and the first admin — and leaves a running WebUI. It works on Linux, or on Windows through WSL2. Prefer to do it by hand? A guided npm route and a Docker image are in the docs.
LINUX · WINDOWS (WSL2)NODE.JS ≥ 22SINGLE SQLITE FILESYSTEMD / DOCKERMIT LICENSE
$ curl -fsSL https://raw.githubusercontent.com/dragocz95/elowen/main/install.sh | bash
# Linux — installs Node, tmux, systemd, admin
● Elowen is live — http://localhost:4500
$ elowen # opens the chat TUI$ npm i -g elowen
$ elowen # guided setup wizard, then the chat TUI
● WebUI at http://localhost:4500$ git clone https://github.com/dragocz95/elowen.git && cd elowen
$ docker build -t elowen .
$ docker run -d -p 4400:4400 -v elowen-data:/app/data elowen
# one SQLite file on the volume — upgrades are a container swap# inside WSL2 (Ubuntu is installed for you if needed)
$ curl -fsSL https://raw.githubusercontent.com/dragocz95/elowen/main/install.sh | bash
● WebUI reachable from Windows at http://localhost:4500Common questions.
Where does my data live?
On your machine. Elowen is a self-hosted daemon with a single SQLite database file — conversations, memory, tasks and settings never leave your infrastructure. Provider credentials stay on the daemon and are never exposed to clients.
Which models can it use?
Any provider you configure — Claude, GPT, Gemini and others. Each sub-agent can run a different model, and administrators can restrict which models each user is allowed to use.
Can it work unattended?
Yes, to the degree you allow. Autonomy levels range from ask-first to autopilot, an overseer gate decides which steps may proceed without confirmation, and approval gates protect risky actions.
Can my team use it too?
Elowen ships with users and roles (RBAC), per-user tools and models, project assignment and visibility rules. Everyone talks to the same runtime under the same policy.
How hard is it to run in production?
The recommended setup is a systemd service behind a reverse proxy — sudo elowen install sets it up, and the one-line installer runs it for you. A Dockerfile is available if you prefer containers.
Does it run on Windows?
Yes, through WSL2. Elowen runs its agents in tmux and its services under systemd, both Linux-only, so the Windows installer enables WSL2, installs Ubuntu if needed, and runs the exact same Linux install inside it. The WebUI is then reachable from Windows at http://localhost:4500.
Is it open source?
Yes — MIT licensed, developed in the open at github.com/dragocz95/elowen.