This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady
Did you know the chainsaw was originally invented to help with childbirth?
Two Scottish doctors in the late 1700s looked at a hard, slow, painful job and thought: there has to be a lazier way. A few centuries later, we use it to cut down trees and star in horror movies.
That's the thing about laziness. It's not a character flaw. It's the R&D department of the human race.
So here's my confession. My AI workflow had become a part-time job. Claude Code in one terminal. Codex in another. A local Llama in Ollama. DeepSeek in a browser tab I kept losing. Every task started with the same ritual: which tab was I in, and where did I put that conversation?
OpenWebUI was supposed to fix this. Instead, I spent an afternoon trying to plug an agent into it and ended up with a lot of YAML and no agent.
So, like any respectable sloth, I did the laziest possible thing. I asked two friends who are almost as lazy as me, and together we built one tool so none of us would ever have to do that again.
AgentWebUI is a lightweight, self-hosted, agent-first web UI. One server, one sidebar, every AI model and agent you use.
You open it, it says "Good evening", and it asks you one question: ask anything, or hand a task to an agent? That second option is the whole point. You don't do the work. You delegate it, then go lie down.
What it lets you be lazy about:
Who gets to be lazier? Any developer juggling more than one AI tool. Which, in 2026, is every developer.
Try it live: agentwebui.hackershostel.com
On the home screen, the sidebar holds a DeepSeek chat, a Claude Code workspace, Codex, OpenAI and Gemini, all in one list. The model picker says llama3.2:3b, running locally. That's five tools' worth of tabs I no longer have to open.
One small web page to chat with AI models and with command-line agents, on your own server. Open it and chat
there is no setup screen and no accounts. Everything is configured in .env. The package and command are still
named agentwebui-lite.
The server is about 3,000 lines of Python with one dependency (aiohttp) and uses about 40 MB of memory. The web
client is Preact through htm with no build step. Nothing loads from the internet unless you pick a font other than
Geist.
Setup, written for people who also don't want to read setup instructions:
git clone https://github.com/HackersHostel/AgentWebUI.git
cd AgentWebUI
cp .env.example .env # fill in your models and agents
docker compose up -d
Then open it in your browser and go back to lying down.
The design rule was simple: agents are the main character, chat is the supporting cast. In most UIs it's the other way around.
Because the laziest model is the one you never have to ask permission to use.
A closed, single-vendor tool can't do this. It wants you in its tab. AgentWebUI is just one tab, and it's yours.
A scientific study, conducted by me, on my own laziness:
| Task | Before | With AgentWebUI |
|---|---|---|
| Find the right AI tool | Open 4 tabs, 2 terminals, sigh | One dropdown |
| Find yesterday's chat | Check every app's history | ⌘K |
| Try a new open model | New tool, new install, new login | Edit env file, restart |
| Hand off a coding task | Open a terminal, set up the agent | Pick Claude Code, type the task |
The chainsaw doctors would be proud. Hard job in, lazy solution out.
Entering for the overall prize.
Built with @tahrimwalid and @mahedi, who are almost as lazy as me.
If you're a developer with more AI tabs than browser memory, give AgentWebUI a spin. Then do what the sloths do: delegate, relax, and let the agents earn their keep. 🦥