Agents

The agents are AI helpers. Each one has its own kind of work. This page lists every agent: what starts it, whether it is on for a new product, its options, and what it needs.

You turn an agent on or off, and start it by hand, on the Agents page. You change its options in Product settings.

A few rules hold for all agents:

• An agent that starts from GitHub acts only for people with write access to the repository, unless its option "Act for" says everyone. On a public repository, anyone can open an issue, and each job uses your AI account.
• When a new agent comes to the platform, it is off on the products you already have. Nothing new starts working on your code unless you turn it on.
• The times of the scheduled agents are in the platform's local time.
• Each job of an agent counts toward your plan. See Plans and limits.
• To start an agent by hand, a person needs the permission to start an agent now. See Roles.

PR reviewer

Reviews every pull request when it opens, and again after new changes. It posts its review on GitHub, with comments on the lines.

• Starts: A pull request opens, or gets new changes.
• On for a new product: Yes.
• Start it by hand: Yes, with Start now on the Agents page, for the pull request you name.

Its options:

• Act for: People with write access or Everyone. Default: People with write access. Members: people with write access to the repository. Everyone: anyone who can open one, which on a public repository lets strangers' requests spend money from your AI account.
• Review draft pull requests too: On or off. Default: Off.
• Review again after new changes: On or off. Default: On.

CI fixer

When the automatic tests (CI) fail on a pull request, it reads the logs and the code, finds the cause and comments the fix. It can put the fix on the pull request's branch instead.

• Starts: The automatic tests fail on a pull request.
• On for a new product: Yes.
• Start it by hand: Yes, with Start now on the Agents page, for the pull request you name.

Its options:

• Put the fix on the pull request's branch: On or off. Default: Off. Only for a pull request whose branch (its own copy of the code) is in this repository, and never on the main branch of your code. Off: the fix is a comment.
• Attempts per pull request: A number from 1 to 5. Default: 2.

Issue triage

Reads each new issue (a request or a bug report) against the code, labels it with your own labels, and comments what it found: the likely cause, the files involved, and what is missing to act on it.

• Starts: A GitHub issue is opened.
• On for a new product: Yes.
• Start it by hand: Yes, with Start now on the Agents page, for the issue you name.

Its options:

• Act for: People with write access or Everyone. Default: People with write access. Members: people with write access to the repository. Everyone: anyone who can open one, which on a public repository lets strangers' requests spend money from your AI account.
• Add labels: On or off. Default: On.
• Comment on the issue: On or off. Default: On.

Issue implementer

Turns an issue into a plan, the code and a pull request that fixes it. It starts when the issue gets the label below, or when someone writes @infrastudio-ai implement on it.

• Starts: An issue gets the label agent:implement, or someone writes @infrastudio-ai implement on it.
• On for a new product: Yes.
• Start it by hand: Yes, with Start now on the Agents page, for the issue you name.

Its options:

• Label that starts it: Text, 1 to 50 characters on one line. Default: agent:implement.

Mentions

Answers when someone writes @infrastudio-ai in an issue or a pull request: questions about the code, and the commands review, fix, triage and implement.

• Starts: Someone writes @infrastudio-ai in an issue or a pull request.
• On for a new product: Yes.
• Start it by hand: No. It only answers what happens on GitHub.

Auto-merge

Off unless you turn it on. Puts the change of a pull request into your code by itself, once the automatic tests passed and the review (a second AI reads the change) approved that same version. Then it watches the change go on your product and checks that your product still answers at its health address. Files named in the repository's ADLC policy, and the platform's protected files, always wait for a person. Shadow mode only says what it would do; Live mode needs every ADLC check in the product's settings to pass.

• Starts: The automatic tests pass on a pull request and the review approves it.
• On for a new product: No. You turn it on.
• Start it by hand: No. It only answers what happens on GitHub.

Its options:

• Mode: Shadow or Live. Default: Shadow. Shadow: only says what it would put into your code, and changes nothing. Live: puts changes into your code, and they go on your product.
• Pull requests: The agents' own or Also people's, with write access. Default: The agents' own. The agents' own pull requests, or also those of people with write access that the PR reviewer approved. Never pull requests from forks (copies of the repository on other accounts).
• At most this many changes a day: A number from 1 to 10. Default: 3.
• Minutes to watch your product after each change goes on it: A number from 10 to 120. Default: 30. The next change waits until then. If your product fails its health check twice in this time, Auto-merge turns itself off and opens a pull request that takes the change back.

Docs updater

Once a week, reads what changed in the code and updates the README and the docs to match, as a pull request.

• Starts: Every Monday at 05:00, in the platform's local time.
• On for a new product: No. You turn it on.
• Start it by hand: Yes, with Start now on the Agents page.

Product analytics review

Once a week, reads your analytics (GA4, PostHog, Clarity) and your errors, and suggests what to change, ranked. Nothing changes until you say yes.

• Starts: Every Monday at 03:30, in the platform's local time.
• On for a new product: No. You turn it on.
• Start it by hand: Yes, with Start now on the Agents page.
• Needs: Google Analytics 4 or PostHog, connected on the Integrations page.

Error triage

Every morning, reads new and rising errors in Sentry, finds their cause in the code, and suggests fixes.

• Starts: Every day at 06:00, in the platform's local time.
• On for a new product: No. You turn it on.
• Start it by hand: Yes, with Start now on the Agents page.
• Needs: Sentry, connected on the Integrations page.