The issue work, done and queued for one look
Hand a companion the outcome. It reads the Linear (API key) issues, does the 17-operation version of the job, and stops for your click on anything that changes a record.
Open the issue. Check it against something else. Write the change. Move to the next one. That is the Linear (API key) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a issue until you approve it.
What it can do is exactly what Linear (API key) exposes to an account you authorise and nothing beyond it: 17 operations, 10 reads and 7 writes. In practice that means it can update an issue, update an initiative and remove a label from issue, and work across the issues, initiatives and comments.
The Linear (API key) API stops at Linear (API key). 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 issues come from?
10 of the 17 operations are reads. Your account, not a guess at it: a companion can search issues, list workflow states and list views, and the full list below is the whole list, with nothing inferred from Linear (API key)'s documentation.
The issues are what most of this inventory is about, alongside the initiatives. A companion can hold all 17 of these operations and forty open tabs in the same pass, which is how an afternoon of Linear (API key) admin becomes a queue you review.
- Search Issues
- List Workflow States
- List Views
- List Projects
- List Labels
- List Initiatives
- List Comments
- Get View Issues
- Get Teams
- Get Issue
What happens before it can update issue?
All 7 write operations wait for you. A companion can update an issue, update an initiative and remove a label from issue, and each one is staged on an approval card first: you see the issue, the field and the new value before it lands in Linear (API key).
Nothing in Linear (API key) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the issue exactly as it was. The gate is the same one on every surface, described at security.
- Update Issue
- Update Initiative
- Remove Label from Issue
- Create Project
- Create Issue
- Create Initiative
- Create Comment
What does the recurring issues pass look like?
Yes. Saved as a routine, the Linear (API key) issues 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 planning, the Linear (API key) issues 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