Configuration
Customize Agent22's behavior, branch strategy, and integration settings.
Project configuration
Projects are configured through The Hub dashboard. A project maps to a single Git repository and defines how Agent22 interacts with your codebase and work tracker.
Repository settings
| Setting | Description | Default |
|---|---|---|
| Name | Display name for the project | — |
| Git repo URL | SSH URL of the repository (e.g. [email protected]:org/repo.git) | — |
| Main branch | Base branch Agent22 creates feature branches from | main |
| Agent instructions | Instructions written to AGENTS.md in the repo — guides the coding agent on conventions, architecture, and expectations | — |
SCM provider
Configure which source code management platform hosts your repository:
| Setting | Description |
|---|---|
| SCM provider | github, gitlab, or gitea |
| SCM provider URL | API URL for your SCM platform (auto-inferred for GitHub and GitLab) |
| SCM username | Username for Git commits |
| SCM API token | API token with repo read/write access |
| SSH private key | PEM-format private key for Git operations |
Default SCM provider URLs:
- GitHub —
https://api.github.com - GitLab —
https://gitlab.com/api/v4 - Gitea — must be provided manually
Work provider
Configure where Agent22 pulls work items from:
| Setting | Description |
|---|---|
| Work source | github, jira, or trello |
| Work provider URL | API URL of the work provider (auto-inferred for GitHub and Trello) |
| Work filter | JQL query (Jira), search query (GitHub), or filter (Trello) to select which items Agent22 picks up |
Provider-specific settings:
| Provider | Additional settings |
|---|---|
| Jira | Jira account email and Jira API token |
| Trello | Trello API key and Trello API token |
| GitHub | Uses the SCM API token for authentication |
Project secrets
You can add key/value secrets to a project. These are injected as environment variables into the agent at runtime.
| Field | Description |
|---|---|
| Key | Secret name (used as the environment variable name) |
| Value | Secret value |
| Viewable | Whether the value is visible in the Hub UI after creation |
Agent configuration
Agents are configured through The Hub and control which coding model is used and what mode the agent operates in.
| Setting | Description | Default |
|---|---|---|
| Name | Display name for the agent | — |
| Mode | work (implement features from work items) or review (review pull requests) | — |
| Project | Which project the agent is assigned to | — |
| Provider | LLM provider — opencode, anthropic, or openai | opencode |
| Model | Model identifier (e.g. opencode/gpt-5.1-codex) | opencode/gpt-5.1-codex |
| API token | API token for the selected LLM provider | — |
Agent statuses
Agents report one of four statuses:
- offline — not running
- waiting — running but no work items to process
- working — actively implementing a work item or reviewing a PR
- errored — encountered a failure
Agent instructions
The Agent instructions field on the project is one of the most important configuration options. This content is written to an AGENTS.md file in the repository root before the coding agent starts work. Use it to describe:
- Project architecture and directory structure
- Coding conventions and style preferences
- Testing expectations (whether to write tests, which framework to use)
- Framework and library preferences
- Any patterns to follow or avoid
Next steps
- Supported integrations — Details on each work provider and Git provider.