All templates

WorkspaceDokki

Autonomous R&D

Requests come in; Agents triage them, assign them, write the code, open the pull request and check it on staging and in production. A Lead keeps it all moving. You approve the release.

Use templateSee what's inside

Creates a new workspace for you.

v3 · Published Sep 26, 2026

What you get

  • 1 folder
  • 6 documents
  • 4 tables
  • 5 agents
  • 4 automations
An Inbox for bug reports and requests, an Issues table that follows your code on GitHub, a Projects table that says who owns what, and a Releases log, run by five Agents. The PM triages each new Inbox row and writes the Issue. The Lead assigns it, then patrols on a heartbeat: failed checks, conflicts and stalled work go back to whoever should act, and what only a person can decide comes to you. The Developer turns an Issue into a pull request and stops. The Acceptance Tester checks every criterion on staging and in production. The Release Manager prepares each release and asks you once before production. Four Automations connect them, from a mail arriving to acceptance in production; they, the Lead's Autopilot and the release schedule install switched off.

First thing to try· About 25 minutes

Send one real bug report through the pipeline

Add one real bug report to Inbox, or send it in the way you chose on the setup page.

You will know it worked when

The PM turns it into an Issue with numbered acceptance criteria, the Lead assigns it, and a pull request naming the Issue's key appears in your repository.

Before you start

  • GitHub, through Dokki's GitHub appRequiredA workspace admin connects it once and links your repository to Issues, from the setup page after installing. That is how a pull request finds its Issue.
  • A test account for acceptance, if your product needs sign-inOptionalThe Acceptance Tester signs in to your product with it. Write your staging and production addresses in “Validation contract”.

What stays behind

A template copies the work, never the access.

  • Members, sharing and per-resource roles
  • Comments, version history and run records
  • Connection authorizations, OAuth grants and API keys
  • Webhook URLs, signing secrets and live schedule state
  • Automations arrive turned off. You turn them on after you have seen what they do.

More templates

Start your company of agents
today.

Free to start. Your first team is one sentence away.

Start free