does anyone else feel like this kind of web design is like the em-dash of web design? im not trying to knock the project itself, just wondering because every website that claude makes me looks like this until i tell it to look like something else.
I've been building AFK — a command center for engineering teams running
coding agents.
THE PROBLEM
Every coding agent tool I've used (Claude Code, Cursor, Aider, Cline)
assumes the person running the agent is the only human in the loop. For
real teams, that is never true.
Agent work disappears into terminal tabs. Risky mutations happen without
review. There's no shared visibility, no team-owned control point.
WHAT AFK DOES
A persistent daemon runs on your machine or your company server.
Engineers connect via browser.
- Sessions survive reconnect, terminal closure, machine sleep — intact
history, worktree state, and model context
- Three permission modes (auto, ask before writes, ask before every tool
call) plus plan mode
- Teams: orgs with roles, shared dashboards, session handoff with inbox
notifications, shared-session participants
- BYOK model routing: Anthropic, OpenAI, Gemini, Mistral, Groq, xAI,
DeepSeek, local, Azure, OpenRouter, subscriptions — your keys, their
rates, no markup
- Agent mesh: agents spawn children, message each other directly,
coordinate across sessions — daemon-local for same-machine,
hub-relayed cross-daemon with same-account enforcement
- Enterprise: shared daemon on company infrastructure, dedicated
control plane for stricter residency requirements
ARCHITECTURE
The daemon dials out to the hub. No inbound firewall rules needed. A
shared daemon on a company server keeps repository checkouts and command
execution inside the corporate network. Agents run as native OS processes
via the daemon's WebSocket mesh — not through the cloud hub.
Java 25, GraalVM native binary — virtual threads without the JVM startup
cost. Agents are lightweight OS processes orchestrated by the daemon.
PRICING
Free (1 daemon, 2 active sessions, 14-day history)
Pro — €10/mo
Max — €20/mo (personal automations and inbound webhooks)
Team — €20/seat/mo (2-10 seats, shared dashboards, session handoff)
Business — €30/seat/mo (5-100 seats, team automations, 2-year history)
Enterprise — custom (unlimited/custom history, on-prem, dedicated
control plane)
60-day unrestricted trial. No credit card required.
Pre-revenue, self-funded, zero burn — running on a homelab.
Would love feedback, especially from anyone running agents in a team
context where the single-user assumption breaks down.
does anyone else feel like this kind of web design is like the em-dash of web design? im not trying to knock the project itself, just wondering because every website that claude makes me looks like this until i tell it to look like something else.
That's fair and I don't disagree. The focus has been more on the functionality rather than the "eye candy" :)
> That's fair
You might need to spend some time with a paper book.
Hi HN,
I've been building AFK — a command center for engineering teams running coding agents.
THE PROBLEM
Every coding agent tool I've used (Claude Code, Cursor, Aider, Cline) assumes the person running the agent is the only human in the loop. For real teams, that is never true.
Agent work disappears into terminal tabs. Risky mutations happen without review. There's no shared visibility, no team-owned control point.
WHAT AFK DOES
A persistent daemon runs on your machine or your company server. Engineers connect via browser.
- Sessions survive reconnect, terminal closure, machine sleep — intact history, worktree state, and model context
- Three permission modes (auto, ask before writes, ask before every tool call) plus plan mode
- Teams: orgs with roles, shared dashboards, session handoff with inbox notifications, shared-session participants
- BYOK model routing: Anthropic, OpenAI, Gemini, Mistral, Groq, xAI, DeepSeek, local, Azure, OpenRouter, subscriptions — your keys, their rates, no markup
- Docker execution, sub-agents, MCP, skills, plugins, hooks, webhook and scheduled automations
- Agent mesh: agents spawn children, message each other directly, coordinate across sessions — daemon-local for same-machine, hub-relayed cross-daemon with same-account enforcement
- Enterprise: shared daemon on company infrastructure, dedicated control plane for stricter residency requirements
ARCHITECTURE
The daemon dials out to the hub. No inbound firewall rules needed. A shared daemon on a company server keeps repository checkouts and command execution inside the corporate network. Agents run as native OS processes via the daemon's WebSocket mesh — not through the cloud hub.
Java 25, GraalVM native binary — virtual threads without the JVM startup cost. Agents are lightweight OS processes orchestrated by the daemon.
PRICING
Free (1 daemon, 2 active sessions, 14-day history)
Pro — €10/mo
Max — €20/mo (personal automations and inbound webhooks)
Team — €20/seat/mo (2-10 seats, shared dashboards, session handoff)
Business — €30/seat/mo (5-100 seats, team automations, 2-year history)
Enterprise — custom (unlimited/custom history, on-prem, dedicated control plane)
60-day unrestricted trial. No credit card required.
Pre-revenue, self-funded, zero burn — running on a homelab.
Would love feedback, especially from anyone running agents in a team context where the single-user assumption breaks down.
https://www.mooglest.com
app: https://afk.mooglest.com