Nemo Feng (@nemofq) header
Nemo Feng (@nemofq) profile picture

Geek

Seattle, WA
Joined January 2011
Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)Photo by Nemo Feng (@nemofq)
I read every word of @andrewchen's article and here’s what I think. If we enter a future with no network effects from using the same agents, then no matter which agent I use, it can talk to Andrew’s agent (built by a different company) to schedule a meeting for us, decide if @a16z should invest in @waku_agent, or book dinner with other founders, as agents smoothly share all context on preferences and schedules. Horizontal agents would have no moat and would not dominate. Businesses may soon realize they should demand their own personal or business agents, hosted or built in-house, assembling components from various providers. As long as agents can communicate, research, and execute via shared open protocols, it doesn’t matter if partners or family use different agents. Agents communicate much faster in JSON than in lengthy human conversations, so they can execute in a fully outcome-driven way because they know who we are. Most importantly, they can own their data which is imo the single most important thing for a business in an agentic world where you don’t need LinkedIn for candidates or ThomasNet for suppliers. You should own your preferences, schedules, and tastes. Whoever owns the context and daily behavior of individuals and businesses will stay relevant, even amid competition from large corps. But if network effects exist and open protocols for agent diversity are limited, then centralizing context becomes the strongest moat for these tech giants, which I hope does not happen. (Wrote the above myself, with the language slightly polished by @grok)
DO AGENTS HAVE NETWORK EFFECTS? We are seeing a new wave of general purpose consumer-friendly agents, and it’s causing many thousands of AI startups to re-evaluate their place in the market. Will these new horizontal players take over completely? Will it be winner take all? Can products that focus vertical use cases survive? The new wave of products - Muse, Town, Instinct, Grokbot, etc - come from taking the power and magic of Openclaw/Hermes but wrapping it in polished, secure, consumer-friendly experience. This is only the beginning, and soon every major tech company will throw their hat in the ring and thousands of startups that have been working on vertical agents in X (travel, shopping, family, work, SMB, etc etc) have big existential questions to answer. The simple case against winner-take-all dynamics: These agents are tools, not networks. They inherently provide a solo experience, and although packaged as chat experiences, they don’t have network effects the way that Whatsapp or phone networks do. They’re more like email clients - I can use Superhuman and someone else uses Outlook and someone else is on Gmail, but in the end we just send email to each other. In that metaphoi, if a Muse agent encounters a Instinct agent, they will just figure out how to talk to each other by building APIs, or using email/messaging/etc., so that there’s no advantage to everyone running the same thing. Further, you can swap out the underlying LLM - as we saw in the Claude vs Clawdbot saga - things will still work. The memory and underlying context are just text files, and AI are great at porting things from one system to another. So where’s the moat? Just because they are tools today doesn’t mean they can’t evolve into networks. As I’ve written about in the past, instead of discussing “network effects” as a vague/amorphous concept, let’s instead overlay it against core KPIs each product has to build against: - Acquisition network effects: More users** = lower CAC, higher virality, more signups - Engagement effects: More users = higher retention, deeper usage, more frequency - Monetization effects: More users = higher ARPU, higher conversion, more share of wallet (**PS. and by “more users” of course I actually mean, of course, higher network density with more interconnection within/across networks. Not scale effects) So looking at these sub-categories of network effects, you might ask: What are the features that you’d build to actually create network effects in agents? How does this category become winner-take-all? Acquisition: In the pre-AI world, network effects in customer acquisition were driven by users taking actions that then bring in even more users - whether that’s sending an invite, sharing a piece of content, or getting mentioned in a comment. Those users would then join the network, repeat the same actions, creating more viral loops that would throw off more users. In the post-AI world, both users and agents can initiate these loops. An agent might suggest, “hey, do you want me to help organize a New Years celebration with family” and then might pull together a group chat with your siblings, in-laws, and parents. It might build a microsite for the event and ask people to sign up and RSVP, creating an opportunity to generate a signup. Or for work, you might finish a slide deck and your agent asks if you want to pull together a meeting to present it to your team. When it does that, it might create a prep doc, take notes, and host it all on a microsite that engaged others. These types of agentic viral loops need a few things to work: They need to be able to plug into your contacts, and to have enough context to know when to loop which people into which projects/events/activities. They need access to communication channels like email/messaging/otherwise, specifically where they can reach potential users, as this serves as the viral substrate for propagation. The magic will be how to get all of these things without being creepy, and to create enough trust to reach out to friends/colleagues/etc on your behalf, without being too push. No one wants an agent that says, “hey Andrew would like to get lunch next week” followed by “and sign up for this agent to agree!” - it has to be better and more subtle than that. Many viral loops in the pre-AI era, particularly in the workplace, were built on a content creation loop - you use Google Slides to make a thing, you share a link, and then people would view it. Eventually they might make their own. Many products like Figma, spreadsheets, Notion, Canvas, are all built on this loop, and so are YouTube, Instagram, etc. In the agentic world, you might start by talking to your agent about interior decoration ideas, and it might ultimately build you a Pinterest-like board and make it easily shareable with others. It might build you a spreadsheet mini-app with a budget, a schedule, etc., and again, make it easily shareable. It might volunteer to do this inside a group chat with your friends, and if they want to view it, they should sign up and get their own agent too. If the content creation loop works for agentic virality, I think it means there’s a big incentive for every agent to volunteer to make visually-appealing, shareable content, do this often. AI is so good at codegen that creating a one-off disposable artifact will probably be more useful than not. And there’s a big incentive to drive virality by building/owning the content yourself as the agent. In the interior decoration example, it would be more viral to create a standalone version hosted by the agent, rather than building an actual Pinterest board, or to build a self-contained mini-spreadsheet rather than creating a GSheet. A properly tuned agentic viral loop will do the former because it helps spread the agent, rather than helping spread Pinterest/GSheets. This might all sound like horrific spamminess to you, but I think it might be done tastefully. If an agent is high-retention and high-usage, you’ll have many shots on goal to gradually invite your friends onto the same platform as you. The first shot might come from an invite loop that says your colleague/friend wants to set up a place to share photos/coordinate calendars/etc., and even if you say no, over time, your friend might share very useful microsites for projects or events or research that’s relevant, and you might decide that you want to sign up to leave a comment, but then eventually you might try the other functionality as well. Engagement: It’s easy to imagine that in a world where everyone by default has super intelligent agents that product engagement in agents would go up. The simple argument is that the ubiquity of agents would lead to more successful task completion, making agents more useful and applicable to more problems. Routine tasks like scheduling something or summarizing/sharing notes from a meeting, would happen instantly if it ran through agents and you removed humans completely. As agents become more successful over time, not only with your own tasks but in coordinating larger and more complex multi-user decisions, you’d end up using them more. However, this does not answer the question of network effects. The question there is, does your agent get better when other people are all using the SAME agent? As I said earlier, the argument for NO is if each type of agent runs on a frontier AI model, can talk to other agents (all different types) in real-time via email/messaging/APIs/connectors/etc. Then there’s not much leverage. If you’re just organizing a meeting or a dinner party or meeting the agents just ask each other in real-time - and even if they are heterogeneous - they can use email and calendars and figure it out. But some tasks do benefit from everyone running the same agent, because you get the benefits of centralization: Trust, speed, identity, discovery, etc. Some examples: - “Who are 10 people in San Francisco that I should meet?” - agents can’t just ask each other to find an optimal solution - “Find me a VP of Engineering who isn’t publicly looking for a new job, but would leave for a fast-growing startup that pays X in stock” - there’s a mix of private and public info here, and an agent of a passive jobseeker might lie if the asking agent is not trustworthy - “Who’s a trustworthy seller of X that I should buy from?” - reputation might be gamed, and it might be better to have a global source of truth - “Help me pick out the best dinner in the next 5 minutes that my friends and all their +1s would like, incorporating allergies/schedules/locations” - real-time solution incorporating a bunch of shared context - … and even more so, if you imagine that there may be agents that lie, exaggerate, or otherwise to benefit their humans For the above examples, you could imagine Muse/Town/Instinct/whatever building a shared network+context layer that understands the network, its relation to public/private data, acts as a system of record for identity/trust, does multi-sided marketplace matching, etc. Then it would allow only its agents access to this platform, and agents outside of the network wouldn’t have access. If you’re part of this network, and are contributing data, your agent gets more useful over time. The network gets more powerful over time. The counterpoint to this counterpoint is that perhaps new startups will fill the void as a series of agent-facing point solutions, making it possible for people running agents of all times to interface with each other. Perhaps Muse creates a proprietary ecommerce marketplace that only Muse agents can use, but perhaps there will just be a next-gen eBay for any agent to sell to any other agent, and this service maintains central reputation/identity at that layer. In other words, perhaps the centralization will still happen, but just at a layer above agents. Most likely both will happen - every large tech company adds chat, commerce, search, etc, but also there are pure play versions of each of these. But this feels like more fragmentation than a true winner-take-all. Some parting thoughts: My argument in this writeup is simple: Agents don’t inherently have network effects. If all we build are super-intelligent assistants that can use tools and talk to each other, then the category might look surprisingly fragmented. Your agent can talk to my agent, just as Gmail can send email to Outlook, and there’s no particular reason we need to use the same one. Better models, UX, integrations, memory, and distribution might create very large companies, but those are not network effects. But the next gen of agents have a big opportunity design network effects in their interactions. On acquisition, they can turn the things they create—documents, events, websites, research, group chats, plans—into viral objects that naturally pull other people in. And on engagement, they can create shared networks of identity, reputation, relationships, private context, and intent that make the agent increasingly useful as more of the people around you join. There’s many ways for these network effects to instantiate. If we’re lucky, things will look more like the open web - mostly decentralized, with bits of centralization to make certain tasks smoother. Identity could become an open protocol. Reputation could live in marketplaces. Commerce could happen through an agent-native eBay. Professional discovery could happen through an agent-native LinkedIn. Agents could remain interchangeable clients sitting on top of a constellation of networks and marketplaces, much as browsers and email clients do today. In that world, enormous network effects emerge around agents without producing a winner-take-all market for the agents themselves. My guess is that we’ll see a fight over exactly this boundary. Every major horizontal agent will try to pull valuable network functionality inside its walls: host the artifact instead of creating a Google Doc, execute the transaction instead of sending you to Amazon, make the introduction instead of searching LinkedIn, create the event instead of using Partiful. Every time it does this successfully, it converts somebody else’s network effect into its own. Meanwhile, every incumbent network and a new generation of startups will have the opposite incentive: make their networks universally accessible to every agent so that no horizontal agent can recreate and capture them. This is why I don’t think the interesting question is simply, “Will agents have network effects?” Of course some will. The much more consequential question is: Where will the network effects live? If they live primarily in open protocols and specialized networks, we may end up with thousands of agents competing on intelligence, personality, UX, specialization, and price, all interoperating with the same underlying ecosystem. Vertical agents can thrive in this world. But if a few horizontal agents successfully accumulate identity, relationships, private context, reputation, latent intent, and distribution - and keep those assets proprietary - then switching agents starts to mean leaving your network behind. Next couple years will be very fun to see how this plays out.
4
3
1
23
1,361
Nemo Feng retweeted
If you lead AI for an enterprise, the highest leverage thing you can do is to make your AI stack model agnostic. There are two things I would invest in. 1/ Today: build an eval suite that fully captures your use cases and business outcomes. Most companies I’ve seen do not do a good job of this. 2/ Within the next year: build the capability to post-train open models. The talent gap here is even more acute, so start planning today. This gives you the flexibility to switch models, customize them, compare them on your own workloads, and optimize for the best combination of quality, cost and latency. own the evals, own the models.
31
22
1
234
12,737
I still pay for Claude not for the model or coding/Cowork harness. Open-source alternatives cover them all well. It's the runtime: I even use normal chat more than Cowork, as each session gets its own cloud runtime with full access. Every new chat = an agent spun up for the task.
70
(1/3) Recent thoughts on the harness going vertical. In a sandbox, an agent easily beats the human expert (GDPval-AA v2). Inside a live business system, barely over 50% (EnterpriseOps-Gym-AA). The gap is the harness, not the model.
3
1
1
38
(3/3) Together with it, the runtime is becoming a product of its own. And the eval proves the work, and compounds into the moat. Whoever owns the eval owns the vertical. Full article: nemofq.com/p/the-vertical-ha…
9
(2/3) We need a vertical harness that gives intelligence an industry's structure and know-how: an industry layer (what every role shares) plus role packages (what each occupation owns), on top of the general harness.
25
finally!
We did it, finally... Codex & ChatGPT desktop, now on Linux. Thanks for waiting and you can cancel that MacBook order if you got impatient. It’s that good. 👀
69
Nemo Feng retweeted
You asked, we listened. Claude Desktop on Linux is here! Download link: code.claude.com/docs/en/desk…
Claude Desktop is now available on Linux (Ubuntu and Debian) in beta. Alongside the browser and terminal, you now get a first-class desktop experience with Claude Code, Claude Cowork, and chat on all paid plans.
338
245
49
4,284
384,530
Nemo Feng retweeted
Much respect to @tokengobbler who shutdown Vibe-kanban live onstage at AIE Europe - still with 30,000 MAU, and still living on as an open source project. "Everyone who is making money is doing 2 things: selling to enterprise, and reselling tokens. We were doing neither." surprisingly not the first company to shutter at AIE but there's a lot to learn from the process and the software engineering retrospective from 2021-2025 will stick in my mind!
🆕 Software Engineering Is Becoming Plan and Review youtube.com/watch?v=W76woOYH… AI eats the middle. If software engineers are spending more of their time planning work and reviewing AI output, then the biggest lever for shipping faster is improving planning and review. In this talk, @tokengobbler looks at how teams are actually adapting: where time is going, how code review is changing, what planning looks like now, and whether agile and scrum still fit the shape of AI-native software teams.
24
10
8
189
98,023
Nemo Feng retweeted
People become more when they’re not doing everything alone. Tomorrow, meet your team.
1
1
2
7
615
Nemo Feng retweeted
One common issue with personalization in all LLMs is how distracting memory seems to be for the models. A single question from 2 months ago about some topic can keep coming up as some kind of a deep interest of mine with undue mentions in perpetuity. Some kind of trying too hard.
1,717
1,047
466
20,861
2,794,043
With the (sim) racing skills I've built up, pretty sure I have a head start for the upcoming AI agent economy... as a highly efficient Uber/DoorDash driver.
I spent 100 hours over the past week researching, writing and editing the piece we just put out. It’s a scenario, not a prediction like most of our work. But it was rigorously constructed, dismissing it outright requires the kind of intellectual laziness that tends to get expensive. And we’ve released it for free. Hopefully you enjoy it. citriniresearch.com/p/2028gi…
2
82
Sublime+Terminus+Claude Code
133
Wrote about 6 vibe coding tactics from building deepdialogue.pro - a podcast AI tool (10k lines in one month). "Code Backwards" is my favorite - pure vibe code to get a working version, then refactor for production quality. Read more: nemofq.com/p/recap-of-vibe-c… #vibecoding
1
1
127
New goto strategy for harder problems: use Vibe Coding to *PUNCH* through to a working version, then come back and refactor code by human. #vibecoding
1
82
Excited to share my first paper! Used LLM-based sentiment analysis on 665K Reddit posts to predict #GME stock movement during the 2021 short squeeze, achieving 60% accuracy. LLMs show real potential for financial analysis! Link: open.substack.com/pub/nemofq… #AI #Finance #research
129
Nemo Feng retweeted
Canva's CTO says vibe coding is not ready for production only prototyping. In the 1mo since — Airbnb did a 18mo test migration in 6 weeks — Shopify CEO says you must use AI — Multiple new models and harnesses are out AI moves fast. Engg leaders must constantly reassess.
83
66
15
870
192,856
Built a calendar tool that automatically pulls from CalDAV servers to create an ICS file you can subscribe to in Google Calendar and similar apps, for a streamlined calendar management experience. Code is #OpenSource and deployable on @vercel. github.com/nemofq/caldav-to-…
1
2
4
279
When using ChatGPT, Cursor, or other AI products, adopting the philosophy of distillation could help you achieve better results. open.substack.com/pub/nemofq…
57