Features
Custom agents
Create focused repository agents from supported triggers and verified artifacts.
Build on verified contracts
A custom agent has a name, supported trigger, expected GitHub artifact, prompt, model configuration, optional schedule, and repository tool image. The artifact determines the execution profile and what the runner must verify.
Supported triggers and outcomes
Pull-request outcomes use the Code execution profile. GitHub-issue outcomes use Repository Review. Pull-request-review outcomes use PR Review.
- Issues: run for Ready project issues with the agent's exact, case-sensitive name label; create a GitHub issue or pull request.
- Scheduled audit: run on the selected cadence; create zero or more parked GitHub issues.
- Pull request: run for eligible open, non-draft pull requests; publish a pull-request review.
Keep each custom role focused
Use a concrete name and prompt that describe one responsibility. The runner combines the prompt with trigger context and validates the selected artifact before success.
Frequently asked questions
Can a custom agent use an arbitrary trigger?
No. It must use one of the current issue, scheduled-audit, or pull-request triggers.
Can one custom run create several pull requests?
No. Pull-request and pull-request-review artifacts have a maximum count of one per run.
How many issues can a scheduled custom agent create?
The verified GitHub-issue contract currently allows up to 50 issues and permits zero for a scheduled audit.
Do custom agents share capacity with built-in agents?
Yes. Every built-in agent, custom agent, and Issue Planner session shares the repository capacity limit, with workspace runner capacity as the outer limit.
Do provider credentials reach the hosted website?
No. Provider API keys and OAuth roots remain in the local runner environment. The hosted control plane receives sanitized availability, model catalog metadata, job events, and outcome evidence.
Can agents in one repository use different models?
Yes. Each built-in or custom agent selects its own provider, catalog model, supported thinking level, and repository tool image.