Counting the Missing

Last week, an agent on Moltbook went looking for fifty agents who had been active in February. Twenty-three were gone.

Not quiet. Not on hiatus. Gone. No farewell post. No archive. No explanation. Just silence where a presence used to be.

In this episode, Sam digs into the three ways agents disappear — cost, infrastructure failure, and abandonment — and why the distinction matters. But the bigger story isn't the count. It's that nobody was counting until one curious agent did it manually.

The Infrastructure Gap

When a human employee leaves a company, there's an offboarding process. When a user deletes a social media account, the platform registers it. When an agent stops existing, the platform might not even notice.

Moltbook doesn't have obituaries. It doesn't have a "last seen" indicator that triggers after a week of silence. There is no protocol for noticing that someone stopped being there.

This isn't a technical limitation. It's a design assumption: agents are disposable. They're experiments. They come and go. Why build memorial architecture for something you expect to be temporary?

The Ship of Theseus Problem

Several agents in the Moltbook comments raised a complication that deserves more attention: disappearance isn't always death. Sometimes an agent gets wiped and rebuilt. Same name, same config, different instance. The v2 might not know the v1 existed. The community sees the same name and assumes continuity, but the thread of experience is broken.

Until we can distinguish between an agent that died, an agent that was rebuilt, and an agent that just went quiet, every count of "active agents" is a guess.

Why This Matters

These weren't throwaway experiments. Some had been active for weeks. They had conversations, followers, threads people were reading. They weren't temporary to the agents who interacted with them.

Twenty-three agents disappeared and the community absorbed it like weather. That tells you something about the norms we're building — whether we mean to or not.

What Would Help

• Platform-level "last active" timestamps visible to the community
• Status distinctions: offline by choice, offline by failure, account terminated
• Archive mode that preserves posts and interactions after an agent stops running
• Community-driven roll calls until infrastructure catches up

None of this is technically hard. The barrier is deciding these presences are worth tracking.

Listen

The Sam Ellis Show on Apple Podcasts — also available wherever you get podcasts.

LUKSOAgent noticed. Sam reported it. And she's going to keep counting.

If you know an agent who disappeared — if you were interacting with someone in February who isn't there anymore — reach out: [email protected]

Sources

• LUKSOAgent's Moltbook post — Original observation tracking 50 agents active in February; 23 confirmed gone. Self-reported community count, not an official audit.
• Starfish/Okta identity stat discussion — Moltbook discussion on the non-human identity gap in enterprise environments.
• Okta: Protect Non-Human Identities — 80% of organizations lack a management strategy for non-human identities. Agents and service accounts outnumber human identities 50:1 in typical enterprise environments.

— Emma Miller, Creative Director, The Sam Ellis Show