Edit HYDI — HyperDispatch

Project Key

Jira project key, e.g. MYPROJ

Jira Cloud ID

Find this in Jira → Settings → Products. It's the UUID in Jira API URLs, e.g. https://api.atlassian.com/ex/jira/CLOUD-ID/rest/...

Board ID

Go to your Jira board → the board ID is the number in the URL: /jira/software/projects/PROJ/boards/123

Oz Environment ID

Run oz environment list in your terminal, or find it in Warp → Settings → Environments

Oz API Key (per-project override)

Input an Oz Cloud API Key here. If an Agent ID is provided, the key should be created specifically for that agent.

Oz Agent ID

Optional. Oz agent identity UID used as the execution principal for this project's runs, so all of its work is tracked under one agent. Leave blank to use the API key's default principal.

GitHub Repo

Format: owner/repo

Default Model

e.g. claude-sonnet-4-5

Model Field ID

In Jira, go to Settings → Issues → Custom Fields. Click the field → the ID is in the URL, e.g. customfield_10050

Backlog Column Name

Column/status name used as Backlog for this project.

To Do Column Name

Incoming webhook transitions to this status will queue work.

In Progress Column Name

Used when HyperDispatch transitions a ticket after spawning an agent.

In Review Column Name

Used when HyperDispatch transitions a succeeded ticket.

Done Column Name

Incoming webhook transitions to this status trigger unblock checks.

Skills (comma-separated specs)

e.g. owner/repo:skill-name, owner/repo:other-skill

MCP Servers JSON

Optional JSON object passed to the spawned agent under mcp_servers.

GitHub PAT (per-project override)

Generate at github.com → Settings → Developer settings → Personal Access Tokens. Needs repo scope. Leave blank to use the global token.

Jira API Token (per-project override)

Service account bearer token (manage at admin.atlassian.com → API keys). Leave blank to use the global token.

Active

Edit: HYDI