DDispatcher

Your coding workspace

Use your workspace access token to continue. Your existing code reviewers run independently.

Workspace access token

DDispatcher

PROJECTS

SESSIONS

CONNECTIONS

CODING WORKSPACE

What would you like to build?

Connecting

One idea. One shared place to build.

Choose a project, then start a session. Your lead coordinates the developer, tests, and independent code reviews.

This idea

Where the work actually is. Each step is shown on its own: something built is not tested, something merged is not deployed, and nothing counts as done until it is verified on what is running.

Connections

Everything this workspace can reach, and exactly what each one is allowed to do. A Google Compute Engine server is set up in one guided step with no keys at all. Anything else that needs a password or API key gets it through Enter a credential on its card, when this workspace has a secure store set up: the value goes straight to Google Secret Manager and this page only ever shows its name.

View pull request

Message your lead

Messages stay with this session, including while work is running.

New project

Project nameGitHub repository Authorized billing account Project spending limit ($)

Funding and payer access must be provisioned by the workspace administrator. Zero pauses paid work.

Start a coding session

Short nameWhat should it do? Developer Session spending limit ($)

Shared code reservations

Your lead verifies these before editing. Conflicting work waits safely.

Files or directories (one per line) Shared interfaces or database resources (one per line)

Start an idea

Short name, shown in the list What should exist when this is done? How will you know it works? One check per line (optional)

How should it be built? Normal: Claude builds it, with the usual reviews. Super: GPT plans and keeps watch, Claude builds. You can switch later without starting over.

Change the goal or checks

Saving publishes a new version of this idea's instructions. Everyone working on it sees the change; nothing already built is thrown away.

Goal Checks, one per line

Credential

This goes straight to Google Secret Manager in your own Google Cloud project, encrypted there. Dispatcher keeps only where it is. Nobody, including the AI, is shown it again. To change it later, enter the new one under the same name; the old one is kept in history, not deleted.

Name it (lowercase, such as api or database) What is it, and what may it do? (no secrets here) The credential itself

Set up the logins

This creates two logins for this server, both reached through Google's secure route with no keys to store: a look-only login Dispatcher uses by itself for logs, service status and disk space, and a repair login it uses only for a repair someone approved.

Open Google Cloud Shell, signed in as the project owner.
Press Copy below and paste it into Cloud Shell. It checks every file it installs and stops on anything unexpected.
Come back here and press Test again. Dispatcher then proves the look-only login cannot change anything.

Add a connection

What is it? Name it so you will recognise it Which one? The instance, service or database name your provider console shows. For a Google Compute Engine server, write project/zone/server. For Supabase, the 20-letter project reference. For Vercel, the project name, or team/project. Environment This provider requires its own change approval

Added connections start at Needs setup. This page will not say a connection can do anything until a real check on the machine proves it.