Grateful we decided to build the @linear mobile app native from the beginning. We wanted to make the best mobile experience we could. Some really nice additions coming soon.

This has sped up my AI coding 20x (prompt at the end): Before building out a big feature, ask ChatGPT 6 Astra to ask you as many questions it needs to fully plan out the idea This is even better than plan mode. plan mode is typically limited to 3 or 4 questions. This is like a super plan mode and makes Astra SO good This has asked me 100+ questions before. Seems like a lot but actually saves you time in the long run The plan it builds will be so detailed and complete that it can basically run autonomously and build the entire thing But here's where you take things to the next level: You also have it take your entire plan and create detailed Linear issues for it It should create 20+ tasks in Linear Then it's as easy as saying "ok work on the next thing" over and over until the feature is done Highly recommend downloading and using Linear if you haven't yet. Amazing project management tool w/ excellent free tier Will basically capture all these details and put your agent on autopilot. It's a 2nd brain. Use this prompt: "I want to build out *describe your feature in detail*. Ask as many questions you need of my to fully understand every detail of what I want to build out. Then take everything you learn, and create super focused and detailed Linear issues. Then begin work" Getting so much more high quality code out with this workflow. You're welcome.

Today I learned that a border-radius can cost you 45 MB of GPU memory and a blank frame per keystroke. Left: rounded bottom corners. Right: rounded all four corners. That's it, that's the fix.

A small quality of life update: When you were using the Linear Agent and a toast was render, it covered the chat. Now the toast renders next to it and changes position when the chat is open/closed.

I run six teams at Warp. Not one of them is engineering. All of them run like engineering teams. Marketing, benefits, people, talent, partnerships, ops. All six on @linear, all six in @claudeai Code. I was a mechanical engineer at Apple, a software engineer at Facebook, then a PM at Google. The most useful thing I took out of all three was watching how those engineering teams worked. Five things they all did: 1/ Everything is written down. Every task has an owner and a state and anyone can go look at it. That sounds like bureaucracy but it does the opposite. Writing work down is what lets ten people work in parallel without a layer of humans in the middle asking each other for updates. 2/ Doing the same thing by hand three times is a bug. An engineer hits the third repetition and writes a script. In ops you can hit the three hundredth and still call it your job. 3/ Deadlines come from breaking the work apart into timed pieces. You cannot put a real date on something you have not decomposed, and the decomposition is the estimate. Every optimistic timeline I have ever been handed was someone skipping that step and hoping. 4/ You ask for the outcome and stay out of the method. People stop coming for permission once the request is clear enough that there is nothing left to ask. 5/ When something breaks, the conversation is about the system that let it break. In engineering that is called a post-mortem. Because of these 5 things, I have changed how my teams operate. Every week, I run a standup with each team around their Linear board. What happened last week, what we are focused on this week, feedback to each other, what is coming. Every engineering org runs this. But almost no operating team does. The usual answer for a high-volume team is to hire an ops person to track the work. I think my people should just be their own project manager. They have ten times the context on what actually matters this week. You lose an entire layer of admin and the prioritization gets better, not worse. None of this would have worked three years ago. The tooling was not there. Now the person who needs the thing can just build the thing, and the work lands in Linear from whoever did it rather than from someone tracking them. The surprise was how fast my team started getting addicted to Linear. Not because they love adding process, but because for most of them this was the first time their work was visible to everyone else. Most operating problems are engineering problems that nobody bothered to engineer.

For the first time, I think issue tracking is dying. At least for small teams. After five years, I shut down our Linear workspace. Every issue I'd file now goes one of two places. If it's urgent enough to deserve tracking, it's urgent enough to hand to an agent right now. It comes back as a PR, not some card rotting in a backlog. If it needs more product thinking than that, it belongs on our feedback board. The issue tracker felt like the middle ground between them. I don't think that middle ground exists anymore. These days my agent workspace is the tracker. What's running is what's being worked on. Nothing else needs a status. This gets harder with a bigger team, I know. But these days, I'm seeing similar across my friends.

At the most product-forward companies, the whole company is starting to work like an engineering team. Marketing, recruiting, finance, ops. The work is visible, owned, and increasingly done with agents. t.co/l3aqiKKLfO

