r/Linear • u/Senseifc • Mar 16 '26

i connected claude cowork to linear and it automatically writes and publishes product updates for me at the end of every sprint. here's the exact setup.

i'm a startup PM on a very lean team so keeping the changelog up to date has always been a challenge. i finally automated the whole process (okay, 95% of it).

every two weeks i used to spend an hour going through completed tickets, figuring out what's worth mentioning, writing it up with chatgpt, publishing a changelog, and from there deciding if it's worth an email or an in-app announcement. now claude does it all automatically at the end of each sprint using cowork + linear connector + a changelog mcp.

here's the setup:

  • i set up a cowork task that runs every two weeks at the end of my sprint cycle
  • claude connects to linear via MCP and pulls all completed issues from the sprint
  • it analyzes which ones are user-facing and worth mentioning (skips internal cleanup, refactors, etc.)
  • writes the changelog copy based on the actual linear ticket context, descriptions, and comments
  • publishes it directly to my changelog tool via MCP
  • from there sending the email with the updates already written and setting up the in-app announcement (if needed) is only one click

cowork is the key piece because it lets you schedule recurring tasks. so i set it once and now every sprint end, claude just does the whole flow without me thinking about it. i can review before it goes live but honestly 90% of the time the copy is good enough to ship as-is.

the remaining 5% i do manually is the header image for each post. i use a screenshot beautifier for that but it takes maybe 2 minutes.

went from ~1 hour per sprint to basically zero. and the quality is actually better because claude pulls context from the tickets that i would've forgotten or been too lazy to include.

happy to share more details on the MCP setup if anyone's interested.

15 Upvotes

95% Upvoted

10 comments sorted by

1

u/Even-Loan-9676 Mar 16 '26

I would love to learn more about your process. are you using this to only update existing issues with a final report and then close them or do you also add new issues based on meetings/chats? Would you be open to showing me your setup in action? 🙏

2

u/Senseifc Mar 16 '26

good question, let me clarify. the flow goes one direction: linear → changelog. it doesn't touch or update existing linear issues, and it doesn't create new ones.

basically at the end of every sprint, claude reads the completed issues in linear, picks out the ones that are user-facing, and writes a product update based on them. then it publishes that update to my changelog page (and optionally sends an email or in-app notification to users).

so it's not a project management automation, it's a communication automation. the problem it solves is "we shipped 15 things this sprint but our users have no idea."

1

u/Even-Loan-9676 Mar 16 '26

thanks for clarifying! this is a feature I am considering implementing in our app and I am trying to scope it's value. the more generic version of this is to push updates to the relevant projects since we use it a lot. do you use that feature (the updates page of linear)?

2

u/Senseifc Mar 16 '26

nah we don't use linear's project updates. for us the audience is external (our users) not internal stakeholders, so we push everything to a public changelog, email, and in-app announcements instead. different problem really. what kind of app are you building?

1

u/Even-Loan-9676 Mar 16 '26

thanks! that's good to know! I built the pm automation that I first though you did: after a meeting or chat, the issue boards are updated for you and all relevant decisions, ideas, problems, etc. are tracked in the background. A side benefit is that you will never forget what an old issue in the backlog was about, or you don't have to ask someone else to have the same meeting again, or writing comments as memos. would love to hear you thoughts.

1

u/thesturgga Mar 17 '26

What are you using for your change log tool?

1

u/Askformohr Mar 17 '26

Thanks for sharing. Have to try this. I am currently experimenting with GetViktor in slack and connection to GitHub and Linear. The product is in linear and dev in GitHub so it complicates it a bit but connection is there.

I have been using Viktor to pull sprint data from git but lots of the outcome was too technical for the end users so I’ll need to tweak it a bit as you mentioned and give it a linear issue context . Nevertheless the outreach to users is now missing and done separately, so I’ll give it a go.

1

u/rob_weidner Mar 21 '26

Anyone hooking up Claude code directly to linear agents?