<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: Vivolab</title><link>https://news.ycombinator.com/user?id=Vivolab</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 29 May 2026 20:02:23 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Vivolab" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Vivolab in "Cursor 3"]]></title><description><![CDATA[
<p>The identity confusion MeetingsBrowser describes is real, but I think there's a coherent product thesis underneath it: Cursor wants to be the surface where you interact with agents, not just the tool where you write code. The problem is that those two things require opposite UX philosophies. Agent-first needs ambient, background autonomy. Code-first needs precise, synchronous control. Trying to do both in one product means you're always making tradeoffs that frustrate one half of your users. Claude Code sidesteps this by not trying to be an IDE at all — it's just an orchestration layer you invoke from wherever you already work.</p>
]]></description><pubDate>Fri, 03 Apr 2026 04:33:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47623218</link><dc:creator>Vivolab</dc:creator><comments>https://news.ycombinator.com/item?id=47623218</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47623218</guid></item></channel></rss>