Video wird geladen...
Video konnte nicht geladen werden
We like to build tools for builders, which is how Linear Diffs originated, and team is cooking up some amazing new additions. What would want to see more from us to make the best way to understand the changes agents are making? Today we have: - Guided Reviews break... show more
32,440 Aufrufe • vor 20 Tagen •via X (Twitter)
43 Kommentare

Interestingly, some of the strongest positive feedback is coming from large public companies with complex codebases. Linear Diffs seems especially shine where understanding changes takes more effort and careful review matters

More on Guided Reviews:

Linear Diffs:

@linear Show all of the PRs in a stack (instead of parent of/stacked on top of) + let us change/add (GitHub) labels on a PR

@linear Ty

@linear Please please please let me see/add GH labels from Linear!

@linear really like the recent change of showing stacks different. that's huge help.

@linear awesome to hear!

@linear There’s something Guide-adjacent I really find myself missing in all tools as a visual learner… I regularly want to visualize how this change fits into the existing app. Diagrams help. Idk I’m thinking of how to solve this for our team because I want it

@linear if you have specific way you want it, you could try the agent to do it for you. We could productize this better but you could just test what would want to see

@linear Interesting - I’ll play with that on some PRs tomorrow. The Linear agent is one of the few in-app agents I get a lot of utility out of but that never occured to me

@linear Let me know how it goes

@linear yh i'd want the diff sorted by what the agent touched outside the task. the lines you asked for are fine, the ones you didn't ask for are what bite later

@linear ty

@linear Agent-aware review trails would make understanding complex changes much easier

@linear ty

@linear A before-and-after of the actual user flow alongside the diff would be huge. Especially when a change looks harmless in code but changes how the product behaves.

@linear explained code per section is the right instinct. what i'd want next: diffs grouped by intent instead of files - agents touch 12 files for one behavior change and the story gets lost

@linear agent 一天改八百行 人眼看不过来了 工具开始围着审查 agent 转

@linear Could it show which reviewed sections changed after the next agent edit? A green checkmark should have an expiration date when the code underneath it moves.

@linear A clear before-and-after of what changes for the customer would be really useful.

@linear lfg, another beautiful design/product my software factory slopcannon can copy🙌🏽

@linear please build a github alternative i’m begging

@linear Linear Diffs for GitLab would be amazing

@linear Ability to manage PR labels Prioritize schemas and interfaces at top of review, like we use Typespec .tsp files for all schemas and openapi defs, and those are the most important to review

@linear Not specific. But a focus on reducing my workstation to just an iPad with the Linear app would be personally game changing. Also, Is there a format my Buidkite automations can reply with a preview URL that is then clickable in Linear? Vercel previews work natively already.

@linear An overall stacks view that github is sorely missing. The primitive is ok but the lack of UI for it on their part is a big miss. More CI stuff, ideally working closely with the new wave (namespace, blacksmith, depot).

@linear How do you get access to the mobile diff beta?

@linear Guided reviews looks pretty cool, I don't need Linear as of now but this could make me adopt it

@linear linking each diff chunk to the subtask that generated it makes large agent prs so much easier to review

@linear Dependency graph to see what is calling what.

@linear Love cmd+click for go to symbols, but it’s limited to navigating to symbols in the diff. Also, would love hover to see TypeScript info

@linear A diff that shows intent rather than lines. Which requirement did this change serve, and which one did it quietly break.

@linear A flag on lines the agent touched without being asked would save most of my review time

@linear ty

Maybe not entirely Diffs related but I love Loops yet really really struggle to keep up with the output/ongoing work. I have a hard time understanding what shows up in my review tab, it’s not all my open PRs. Moreover the loop creates PRs as a Linear bot and the work gets lost into the ether. I wish diffs gave me a very clear view of what our agent is working on, that it felt like a command centre for the work all my agents are doing for me. I don’t like digging through our PRs in GitHub looking for ones generated by linear-bot (which is not a real user, so I can even search for it)

@linear agents are terrified of deleting legacy logic so diffs get bloated fast. giving us a "ghost code / un-deleted paths" alert in the diff review would be game changing.

@linear i'd want to see what the agent was unsure about, not just what it changed. a diff tells me the result, but the risky part is usually a guess buried in the middle of it. flag those and i can skip the other 90%.

@linear reviews on phone is the one I'd actually use daily how big a diff can it handle on mobile before it gets painful

@linear BYOK 🙄

@linear Absolutely love doing review in Linear! Is it possible to get beta access for review on mobile?

@linear Per-project chat rooms (ala Basecamp) for team and agents would be nice :)

@linear Having actual compiler types and lint's. I keep falling back to vscode so I can see the inferred types and being able to do CMD click and CMD minus so I can navigate the code
