Introduction
AFK (Autonomous Flow Kit) is a model-agnostic coding agent platform. A daemon works near your code while the browser app gives you visibility, approvals, collaboration, and control — so agent work keeps moving even when you're away from keyboard.
What is AFK?
AFK is the control room for engineering teams running coding agents. It provides persistent agent sessions with browser-based visibility, BYOK (bring-your-own-API-key) model routing across every major provider, workspace controls, and human-in-the-loop safeguards such as tool approvals and plan review.
Key design principles:
- Work stays near your code. The daemon runs on a developer machine or approved shared runner so project access remains under your control.
- Simple connectivity. The daemon uses an outbound connection to AFK, so typical setups do not require inbound firewall rules or port forwarding.
- Model-agnostic. AFK supports Anthropic, OpenAI, Gemini, Mistral, Groq, xAI, DeepSeek, Azure, local models (Ollama, LM Studio), and Claude, ChatGPT, Kimi, and xAI subscriptions. You bring your own keys.
- Parallel agent work. AFK can coordinate sub-agents, scheduled work, task tracking, and session-to-session handoffs from the same browser workspace.
- External systems can start work. Inbound webhooks, saved schedules, and repository integrations let CI, monitoring, ticketing, or GitHub-driven workflows launch the same human-supervised sessions users start manually in the browser.
How it works
AFK has three components:
| Component | Runs where | Role |
|---|---|---|
afk server | Cloud | Hosted or enterprise control plane for browser access, session history, account settings, and team coordination. |
afk daemon | Developer machine | Runs agent work near your code, manages approved project access, and supports local, worktree, and Docker-backed sessions. |
| Browser UI | Any browser | Real-time chat with the agent, tool call visibility, approval flows, task boards, and session management. |
The browser is the command surface, while the daemon performs approved work against projects it can access. AFK keeps the transcript, approvals, tool activity, and team status visible from the browser.