Shape in the workstream thread
The operator talks in one room. Scope, taste calls, docs, task state, and agent context stay attached to the workstream instead of scattering across chat tabs.
Route human taste through one project room: shape work in a thread, let the orchestrator gate the next move, dispatch specialist agents, and review returns without polling a dozen chat tabs.
Controlled access while the product is shaped with early operators.
frontend lane
implementingreview lane
waitingdocs lane
clearthe bottleneck moved
Coding agents make it easy to start more work than one human can responsibly supervise. The hard part is deciding what should continue, what needs taste, what is safe to integrate, and which stop points deserve escalation.
DevPoke treats the human as the scarce resource. The inbox becomes the home for decisions, while every workstream carries its own context, gates, specialist lanes, and review trail.
operator loop
The operator talks in one room. Scope, taste calls, docs, task state, and agent context stay attached to the workstream instead of scattering across chat tabs.
The orchestrator decides obvious continuations and reserves human attention for readiness, launch, integration, and risky product calls.
Focused agents take separate worktrees for implementation, tests, docs, infra, and review while the cockpit keeps ownership and status visible.
Returns are evaluated against the workstream promise. Reviewers catch bad splits, integration gets audited, and the next stop point is explicit.
product surfaces
Every human decision request lands in one queue, ordered by urgency, project priority, and age.
Shaping, executing, blocked, paused, and complete are first-class states with context, gates, and owner lanes.
Each agent lane carries its assignment, branch, artifacts, reviewer notes, and handoff evidence back to the room.
Autonomy rises where the loop proves itself and falls back to the human when taste, permission, or accountability matters.
early access
Tell us who should evaluate DevPoke and what operator loop you are trying to run. Access stays controlled while the beta is shaped with early operators.
Built for real agent supervision workflows, not open signup volume.
Requests are reviewed for fit with the private beta.
faq