@reallygabriella: I run six teams at Warp. Not one of them is engineering. All of them run like engineering teams. Marketing, benefits, people, talent, partnerships, ops. All six on @linear, all six in @claudeai Code. I was a mechanical engineer at Apple, a software engineer at Facebook, then a https://t.co/Hf8CraUKrs

If Miro had raised $50M total, last at a $20B valuation, and sold for $1.79B in equity value, would we tell a different story about the outcome? They're profitable and still have substantial cash ($435M). The capital wasn’t simply lit on fire. I don’t love overcapitalizing companies, and we’ve chosen not to at Linear when we could have. But "they raised too much" is sometimes a convenient morality tale, not an explanation for why a business with ~$600M in ARR sold for $1.79B.

Darling of 2021, ~20B valuation, 500m raised They don’t tell you this one but “too much capital” is equally likely, if not more, to kill a company than too little You get drunk assuming the party never ends and then boom, you get wiped out https://t.co/2MhZ6TBMWY

Linear docs getting better and better t.co/XxjZuN81ep

@guglielmodanna: Small, big addition to Linear docs: callout components. https://t.co/EJBcdoVd7c

Stickers for @linear

we're back with more software factory alpha on the AI That Works show - @vaibcode and I teamed up with - @tbrownio - discussed how they run a discuss/do/compound loop in their factory, with @linear as the frontend and all agent sessions running on mac minis - @colemurray sharing tales from the trenches rolling out the OSS OpenInspect factory to teams of up to 500 engineers in the enterprises super fun time - catch us every week at 10:15am PT on X and on

Czy ktoś zna jakieś firmy w Polsce które używają @linear ?

Small, big addition to Linear docs: callout components.

Mind-drop: List of MacOS apps I can't imagine not using on a daily basis, fall 2026 and one highlight feature: Do you agree? disagree? what are yours must have apps? comment below! @raycast - This starts them all, tho I don't use the AI features much. ⭐ feature: Clipboard & Browser history @1Password - Been a loyal user for AGES, upcoming Muse integration pays dividends! ⭐ feature: Service account with agents own vault @CleanShot X - Still best screenshotting/quick video. 5th release underwhelming (poor clone of Screenstudio) but otherwise still goated. ⭐ Copying text from screenshots via shortcut @arcinternet Arc browser - Can't stop won't stop, instant tabs mirror between macs, mini arc, account based workspaces. Just a perfect browser. Downside, harder to control for my AIs. ⭐ 3 way tab split for wide monitors Karabiner - setting up hyperkey, and hjkl for arrow keys! ⭐ hypermanagement @cotypist - New entry I can't live without, bought a full aas license, as someone who writes a ton, this local ai app makes writing easier without it being AI slop! ⭐ Your writing dictionary syncing via icloud. Codex - at this point, I cannot see myself using a mac without @OpenAI Codex and start sweating when my usage comes to below 10%. Every config, every Q, every fix, goes through Codex. ⭐ Computer History is so good at recapping your day! Muse - not an app yet, but I just know that once @muse drops it'll sit in my doc! Just so easy to send something to it have it do work! ⭐ 100% the @link integration and the upcoming @1Password integration @cursor - I've long treated Cursor as IDE and kept it around for that, ⭐ OMG the new projects feature is just incredible, no going back! @linear - I started coordinating all my agents and their work in Linear (will do a proper write up soon about how to set this up between all your agents) and now it belongs on my mac ⭐ building an "entity" for each agent separately and assigning work per agent @cleanmymac - with all these agents running, space is at a premium, I constantly need cleaning ⭐ their new CLI is a godsend for agentic cleanings @EndelSound - with all these apps and agents, focus is key! Nothing like Endel out there to get me in focus for prolonged periods of time ⭐ the timer feature that reminds me to take a break Humming bird - moving and resizing windows without having to click their toolbar! Can't go a day without this! @warpdotdev best damn terminal app if you need some agentic stuff ⭐ supports your own keys and X Oauth @slashlast30days not an app yet, but absolutely the best research skill, all my agents have it ⭐ changing the 30 days to 7 or a whole year for tons of research! Phew, I think that's most of it!? Do you agree? disagree? what are yours must have apps? comment below!

Neat! Works everywhere. Issues, docs, reviews. t.co/nJTAY4iJ1W

@guglielmodanna: Small, big addition to Linear docs: callout components. https://t.co/EJBcdoVd7c

