Komos StrawberryTask runs and queue task runs out of Komos without the tab work
Hand a companion the outcome. It reads the Komos task runs, does the 4-operation version of the job, and stops for your click on anything that changes a record.
Open the task run. Check it against something else. Write the change. Move to the next one. That is the Komos 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 Komos exposes to an account you authorise and nothing beyond it: 4 operations, 4 reads and no writes. In practice that means it can queue task run, list tasks and list task runs, and work across the task runs, queue task runs and tasks.
The Komos API stops at Komos. 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.
Where do the task runs come from?
All 4 operations read.
Your account, not a guess at it: a companion can queue task run, list tasks and list task runs, and the full list below is the whole list, with nothing inferred from Komos's documentation.
The task runs are what most of this inventory is about, alongside the queue task runs. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Komos admin becomes a queue you review.
- Queue Task Run
- List Tasks
- List Task Runs
- Get Task Run
Nothing writes back. So what moves the task runs?
Through the screens you already use.
Komos exposes no write operation to a connected account, so a companion drives Komos in the session you are already signed into instead, filling the same forms you would to move a task run, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what a task run in Komos touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Can it queue task run every morning by itself?
Yes.
Saved as a routine, the Komos task runs 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 Komos task runs sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
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