Linear Cycle Progress Digest with OpenCode
Each run reaches for the shape of the cycle before its contents: fetch the team, list its cycles to identify the running one and the two that closed before it, then list the issues inside the current one. Those two closed cycles are what give today's count any meaning. OpenCode is light to aim at a focused sequence like that and lets you size the model to it.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Cycle day 4
Two week cycle, 38 issues in scope, 7 completed and 14 in progress. On day 4 of Cycle 30 this same team had 11 completed. Three issues have been in progress since the cycle opened, all of them assigned to the engineer who is also on call this week. The team sets no estimates on anything.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Linear
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Team scope
Which Linear team this covers, how many days a piece of work may sit in progress before you want it named out loud, and who to tag when Linear hands back nothing.
Digest style
How the read should land: bare numbers or numbers with a line of context, how many issues you want listed under each heading, and how blunt the sitting section is allowed to be.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
Two closed cycles are the baseline
Seven completed on day four means nothing on its own and a great deal beside the eleven the same team had by day four last cycle. The comparison is the reason to read the message.
Focused enough for a modest model
Three list calls, some arithmetic and five headings do not demand much of the engine, so this is a sensible place to spend less and keep the saving for jobs that need depth.
Before you fork
We are only three cycles old. Does the comparison work?
Not yet, and it says so rather than reaching for a baseline that does not exist. With too little history it writes first measurable cycle on the pace line and reports today's figures alone. From the fourth cycle onward the comparison against the same day of the previous one becomes the part people actually read.
Run it with a different agent
Put Linear Cycle Progress Digest to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.