Tickets
CropsCode is ticket-driven. Instead of manually configuring containers, you paste a ticket URL and the system handles everything: fetching context, picking a worker, creating the container, and starting the AI agent with full task context.
Supported Providers
Section titled “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
Section titled “How It Works”- Paste a ticket URL into the launch modal (or ask CropPilot)
- CropsCode fetches the ticket details — title, description, labels, comments
- A CLAUDE.md is generated with the full ticket context as instructions for the AI agent
- A container launches on the least-loaded worker with the repo cloned and agent ready
- The AI agent works on the ticket autonomously
- You get a draft PR when the work is complete
What Gets Passed to the Agent
Section titled “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
Section titled “GitHub Token”For GitHub Issues, a personal access token increases rate limits:
| Without token | With token |
|---|---|
| 60 requests/hour | 5,000 requests/hour |
Set your token in the orchestrator environment:
GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAutomation with Cron
Section titled “Automation with Cron”Combine tickets with cron workflows to automatically process new tickets on a schedule — wake up to draft PRs every morning.