Linear Cycle Progress Digest with Codex
A morning read of one Linear cycle is three list calls and a message, and it costs the same on a twenty issue cycle as on a two hundred issue one. The figure that multiplies your bill is teams, not issues. Codex is quick on a bounded fetch like this, which keeps the per morning number small enough to stop thinking about.
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 Codex
Preselected for this page — connect your Codex 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 Codex for this agent
Teams multiply, issues do not
Scope changes during a cycle move the numbers in the message and not the cost of producing it. Budgeting means counting the teams you point it at and the mornings in a month.
Three fetches and a post
Team, cycles, issues, message. There is no exploration step that can run long, which is what makes the per run cost sit in a narrow band.
Before you fork
We want it on eight teams. Is that eight subscriptions?
It is eight forks of the same workflow and eight scheduled runs a morning, each with its own team scope, its own threshold and its own channel, sharing the Linear and Slack connections. Adding a ninth team later is another fork and another schedule rather than any rebuild.
Run it with a different agent
Put Linear Cycle Progress Digest to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.