Tickets

ClusterCode is ticket-driven. Instead of manually configuring DevBoxes, you paste a ticket URL and the system handles the setup: fetching context, suggesting a worker, creating the DevBox, and staging the ticket context so an agent can pick it up.

Supported Providers

Provider	URL Pattern	Availability
GitHub Issues	github.com/{owner}/{repo}/issues/{number}	All plans
Azure DevOps	dev.azure.com/{org}/{project}/_workitems/edit/{id}	Pro and Enterprise
Trello	trello.com/c/{cardId}/{card-name}	Coming soon
Monday.com	monday.com/boards/{boardId}/pulses/{itemId}	Coming soon

How It Works

1. Paste a ticket URL into the launch modal (or ask Nucleus)
2. ClusterCode fetches the ticket details — title, description, labels, comments
3. A CLAUDE.md is generated with the full ticket context as instructions for the AI agent
4. A DevBox launches on the worker you selected — or, on auto-select, one chosen by the placement rules — with the repo cloned and the agent CLI ready
5. You start the agent from the live terminal — or skip the launch entirely and start a Run with the ticket URL, which drives the agent for you
6. The agent opens a draft PR when the work is done

What Gets Passed to the Agent

The generated context includes:

• Ticket title and full description
• Labels and assignees
• Comments and discussion
• Repository URL and default branch
• Any linked PRs or issues

GitHub Token

For GitHub Issues, a personal access token increases rate limits:

Without token	With token
60 requests/hour	5,000 requests/hour

Add your GitHub token under Settings → Environment Variables → Service access — once set, it’s injected as GH_TOKEN and used for authenticated GitHub requests.

Automation with Cron

Combine tickets with recurring work to automatically process new tickets on a schedule — wake up to draft PRs every morning.