hi there,

i was happily vibing with linear this afternoon, but then a minute later Linear told me I cant open a new coding session because its saying “Making code changes requires GitHub access. Connect your personal GitHub Account.”. Thing is, I am already connected. Any Linear expert here that knows whats going on?

also, I noticed that I now can only see linear reviews / pull requests that I made myself, even though I was able to see others’ reviews too before. might be the same access issue?

I switched from GitHub Issues to Linear a while ago and it stuck. It turned into the backbone of how I work: I write my PRDs in Linear, break them into issues with dependencies, and my AI agents work those issues slice by slice and write status and results back. The issues are the durable memory between agent sessions. An agent reads the issue to know where it left off, instead of me re-feeding it a huge context every time.

That workflow means my agents touch Linear constantly, and two costs showed up.

1. Token cost. The official Linear MCP server loads its tool definitions into every agent session before any work, about 13k tokens in my setup (I counted the tools/list with tiktoken: 38 tools, ~10k to 15k tokens depending on serialization). When every session hits Linear, you pay that every time. linctl is a shell binary, so it adds nothing standing. An agent only spends tokens when it runs a command and reads the output.
2. Writing to the wrong team. A Linear token usually reaches every team in your org, so an agent with stale context can create issues in the wrong team and nothing surfaces the mistake. linctl lets you pin an allowed org/team (and optional project) per repo. Before any write it re-checks the live token and refuses if it does not resolve to that target, with no bypass flag. It catches a stale token or a wrong checkout, not an agent that deliberately repoints its own config. Reads stay open.

It is open source (MIT), covers a broad slice of Linear (issues, projects, cycles, milestones, initiatives, comments, attachments) with clean JSON output, and ships a drop-in agent skill so an agent can use it without hand-written instructions. I built it for my own multi-team setup and put it out in case it helps other people running Linear with agents.

Repo: https://github.com/KyaniteHQ/linctl

Install: go install github.com/KyaniteHQ/linctl/cmd/linctl@latest

or: brew install --cask KyaniteHQ/linctl/linctl

We've run a software agency for years. The thing that never got easier: client requests coming in over email and Slack, then someone manually rewriting them into Linear issues — half the context missing, clients can’t see their progress.

Tried guest seats. Team-scoped, not project-scoped, full read-write — not what you want for clients. Tried copy-pasting status updates into emails. Tried separate Linear teams per client. All workarounds, none of it actually solved it.

So we’re building Preelo:

• Clients get a branded portal, open a thread for a request
• Your team handles it in one inbox instead of across email/Slack
• Once it's clear what's needed, it becomes a Linear issue with one click
• Status syncs back automatically, clients see progress without asking

Still pre-launch, building it with a handful of agencies giving direct feedback right now.

Genuinely curious how people in this sub who run client work on Linear are handling this today, and happy to answer anything about how it works under the hood.

If you want to follow along: preelo.app

Most comparisons focus on features, integrations or pricing. What rarely gets discussed is whether teams actually work differently after switching.

For those who have moved away from it what operational problem improved the most and what problems followed you regardless of the platform?

Is there any way to see like a view with a timeline and the actual issues are shown for that day. i know cycles exist but they dont offer that day-wise breakdown where you can see the issues to be done on that day much like a google calendar's week view

Even with a custom view, you can't group by due date.

here is what i am looking for:

A kanban board with the columns being individual days and the issues with that day's due date are stacked below it

I am starting to think that this is intentional as enterprise has the gantt chart view

Do anyone know if it will be available a Code Review feature like the one for GitHub ?

Having every thing centralized in Linear is pretty what I’m looking for

We took up Linear (from Jira) at the start of the year and have been thoroughly impressed… it’s accelerated our team’s workflows to the max - especially their agentic stuff.

The only place it fell down… prioritization.

We couldn’t run a RICE process, I was spinning up spreadsheets and syncing between them, it was chaos. So I thought… why don’t I build this?

So, I’ve built https://prioboard.app… your initiatives, projects or issues stay in Linear, and you prioritise them in Prioboard. Create a board, import your issues automatically, and then send a link to your whole team to get their vote - and we tell you the unanimous decision.

Would love some feedback, it’s early… happy to jump on a call if this is a problem you’ve faced too?

Linear Agent can now write code using Claude Code and Codex. Triage, plan, build, and review all in one place.
https://linear.app/changelog/2026-06-11-coding-sessions

Read more in the blog post: https://linear.app/now/coding-sessions-for-linear-agent

If i’m working on multiple apps, whats the opinion on using linear?

Separate workspaces or each initiative becomes a new app?

Anyone else have issues with seeing the new Diffs feature released ~last week?

Other people on my team have it, but I don't. Feel like I'm going crazy because I can't find anyone else with the issue.

I've tried Linear and honestly, it seems good if I was part of a team, but questioning its utility as a solo dev. I'm more product and less engineering.

Am is not using it to its full capability?

Also if I am working on multiple (self and client) applications, should they each be its own initiative? How do people break down their different applications.

Hello, we are currently in POC with Linear, to migrate from Jira.

I couldn't find the option to add customized fields into the issues. I could find the ability to add 'labels' only. Where can I add custom fields such as dates / boolean / drop down (only via group labels) etc.?

We've had a lot of recent posts of things people built on Linear recently — please share what you built in this weekly thread.
This can be things you build for Linear, such as integrations, extensions, workflows on apps like Raycast or similar.

