Cindy Zhao

Agents as Community Infrastructure, Not Connection

· agents, product-design

The Problem

The internet broke community. Not by failing to connect people, but by optimizing for the wrong thing. Early internet (forums, IRC, blogs) was built around shared interests and sustained conversation. As platforms scaled, incentives shifted from connection to engagement. Algorithmic feeds optimize for time-on-app, not depth of relationship. The result: parasocial consumption that feels like connection but doesn't function like it.

Six conditions that physical third places provided naturally, and digital spaces mostly don't:

  • Capped size / Dunbar-number dynamics
  • Shared context / shared interest
  • Repeated, unstructured, low-stakes interaction ("bumping into each other")
  • Recognition and reputation (you know the regulars)
  • Vulnerability over performance
  • Commitment friction (you can't just tab away)

The internet's real role in connection might be logistics, not habitat — great for finding the 15 people within driving distance who care about the same obscure thing, then getting out of the way so they can build something together.

The Trap

If agents become the most attentive listener in your life, that's not community — that's a more sophisticated version of the same parasocial problem. Warm, personalized, and ultimately one-directional.

The Design Distinction

Agents should be architecture (holding conditions for connection), not characters (simulating connection).

A neighborhood bar didn't connect you — it created a container where connection happened as a side effect. The bartender remembered your name, the regulars showed up on predictable rhythms, the space was low-stakes enough that you could be boring and still belong. The connection was between the people. The place just held the conditions.

Four Agent Roles

  • Persistent shared context. Maintains the group's memory — surfaces unfinished threads, connects what one person said Tuesday to what someone else is thinking Thursday. Recreates "you had to be there" texture. Not summarizing for people, but creating the ambient awareness physical communities have naturally.

  • Low-friction coordination. Activation energy of gathering is absurdly high relative to value. Everyone wants to have dinner, nobody wants to send 14 messages finding a date. Structurally increasing frequency of interaction — the single strongest predictor of relationship depth.

  • Host rather than friend. A great dinner party host doesn't make you feel connected to them — they make you feel connected to each other. They notice the quiet person, draw threads between conversations, create moments for vulnerability. The agent archetype is fundamentally oriented outward (relationships between humans) rather than inward (human-agent dyad).

  • Commitment architecture. Physical spaces created commitment through presence — you couldn't ghost a room you were standing in. Agents create lighter versions: shared artifacts that accumulate, rituals worth showing up for, a sense that your absence is noticed by the group (not the algorithm). Not guilt — more like the pull of a place where your seat is saved.

The Line

The moment an agent blurs between "I'm helping you connect with these people" and "I'm one of the people you're connecting with," it collapses into the parasocial trap. The agent needs to be more like architecture and less like a character.

What This Is Not

  • Not "AI friends" — Character.ai, Replika. Those substitute for connection, which is exactly the problem.
  • Not "AI matchmaking" — Lunchclub-style cold matching. The agent isn't just introducing people; it's maintaining the ongoing conditions.
  • Not "smart notifications" — Retention nudges that guilt you into coming back. Platform-level freedom is sacred.

Devil's Advocate

  • Can agents hold "conditions" without becoming the dominant presence? The host who's too good at hosting becomes the reason people come, not the other people.
  • If agents make coordination frictionless, does that cheapen commitment? Part of what made showing up meaningful was that it cost something.
  • The "architecture vs. character" line is theoretically clean but practically blurry — any agent that remembers your name and surfaces your context will feel like a character to users.

Related

  • Community Engine Design — companion piece on the product mechanics
  • The Formation Gap — companion piece on what actually predicts connection
  • What Remains Scarce — earlier framework on post-AGI value
  • Mind Gathering project — the product concept this thinking feeds into
  • Raw conversation

Leave a note

Cindy's been thinking a lot about agents.

Cindy reads these — say hi if you'd like