These presentations, like most LLM output, look good but aren’t very informative. The Jev one kept repeating the same point (Jev is by TypeSafe AI, Jev is faster and cheaper) - I bet I could condense it into like 4 slides. The linear one wasn’t entirely clear: it seems you create issues and assign them to agents, and create gantt charts / timelines? Although https://linear.app isn’t much clearer.
But: I think as LLMs fully generate more and more complicated things, we’ll start discovering ways to make them generate with good user control.
My biggest takeaway (as a one man band 20 leagues below this spending time optimizing Gitlab free plan and self hosted runners): they did not worry about any of this until 100M ARR and more 1B valuation[0].
> there's almost no reason to use MCPs if you are running a full-blown terminal agent
I disagree. Adding "https://mcp.linear.app/mcp" and having everything happen (discovery, usage, updates to the API, etc) without having to install or configure anything else locally is a big deal.
Think of Pizza Bot as the "harness"/interface your agents actually run in. You'd still hook up Linear via their MCP server (https://linear.app/docs/mcp) for "what needs doing." Pizza Bot is what handles the run itself (scheduling the interaction, routing tool-call approvals to you, and holding conversation/agent state).
The part that's actually different from "agent in a terminal" or "agent posting to Slack" is that it's built for having a bunch of these running at once. Instead of N terminal tabs or N ticket comment threads to figure out which agent is stuck waiting on you, they land in one inbox — jump between threads, see which ones are paused on an approval or a question, answer, and move on.
Disclaimer: I'm using reduced motion on my phone, please acknowledge this bias before reading my comment
All of those, citing the pricing page, "websites people remember" look the same and use the same handful of effects
- Fade in on scroll
- Big letters
- Punishment of firefox users
- Fullscreen imagery
- Cursor replacement
- Annoying takeover of browser scrolling
Of course you would be impressed if you see something like this the first time. If every third company has websites like this, it gets annoying. I don't remember any of them
They look cool on twitter, how they perform independently of it?
I miss "boring" landings. Pretty ones, not wordpress or wix slop, not "beautiful, that's hard to forget. Make no mistakes" ahem...
hey! thanks for the feedback. Only for web right now - mobile is on the roadmap.
As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling.
Also, all the data you get from a session recording - is data you already have (or could easily get).
As for the culture - I completely agree with you. This is why companies like Linear stand out (https://linear.app/now/zero-bugs-policy). One of my beliefs for starting Opslane is that we can get more companies to understand the bugs that matter and help improve the papercuts in their product.
It would seem like GitHub is in a precarious situation.
We have many agents per employee working in parallel pushing way more commits than was humanly possible before AI, triggering GitHub actions a lot more than the workflows were built for, causing Actions costs to escalate (they really aren't cheap if you compare to hosting it yourself), meanwhile working with YAML workflows is just a pain, and just writing code would be so much more fun and AI compatible[1].
At the same time, GitHub has about ~3 different PR review UIs? And they're all half-bad? Any decently sized PR triggers their "optimized for large PRs" UI which jumps around randomly in my experience. If you don't get that UI and keep the scrolling one (there's an old and a new one btw) then god forbid you click a line number because at some point your browser will randomly scroll back to that line and it won't unstick. Now Linear[2] (and others) is replacing the PR review experience for the agentic era.
I'd love to see a solid AI first Git + CI + reviews.
To me, the thing that stands out about the whole state we're in here is PR review.
Yes, in an ideal world, PRs read well, are a joy to review, reflect what you discussed etc etc. We have to be real; there is only so much we can do to that end.
I'm not sure how the best teams do PR review, from my perspective it sucks. I'm talking specifically about the UX. I've always hated Github's PR page, so I typically reviewed by pulling down the branch and opening the diff with $EDITOR.
These days I think there's really no excuse for the awful UX. Linear (a company that isn't even in the domain of code review) put out a basic PR review feature[0] that is already better than what GH offers. It's simple: point a small model at the PR, group file changes together based on theme, add some commentary and sort by importance (schema changes > openapi spec).
Immediately, so much mental load has been reduced without the reviewer or the requester doing anything. This feature is pretty damn basic, and I think there are obvious next steps like generating visualisations which a dedicated product could find the time to implement.
Keen to hear others thoughts on why this is the wrong approach, or if there are tools in wide use that solve for this, or why this isnt the right problem to focus on.
Yet https://linear.app/Homepage doesn't scroll without jank on mobile.