InfraStudio Agents Start free

Guides

Approve a suggestion

Say yes or no to a suggestion, ask for a change, and put the change on your product.

Last updated

After this guide, you can take a suggestion from the first idea to a change on your product, or say no to it.

Who can do it: a workspace admin or owner, or a person who may run agents in that product. A member can see suggestions and ask about them, but cannot answer them. See Roles.

What a suggestion is

A suggestion is something the agents think should change on your product. Nothing changes until you say yes, unless Auto-merge is on and its checks pass.

Suggestions come from:

  • the Product analytics review, which reads your analytics and errors once a week;
  • Error triage, which reads new errors in Sentry every morning;
  • the Issue implementer, when an issue on GitHub or in Jira gets its label;
  • a change you describe in Chat.

Each suggestion has a label, such as F6. You use the label in Chat and in Telegram.

The stages

A suggestion goes through these stages:

  1. Suggested: it waits for your answer.
  2. Planned: the agents wrote a plan, and wait for you.
  3. Being made: an agent writes the code.
  4. Testing: the change is in a pull request. The automatic tests run, and a second AI reads the change.
  5. On your product: the change is in your code and live.

It can also end as Did not work, or as Closed when you said no or the pull request was closed.

Say yes

  1. Open Suggestions in the side bar. The tab Waiting for you lists what needs your answer.
  2. Open the suggestion. Read What we will change and The report.
  3. Press Yes, work on it. You can add a note for the plan.
  4. Press Send.

The agents write a plan, then the code, and open a pull request. If you want to read the plan before any code is written, press Show me the plan first instead. When the plan is ready, press Yes, work on it to go on, or Make a new plan and write what should be different.

The Overview page has the same buttons, under Waiting for your answer. It also says how many things wait for your answer, and shows Suggestions by stage. More options opens the suggestion with all its buttons.

The reports and plans behind each suggestion are also under Documents, with a search over every report, plan and summary.

Say no

  1. Open the suggestion.
  2. Press No, leave it as it is. You can write why. The next weekly check reads it.
  3. Press Send.

The agents close the suggestion, and its pull request if it has one. They do not suggest it again, unless what they see changes.

A suggestion that is not a change to your code

Some suggestions are work for a person, for example a text to write. Press I will do this myself. The suggestion is marked as yours. The next weekly check looks at it.

When the change is in testing

When the pull request is open, the suggestion offers these buttons:

  • The main button puts the change on your product. Its text starts with "Yes, put it on" and ends with your product's name. It merges the pull request, and the change goes live. To take it back later, revert the pull request on GitHub.
  • Ask for a change: write what should be different. An agent corrects the pull request.
  • Fix the failed tests: shown when the automatic tests failed. An agent finds the cause and corrects the change.
  • Look again for problems: the second AI reads the change once more.
  • No, leave it as it is: closes the pull request.

If the second AI did not approve the change, the merge button says "without the second reading". Read the change on GitHub before you press it.

What you see when it worked

  • The suggestion moves to the next stage. The tab In progress lists the ones the agents work on.
  • When the change is live, the suggestion is under the tab with your product's name.
  • If you linked Telegram or Slack, the bot sends the news there too.

Stop a job

While the agents work on a suggestion, it has the button Stop. It stops the job that is in line or working.

A change larger than the product's limits

Each product has limits on the size of one change: Most files per change and Most lines per change. At first they are 20 files and 600 lines added or removed. You can change them in Product settings.

A change that is larger is not sent to GitHub. The suggestion says Did not work, with these buttons:

  • Use the large change anyway: opens the pull request for the change as it is, up to twice the limits. Nothing runs again, so nothing more is paid. The pull request says that it is large. Paths that agents may never touch stay blocked.
  • Split it into smaller changes: the agents plan it again as smaller changes, one after the other.
  • Start again (a new job, paid again): the agents make the change again from the beginning.
  • No, leave it as it is.

A suggestion that waits for another one

A plan can be split into parts. Each later part builds on the part before it. A later part waits until the part before it is in your code. If you say yes to it too early, the bot says which part it waits for.

When a plan has later parts, the suggestion can offer a button that starts with "Implement and auto-continue through" and names the parts. With it, each later part starts by itself once the part before it is live. Putting each change on your product stays your choice. A failure, a "no" or a closed pull request stops it.

Answer from Chat or Telegram

You can also answer with a word and the label, for example implement F6, reject F6 or merge F6. See Ask in Chat and Commands.

More