The tool
devkick init
A running agent in under five minutes, on venue wifi.
Shipping with devkick v1. Want it sooner? Come to a build night and ask for it; the CLI is built from what members request.
What it scaffolds
- Local-vs-API prompt: Ollama or an Anthropic key, your call
- Docker sandbox so the agent can't touch your machine
- git-worktree isolation so it can't touch your branch
- A hello-world agent task with streaming terminal output
Offline-friendly. No accounts, no config files, no telemetry. ~200 lines of Node you can read in one sitting.
Why this tool exists
devkick init is aimed at the first few minutes of a build night. A new builder should be able to get from a blank machine to a running agent without spending the room's best energy on setup. The promise is deliberately concrete: one command, a sandbox, and a hello-world task that produces streaming terminal output.
The scaffold keeps the local machine and the project boundary separate. Docker gives the agent a sandbox so it cannot touch the machine directly. Git-worktree isolation keeps it from touching the builder's branch. The setup also asks whether the run should use Ollama locally or an Anthropic key through an API path.
The v1 shape is intentionally small and readable. It is planned as roughly 200 lines of Node, with no account system, no config files, and no telemetry. It is offline-friendly, which matters when a room has a crowded venue network and a builder needs to keep working.
This page describes the tool before its publish step. The command is coming soon, and it is demoed at a build night before it is announced anywhere else. The roadmap is not a promise of a large platform: future template scaffolds are meant to come from community issues and pull requests, guided by what members ask for at devkick events.
The tool is part of the same builder loop as the Kicks. Bring a project, get a safe starting environment, run a real task, and show what happened. If the current promise matches the setup you need, follow the calendar on Luma and come to the Kick where it ships.
Questions, answered
What is devkick init?
It is a command intended to scaffold a local agent workspace with a Docker sandbox, git-worktree isolation, a hello-world task, and streaming terminal output.
How long should setup take?
The v1 promise is a running agent in under five minutes, including on venue wifi.
Does devkick init require an account?
The planned v1 is offline-friendly with no accounts, no config files, and no telemetry.
What can the scaffold use for a model?
The local-vs-API prompt offers Ollama or an Anthropic key. The choice is yours.
Roadmap
Whatever members ask for at events. Issues and PRs welcome on
GitHub: community
--template scaffolds are the intended growth path.
Be there when devkick-cli ships
The CLI lands at a build night, and the roadmap is whatever members ask for in the Discord.