Roundtable Strawberry

Consult councils, debug issues and design architectures, worked for you

Hand a companion the outcome. It reads the Roundtable consult councils, does the 4-operation version of the job, and stops for your click on anything that changes a record.

Open the consult council. Check it against something else. Write the change. Move to the next one. That is the Roundtable afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.

What it can do is exactly what Roundtable exposes to an account you authorise and nothing beyond it: 4 operations, 4 reads and no writes. In practice that means it can review code, design architecture and debug issue, and work across the consult councils, debug issues and design architectures.

The Roundtable API stops at Roundtable. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Which Roundtable consult councils does a companion see?

All 4 operations read.

Your account, not a guess at it: a companion can review code, design architecture and debug issue, and the full list below is the whole list, with nothing inferred from Roundtable's documentation.

The consult councils are what most of this inventory is about, alongside the debug issues. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Roundtable admin becomes a queue you review.

  • Review Code
  • Design Architecture
  • Debug Issue
  • Consult Council

Nothing writes back. So what moves the consult councils?

Through the screens you already use.

Roundtable exposes no write operation to a connected account, so a companion drives Roundtable in the session you are already signed into instead, filling the same forms you would to move a consult council, and anything consequential stops for an approval card before it happens.

That is the ordinary case rather than the exception. Most of what a consult council in Roundtable touches has no API pointed at it, and a companion is useful precisely because it does not need one.

Does the consult council sweep have to be asked for every time?

Yes.

Saved as a routine, the Roundtable consult councils pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The operations playbook catalogues the other recurring shapes of the busywork, the Roundtable consult councils sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Roundtable account and a companion works 4 operations in it. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide