Reference
Product settings
Every setting on a product's settings page, in the order of the page, with what it does.
Each product has its own settings page. Open Settings → Products, and press Settings on the product's row. On the Agents page, the link Product settings opens the same page.
Who can change the settings: a workspace admin or owner, or a person who may change everything in that product. Everyone else sees the settings, but cannot change them. See Roles.
How saving works
- A switch saves at once.
- A field you type in is kept until you save. A bar at the bottom of the window counts the unsaved changes and names their parts. Press Save to save them, or Discard to drop them. Enter in a one-line field saves too.
- After a save, each part says Saved., or what is wrong. A part with a problem saves nothing.
The top of the page shows the product's repository, its name, and how many suggestions, jobs and documents it has. All products goes back to the list, and Open overview opens the product's Overview.
The technical settings are at the end of the page, inside Technical settings, which is closed at first.
On or off
| Setting | What it does |
|---|---|
| The platform runs the agents of this product | On: the platform runs this product's agents. Set the keys on the Integrations page first. Off: no agent of the platform starts for this product, whatever its switch says. The line above it says if the agents are online. |
| Put this product away | Archives the product. It is hidden from the Overview, the list of products marks it "archived", and no agent works on it. You can undo it. An archived product does not count toward the active products of your plan. |
Agents
One row for each agent of the product, with what it does and what starts it.
| Setting | What it does |
|---|---|
| The switch | Turns the agent on or off. Off: it does not start by itself. You can still start it with Start now on the Agents page. |
| Options | The agent's own options, such as Act for or Label that starts it. See Agents for every option. |
| Technical settings under a scheduled agent | Schedule: when the agent starts, in the platform's local time. |
Start now… at the top of the part opens the Agents page. Under Auto-merge, the part also lists the readiness checks. See Turn on Auto-merge.
If an agent needs a key that is missing, its row says which one, with a link to Integrations.
Name
| Setting | What it does |
|---|---|
| Name | The product's name, as the app shows it. |
Repositories
This part shows when the product can have more than one repository. It lists the product's repositories, the main one first.
| Setting | What it does |
|---|---|
| Add a repository | Adds another repository of the product, up to your plan's limit. |
| Details | The repository's own Default branch, CI workflow name, Deploy job name and Health URL. The row's own Save saves them. |
| Remove | The agents stop following the repository. Not on the main one. |
See A product with several repositories.
Messages
| Setting | What it does |
|---|---|
| Slack channel | Where this product's news goes in Slack. Team plan. Empty: the workspace's channel. |
| Telegram chat id | A Telegram group for this product's news. Easiest: add the bot to the group, make it an admin, and send /link and the product's short name there. Empty: your private chat with the bot. |
See Get news in Slack or Telegram.
Privacy
Before anything is stored or sent, the platform removes e-mail addresses, IP addresses, phone and card numbers, IBANs and keys from what agents read from your integrations and from what they write.
| Setting | What it does |
|---|---|
| Private product | Telegram, Slack and the daily e-mail say only that there is news, with the label of the suggestion and the number of its pull request. The content stays on the website. |
| E-mail domains to keep | Your own domains, one per line, such as acme.com. Their addresses stay in reports. Every other address is removed. |
See Repository rules and privacy.
Technical settings
Where the code is
| Setting | What it does |
|---|---|
| Repository | The product's GitHub repository, as owner/name. |
| Default branch | The branch the agents read and make changes against. Usually main. |
In a product with a Repositories part, these two are on each repository's row instead.
Repository rules
| Setting | What it does |
|---|---|
| CI workflow name | The exact name of the GitHub Actions workflow that runs on the main branch after a merge. The platform follows its deploy. |
| Deploy job name | The job in that workflow whose success means that your product runs the change. Empty: a green run on the main branch counts as the release. |
| Health URL | An https address that answers 200 when your product is healthy. Auto-merge checks it after each deploy it starts. Redirects and private addresses do not count. |
| Most files per change | The most files one change may touch, from 1 to 200. Empty: 20. |
| Most lines per change | The most lines one change may add and remove together, from 10 to 10,000. Empty: 600. |
| Extra paths agents may never touch | One regular expression per line, matched against the paths in the repository. CI, Docker, migrations, secrets and dependency files are always blocked. |
In a product with a Repositories part, the first three are on each repository's row instead. See Repository rules and privacy.
Analytics and AI
| Setting | What it does |
|---|---|
| PostHog project ID | The number in PostHog's address, such as …/project/12345. The agents read only this PostHog project. |
| AI provider | The provider the agents run on, with your key from the Integrations page. Automatic: the first provider with a key is the default. |
| Models per kind of job | A model for each kind of job. Empty: the provider's default. On AWS Bedrock use Bedrock model IDs; on Azure, your deployment's name. |
The kinds of job in Models per kind of job are: Product analytics review, Error triage, Plan, Making a change, Correcting a change, Second reading of a change, PR reviewer, CI fixer, Issue triage, Docs updater and Question.
See Add your AI key.
Jira
| Setting | What it does |
|---|---|
| Jira project key | The key of your Jira project, such as ACME. Its issues that get the Issue implementer's label become pull requests here. The Jira key is on the Integrations page. |
See Connect Jira.
Other scheduled work
Scheduled work that is not one of the agents, such as the Collector (Clarity). Each row has its schedule, its state, its last job, its next start and a switch. Edit opens its fields. Add scheduled work adds one.
| Field | What it does |
|---|---|
| Short name | Lowercase letters, digits and dashes. Only when you add one. |
| Kind | Product analytics review or Collector (Clarity). Only when you add one. |
| Name | The name the app shows. |
| Schedule (cron, the platform's local time) | When it starts, in the platform's local time. Empty: only when you start it with Start now on the Agents page. |
| Model | The model it uses. Empty: the default for the kind. |
| Effort | How hard the model thinks: low, medium, high, xhigh or max. |
| Most turns | The most steps of one job, from 1 to 500. |
| Time limit (min) | The most minutes of one job, from 1 to 240. Your plan can set a lower limit. |
See Connect analytics and Sentry.
Webhooks
This part shows once the Jira project key is saved.
| Setting | What it does |
|---|---|
| Make the Jira webhook | Makes the address that tells the agents about Jira issues the moment they are created or changed. The page shows the URL and the JQL line once. A new secret replaces the old one. |
Delete this product
Delete this product… removes the product from the platform, with everything the platform keeps for it: its suggestions, jobs, documents, chat, scheduled work, agents and stored keys. It cannot be undone. Your repository is not touched, and neither are webhooks set up on GitHub or Jira. The audit log keeps that it was deleted, and by whom.
To confirm, type the product's short name. Put it away instead archives the product, which you can undo.
Only a person who may delete the product sees this part.
More
- Agents: every agent and its options.
- Plans and limits: how many products, repositories and jobs your plan has.
- When something does not work.