Team surface
Browser command center for sessions, prompts, review gates, and handoffs.
01 · Architecture
Built like an operations layer, not an inference reseller.
AFK sits above the model labs and below the team. It owns orchestration, observability, durability, isolation, and the agent harness — MCP tools, skills, hooks, memory, sub-agents, permissions, and browser feedback — while keeping providers swappable by design.
AFK harness
Daemon, hub, and history with tools, memory, hooks, skills, and sub-agents.
Execution lanes
Host, Docker, worktrees, and MCP-backed execution under team control.
Inference layer
Your providers: Anthropic, OpenAI, Gemini, local models, and private endpoints.
Team operations
AFK turns agent sessions into durable memory while work stays in motion.
Teams do not buy AFK to access a model. They use it to preserve what happened: decisions, tool calls, context, outputs, and continuity across real engineering work.
- Persistent and resumable coding-agent sessions
- Human-in-the-loop review gates and plan approval
- Webhook-triggered and scheduled automations
- BYOK model routing with no token markup
- Docker, host, worktree, and shared-daemon execution