Linear Cycle Progress Digest with OpenClaw
There is no code anywhere in this job. It is reads against Linear, arithmetic over issue counts, and one message with five headings, run once a morning and writing nothing back. OpenClaw is an approachable agent for standing work of that kind, hosted, with the Linear and Slack credentials handled for you.
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 OpenClaw
Preselected for this page — connect your OpenClaw 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 OpenClaw for this agent
Arithmetic, not analysis
Day four of fourteen, seven of thirty eight completed, eleven at the same point last cycle. Producing those three numbers correctly is more valuable than any interpretation laid over them.
Read only by wiring
The allowlist covers Linear reads and nothing else. No issue edit, no comment, no cycle move, so the strongest thing a bad run can produce is an odd line in a channel.
Before you fork
Our cycles are one week rather than two. Does anything change?
No. It reads the cycle length from Linear and reports day N of that length, so a shorter cycle simply reaches its comparison points sooner. The setting worth revisiting is the days in progress threshold in your team scope, because a one week cycle usually wants a smaller number than a fortnight does.
Run it with a different agent
Put Linear Cycle Progress Digest to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.