Hand the DevRev comments to a companion
A companion works the 6 operations your DevRev account exposes. It can create a ticket and create a task, and every one of those waits on an approval card showing the comment before it changes.
Open the comment. Check it against something else. Write the change. Move to the next one. That is the DevRev afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a comment until you approve it.
What it can do is exactly what DevRev exposes to an account you authorise and nothing beyond it: 6 operations, no reads and 6 writes. In practice that means it can create a ticket, create a task and create or update custom schema fragment, and work across the comments, custom schema fragments and issues.
The DevRev API stops at DevRev. 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.
Does it read the comments or ask you for them?
In the tab.
DevRev exposes no read operation to a connected account, so a companion opens DevRev in the session you are already signed into and reads the screens you would.
The comments are what most of this inventory is about, alongside the custom schema fragments. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of DevRev admin becomes a queue you review.
What happens before it can create ticket?
All 6 write operations wait for you.
A companion can create a ticket, create a task and create or update custom schema fragment, and each one is staged on an approval card first: you see the comment, the field and the new value before it lands in DevRev.
Nothing in DevRev is sent, changed or deleted on your behalf without that click, and a rejected card leaves the comment exactly as it was. The gate is the same one on every surface, described at security.
- Create Ticket
- Create Task
- Create or Update Custom Schema Fragment
- Create Opportunity
- Create Issue
- Create Comment
Does the comment sweep have to be asked for every time?
Yes.
Saved as a routine, the DevRev comments 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 operations, the DevRev comments 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