A $7B healthcare AI company left a certain legacy issue tracker for Linear. They’ve since logged 80,000+ customer requests and built a system to weigh them by frequency and revenue. t.co/JsxQq3yO5H

Last night at Granola SF Cristina Cordova and Michael Altom, COOs of @linear and @meetgranola, on growing a beloved product into a rapidly scaling company.

I guess @linear Diffs could work well with a wider screen

protip t.co/rVNqvn81GF

@_drankou: TIL that replacing https://t.co/fvb7HLQ8ia with https://t.co/vrnaef8RW5 on PR automatically opens the @linear diff viewer. So I prepared a @raycast script and set up the ✦R shortcut to quickly open GitHub PRs in Linear Guide...‍

TIL that replacing t.co/fvb7HLQ8ia with t.co/vrnaef8RW5 on PR automatically opens the @linear diff viewer. So I prepared a @raycast script and set up the ✦R shortcut to quickly open GitHub PRs in Linear Guide...‍

Paul is cooking t.co/wnuRmd2R8A

@pdotcv: Stickers for @linear https://t.co/b4DBfPuFjY

Not all customer feedback is created equal. @CommureOS's product team uses Customer Requests in Linear to weigh it, by count and by revenue. t.co/5lMVw2J3tR

If product quality is an issue that frustrates you at work, here's the #1 way to make a difference: start fixing shit. Don't try to fix the system, have long discussions about it, complain to your manager/peers. At least not yet. Just go. Fix 5+ things every week. Share with your team. Build momentum. Action builds credibility, and you'll get surprisingly far on it alone. Or just come work with me at Linear

Ableton live session or front-end engineer bragging about his new rendering optimization?

anyone want to grab a merge martini? such a fun happy hour by @merge_api and @linear for @lennysan Lenny and Friends Summit! s/o @danielyegarcia host/planner extraordinaire

We're hiring on my team in @linear! Fully remote, EU based. Check out our careers page for the full job description.

t.co/ZWwmTNAsb7

@_drankou: TIL that replacing https://t.co/fvb7HLQ8ia with https://t.co/vrnaef8RW5 on PR automatically opens the @linear diff viewer. So I prepared a @raycast script and set up the ✦R shortcut to quickly open GitHub PRs in Linear Guide...‍

This was gnarly performance issue, so nice to vibe to it after you've fixed it

Find yourself a designer you can lovingly terrorize @yannglt t.co/8cm2CJgy3e

@maya_ndljk: (Best part is that I did this feature with @yannglt, then handed it off to the guys to ship while I went and had a baby. So good having such a reliable team )

You can ask @linear to explain you the code. It won't judge. Not in a way that you could see, at least.

When codex starts to use computer use instead of API/MCP/CLI to close tickets on Linear.

Made a website that lets you visualize your @linear projects as a connected graph. You just connect a workspace and it shows you all tickets, their status, relationships, etc. Cool to see progress in that manner, and the areas where a bunch of work is left still

for those interested in fully autonomous agentic loops, go --> I’m building the v2 of HWG Web App and I needed to finish a sprint to go live this week. Here's the loop happening: Codex and Cursor plan the sprint with me --> Cursor outlined the Linear tickets (engineering project tasks) --> I approved the sprint --> Cursor writes Linear tickets --> Codex verifies ---> Codex kicks off sprint --> Codex instructs Devin (an AI developer) to write and ship PRs in a dedicated Slack channel for the rebuild, by Linear ticket, with detailed instructions --> Ricia, our Openclaw, monitors the thread for Cursor --> Devin evaluates and writes code and submits branches --> Codex checks code against the sprint and ticket and waits for Cursor --> Cursor monitors the slack channel and PRs --> reviews them adversarially, writes comments on the Linear ticket if issues, comments and merges PR if clean --> Codex monitors the PRs and Linear for merges and issues --> if there are issues, Codex monitors Linear and PR --> instructs Devin --> Devin ships updates and comments on Linear / PRs --> Cursor monitors slack threads thru Ricia.. If merged, Codex reviews PR again, marks Linear ticket and moves to next ticket. We’re almost 50% thru a week sprint. We’ll be done early tomorrow. At a subscription budget of $600 / month ($200 --> Cursor, $200 --> Devin, $200 --> Codex) + usage. ZERO Humans in the loop.