Zozo Docs

Quickstart ​

Setup takes a newly invited hosted tenant from sign-in to a Stack that can Dispatch Issues on either supported Platform. Before you begin, have a GitHub sign-in account, a Claude or Codex Credential, and a GitHub personal access token or the Atlassian Platform Credential ready.

During account signup, choose the EU Home Region. Stacks are hosted in the EU (Germany or Finland) for now.

Zozo provides Node.js 22 and Python 3 by default, and it can provision repository-declared versions or other mise-supported Toolchains before a Run starts. See Declare a Toolchain when your repository pins a version or uses another language ecosystem.

Sign In ​

Open app.zozohq.com, enter the invite code from whoever administers your Zozo deployment, and select Continue with GitHub. After you approve the GitHub sign-in and finish the account steps, the app provisions your Stack. When it shows Your Dashboard is ready, select Open your Dashboard to enter the Stack's own Dashboard.

The provisioning page checks your Stack automatically while you wait. The control-plane sign-in and your Stack's own session are separate, so Open your Dashboard completes a secure handoff and signs you in to the Dashboard. See Auth & Consent for why.

Complete the Three Steps ​

The three Setup steps appear when you enter an incomplete Stack for the first time. From app.zozohq.com, sign in and select Open your Dashboard. The Dashboard opens Setup automatically. Together, its three steps provide everything Zozo needs to watch a Project and Dispatch its Issues:

  1. Credential: Connect a Runtime. Name a Credential, choose Claude or Codex, choose its kind, and provide the value. A Solo tenant running Zozo against their own repositories and spending their own money will usually use a personal subscription Credential. A Billed tenant running work for a client they invoice will usually use that client's vendor API key. A subscription Credential also asks you to record consent. See Connect a Personal Subscription Credential for the vendor-specific preparation.
  2. Platform Credential: Choose GitHub (preselected) or Atlassian. A Platform supplies a Project's repository and issue tracker together. For GitHub, provide the personal access token the Dispatcher uses to read Issues and repositories and write branches and Pull Requests. Setup lists the permissions. Use a classic token for collaborator repositories owned by someone else. For Atlassian, provide one account email, a Bitbucket-scoped API token with its workspace, and a Jira-scoped API token with its Cloud site. These form one Platform Credential, with a health reading for each token. See Atlassian Projects for scopes and token creation.
  3. Project: Watch a Project, and set its pace. Pick a repository, its priority, and whether it's active. Atlassian lists repositories from the bound workspace and asks you to choose a Jira project from the bound site. Pick the required Publish Issue Type and optionally a parent-capable Spec Issue Type for Medium Intake and Wayfinder. An optional component and labels narrow the Jira scope. Small Intake works without a Spec Issue Type; Prototyping Sessions require GitHub. Label Authority defaults to Observed; choose Owned explicitly to let Zozo maintain Control Labels. Then choose one Pace preset: review-paced waits for you to clear the previous Pull Request; full-speed keeps selecting Issues without that wait; and autonomous also merges ready changes. These are presets for the underlying settings, which remain editable on Projects.

Setup derives completion live from Credentials, Platform Credentials, and Projects, using the same facts as the Dashboard checklist. Every watched Project's Platform must have all its token health readings valid. An Atlassian-only Stack needs only the Atlassian Platform Credential. You can continue after a record is stored even when a health reading is invalid or unproven. You can skip Setup and configure the same state on Credentials and Projects. Resume Setup returns to incomplete steps.

Remove a Platform Credential from Credentials. Removal is refused while any registered Project depends on it, active or not, and names those Projects. Removing the last record with no Project left makes Setup incomplete again.

Start Work ​

The Frontier contains open Issues carrying the ready-for-agent label that are safe for the Dispatcher to pick up. Add that label to an Issue in the Project you just watched, then return to Setup's Stack ready screen and select ▶ Start Dispatching. This enables Auto-dispatch, which keeps selecting eligible Issues until you select Suspend on the Dashboard.

The Dashboard shows the resulting Thread and its Runs live. A Run's status moves from queued to running, then to completed, failed, or Interrupted. The Messages, Tools, and System filters separate the Events in its timeline.

Use the Regular Pages ​

If you skipped Setup or are reconfiguring an existing Stack, follow the same path through the regular Dashboard pages:

  1. Open Credentials (#/auth). Under Add a Credential, choose its name, Provider, and kind. Supply the token, key, or auth file, and record consent when the subscription kind requires it. Wait for the Credential to show authenticated.
  2. On the same page, provide a Platform Credential for GitHub or Atlassian. Follow the displayed permission guidance and save it.
  3. Open Projects (#/projects) and add a repository. Choose review-paced, full-speed, or autonomous, along with its priority and active state.
  4. Label an open Issue ready-for-agent, then enable Auto-dispatch on the Dashboard. The Dispatcher will claim the eligible Issue during a Selection Pass and stream its Runs into the Dashboard.

The control plane starts a short-lived, single-use handoff to your Stack, which redeems it and creates its own local session. The invite and browser redirects handle this flow, so you don't need to copy session tokens or call handoff routes yourself.

What's Next ​

Docs for Zozo: a coding-agent harness.

Copyright © Zozo