A management platform for agentic coding. Everything is driven from a web GUI: a background orchestrator creates worktrees, runs and monitors sandboxed coding sessions, puts question sets and commits to you, and works through task lists and staged roadmaps unattended.
Verkstead (Norse verk, work + stead: a workshop) began as a clone of askance and keeps its architecture — a Rust workspace and a SolidJS SPA in one binary, SQLite, SSE nudges, web push, and server-side rendering of everything an agent writes. askance remains a separate, maintained product; Verkstead diverges freely from it.
Early, private, and unreleased. There is nothing to download yet. The workbench, the sandboxed sessions, the task-list and roadmap pipelines and the per-PR wrap-up are built; what has not happened yet is a real repository driven through them end to end, which is where adoption stands.
What a tag will produce is four ways in rather than one, and no two of them
are the same thing. On a host that is always on, the flake builds the headless
daemon and the NixOS module runs it. On a Linux desktop,
Verkstead-x86_64.AppImage is that same server started from an icon: the viewer
in your browser and a tray icon over it — or no icon at all where the desktop
has no tray host, vanilla GNOME being the case people meet, and it serves just
the same. On a Mac, Verkstead-universal.dmg carries Verkstead.app — one
download for both Macs, the same server again, with its icon in the menu bar.
That app is unsigned, so the first launch is refused and System Settings is
where it is allowed through; the steps are written out beside the download in
adoption. On Windows,
Verkstead-x86_64.msi installs that same app into your own profile — no
administrator, its icon in the notification area, and verkstead on your
PATH for a terminal. It is unsigned there too, so SmartScreen stops the
install behind a More info link with Run anyway under it — also written
out beside the download in
adoption. Which of the four you
want is adoption.
Sessions run on all three, and on all three behind a boundary. One description of what a session may reach, rendered over the mechanism each platform has: bubblewrap on Linux, where the rest of the machine is not in the session's namespace at all; Apple's sandbox on a Mac, where the machine is in plain sight and refused; and a local account of Verkstead's own on Windows, where reach is an access-control entry written for that account on each real directory the description names. What is inside is the same on all three, and adoption says what a session can and cannot get to on each — including the one elevated command a Windows machine wants once, to make that account. The daemon install is the NixOS module's.
Design — what Verkstead is and the decisions it rests on, as settled in the planning session behind it.
MVP roadmap — the five stages from here to a Verkstead that covers the whole loop, and the brief for each.
CONTEXT.md — the project's vocabulary. Conversation, Brief, Timeline, Question Set, Answer and the rest, defined once.
Adoption — what Verkstead replaces, how to get it running, and how a day's work goes through it from Brief to settled pull request.
Development — the dev shell, building the viewer, and the loop for working on Verkstead itself.
Releasing — the one workflow that turns a version number into the published binaries, the AppImage, the dmg and the msi. Nothing has been released under this name yet.
MIT — see LICENSE.