The tracker keeps itself honest.
Cedric creates issues from what the team decides and reads back projects and cycle status in plain words, before anyone has to ask twice.
$50 in free credits when you sign up. No card needed.
- Trackers drift because filing happens later, and later loses to everything.
- Cedric turns what the thread decided into Linear issues, filed on your yes with the context attached.
- Cycle and project status read back in plain words: done, in progress, untouched, and what that means for the date.
- The slip shows up on day eight, not in the retro.
- Status reporting becomes a scheduled post, not a meeting.
What can a Linear AI agent do?
A tracker is a model of reality, and models rot when updating them is a chore. Work gets decided in threads and meetings; Linear finds out days later, if at all. A Linear AI agent shortens that pipeline to one approval: when the conversation lands on 'we should fix that', Cedric drafts the issue, description, context, the thread it came from, and files it into the right project on your yes.
Reading back is the daily value. 'How is the cycle looking' should not require opening views and counting: Cedric reads issues, projects and cycle status and answers in plain words, including the part dashboards are polite about, the cluster of untouched issues that means the date is going to slip.
An AI employee that reads the tracker every day is also the one that notices what people miss on Fridays: the bug thread that never became an issue, the project with no movement in a week, the cycle quietly overcommitted. It says so in the channel, early, while the fix is still cheap.
Cycle check
Day eight, read honestly.
Felix Andersson9:14 AM
@Cedric how is the cycle looking?
CedricAPP9:15 AM
Day 8 of 14. 19 of 31 issues done, 5 in progress, 7 untouched. The untouched ones cluster on the export feature; at the current pace that slips. Also: two bugs from this week's thread never made it into the tracker, the CSV encoding bug and the empty-state crash. I can file both into the current cycle.
Issues from threads
Decided in chat, filed in Linear with context and links, on your yes.
Status, plainly
Projects and cycles read back honestly, including the untouched cluster nobody mentions.
The slip, early
Pace against the date, flagged while there is still a week to do something about it.
Connect Linear in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Linear from the dashboard
Open the Integrations page and sign in with Linear on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what's the status of the current cycle?". You describe the outcome; Cedric picks the Linear actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Linear into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
The plan lives in Linear; the proof lives in GitHub, and Cedric reading both is how planned and shipped stay the same list. Action items from a call it attended through Google Meet can land as issues the same afternoon, owners attached.
Meeting to tracker to repo, one assistant, no retyping at any step.
Where the limits are
Cedric files and reads; it does not run your roadmap. Priorities, estimates, and what makes the cut stay product decisions. It will tell you the cycle is slipping; deciding what drops is the part that stays human.
Cedric sees what the Linear connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes, natively. Linear is one of the apps Cedric knows deeply, with a built-in playbook: connect it once from the dashboard and ask in plain words, with no workflow to build and no fields to map. It sits alongside 3,200+ other connectable apps.
Yes. From a call Cedric attended, the action items come out with owners, and the ones that are real work can be filed as issues on your yes, the same afternoon, while the context is fresh.
No. It creates and reads back. Anything that changes the plan is proposed in the channel and waits for a person to say yes.
Yes: a cycle summary every morning or every Monday, the same honest shape each time. The status meeting becomes a message people can read in twenty seconds.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Close the gap between decided and tracked.
Install Cedric, connect Linear, and let the cycle report itself.
100K credits ($50) on sign up. No card needed.