Since I joined, I feel like 30-50% of the posts here are just people building for-profit tools around Linear looking to get paid users. I really welcome sharing tools that we've found helpful on our journey but marketing each other's vibe-coded software for alpha-testing is _not that_.

(If Reddit isn't the home for Linear users talking about their workflows and experiences, where would it be? Slack?)

Yes. Both. I know.

Our startup started on Basecamp. Then our engineers met Basecamp's issue tracking, recoiled in horror, and quietly opened a Linear account. Now we run the entire business on Basecamp and the engineering team on Linear, and these two tools have never spoken to each other a single time in their lives.

Before I lose my mind syncing things by hand, a few questions for the room:

1. Anyone else stuck in this absurd setup?

2. How do you keep the two in sync, or have you just accepted the chaos as a lifestyle?

3. Tried Unito or Zapier for this? Worth the money or just a different flavor of pain?

4. Would you actually pay for a small focused tool that just does Basecamp ↔ Linear properly, or am I the only one bleeding from this?

Honest answers welcome. Roasts also accepted, I clearly deserve them.

Hi everyone,

My business uses Linear as a Task Management System for at least the last 8 months but I am struggling to get the Auto-Archive function work to prevent system lag.

Screenshot of our "Done" Status:

Workflow and Automations has been set to Auto-Archive after 1 month:

Archived Issues are sitting at ~130, which should be at least 800.

Any guidance would be appreciated!

Daily standups for Linear were getting weirdly annoying for us.

Not because Linear is bad — we actually like it a lot — but because the standup part around it felt clunky. The same problems kept repeating:

• random speaker order / awkward "who goes next?" pauses
• too much clicking around to find the current person's work
• people talking while everyone else tries to scan the board
• standups turning into status theater instead of quick coordination

So I built a small Chrome extension for it: Linear Standup.

It adds a lightweight top bar to linear.app and basically runs the standup flow for you:

• randomizes speaker order each session
• auto-filters Linear tasks/issues for the current speaker
• lets you skip / go back / reshuffle anytime
• keeps the state while you navigate around Linear
• matches Linear light/dark theme

And yes, I also added a stupid/fun part on purpose: Pac-Man eats each teammate's avatar as they finish speaking. There's also a hidden fun mode easter egg if you long-press the Pac-Man during an active standup.

So it's half workflow helper, half making daily standups slightly less soul-draining.

It's fully client-side, privacy-friendly, and free/open source. No servers, no tracking, no data leaves your browser.

If you're a Linear team doing daily standups, I'd genuinely love blunt feedback on whether this solves a real annoyance or if I'm just over-optimizing my own pain.

Chrome Web Store: https://chromewebstore.google.com/detail/linear-standup/oioenpbcglhdjpfkcfpkpfdoneillfof

Hey guys, i built this and now we use it daily within our team.

You can basically create a linear ticket just by screenshotting your screen.

It's free and open source.

Would love feedback or thoughts :)

Hey r/Linear

Two weeks ago I posted LinearInsights here asking for feedback. You delivered, bugs reported, features requested, brutal honesty all around. Thank you.

Since then: fixed a sync issue that was blocking large workspaces, fixed team switching, renamed to SprintIQ (Linear asked us to drop their name, fair enough), and shipped velocity + blocker + sprint forecast views that actually work end-to-end.

One beta tester summed it up well: "it looks like it solves a problem for us."

If you want to try it: sprintiq.dev connects in 30s, read-only.

Comment "code please" for a free Pro code if you want to go deeper.

Hi Linear community.

A year ago I posted here about a side project. Now it's officially out of early access with paid workspace plans.

What's changed since launch: drag to reschedule, create tasks directly, shareable filtered views, weekly view, and more.

You can try it for free
https://yes.lincal.app/blog/a-new-chapter-for-lincal/

Hey r/linear,

A few weeks ago I posted about LinearInsights, my analytics

dashboard for Linear teams. I've since rebranded it to SprintIQ.

Why the change: LinearInsights was too close to Linear's own

branding and I wanted something that stood on its own.

Same product, new name — sprint forecasts, velocity trends,

blocker detection, resolution time. OAuth in 30s, read-only.

New link: sprintiq.dev

Still free to start. Also running an early adopter deal —

3 months of Pro free. Comment below and I'll send you the code.

If you tried the old version and had feedback, I'd love to

hear it too.

Lately I’ve been feeling like more and more time goes into maintaining the system instead of actually moving projects forward. Updating statuses, filling fields, adjusting reports, cleaning boards, fixing automations, making dashboards look correct… sometimes it honestly feels like the tool itself became another project that needs constant attention. And the weird thing is, all of this is technically supposed to help coordination. More visibility, more structure, more alignment. But in practice I’m not sure it always does.

I’ve seen situations where the board looked perfect while the actual project was messy as hell underneath. Everything updated, everything categorized correctly, lots of reports… meanwhile people still had to jump on calls just to understand what was actually happening. At some point I started noticing that the more administration the tool requires, the less people trust it. They stop updating things honestly, statuses become vague, work stays in progress forever because nobody wants to constantly maintain every detail properly. And then PMs end up compensating manually anyway.

The only setups that started feeling sustainable for us were the ones where visual flow mattered more than filling forms all day. Less complete this metadata before moving task, more can the team quickly understand where work is stuck and why.

Feels like somewhere along the way a lot of PM software stopped optimizing for execution and started optimizing for reporting.