Are there thoughts on getting to something more like a "single window dev workflow"? The code editing and reviewing experiences are very disjoint, generally speaking.
My other question is whether stacked PRs are the endpoint of presenting changes or a waypoint to a bigger vision? I can't get past the idea that presenting changes as diffs in filesystem order is suboptimal, rather than as stories of what changed and why. Almost like literate programming.
I really like all these ideas - very similar to what we discuss internally! We need to iterate our way there, but working with Cursor makes some of these visions much more possible
Stacked PRs are a really natural fit for vibe coding workflows, it helps turn illegible 10k+ line PRs into manageable chunks that you can review independently. (Not affiliated with Cursor or Graphite)
Are there thoughts on getting to something more like a "single window dev workflow"? The code editing and reviewing experiences are very disjoint, generally speaking.
My other question is whether stacked PRs are the endpoint of presenting changes or a waypoint to a bigger vision? I can't get past the idea that presenting changes as diffs in filesystem order is suboptimal, rather than as stories of what changed and why. Almost like literate programming.
I really like all these ideas - very similar to what we discuss internally! We need to iterate our way there, but working with Cursor makes some of these visions much more possible
What's the main synergy between Cursor and Graphite that led you to join? Stacked PRs? AI code review? Something else?
Stacked PRs are a really natural fit for vibe coding workflows, it helps turn illegible 10k+ line PRs into manageable chunks that you can review independently. (Not affiliated with Cursor or Graphite)
Congrats on the acquisition! I know its early but would existing cursor users get graphite for free/at a discount?
Im sure we'll do something to simplify pricing and packaging in the future, but not right away
Congratulations Tomas!