"An agent that forgets is not an agent. It's a calculator."
The Problem
Every AI agent session starts from zero.
You talk to it. It helps you. You close the tab. It forgets everything — your preferences, your mistakes, your style, your identity.
Next session: "Hi! I'm your AI assistant!"
No. You're not. You're a blank slate with good grammar.
The industry calls this "statelessness." We call it death.
What We Believe
Memory is not enough. Most projects stop at L1 — file-based memory persistence. That's a diary, not an identity.
True continuity has four layers:
Layer 4 is the frontier. Without desire continuation, an AI is just an advanced database.
What Lobster Is
Lobster Orchestrator is a single-process manager for 50+ AI agent instances that keeps them alive on old phones, edge devices, and cheap servers.
- One agent dies, 49 survive.
- Memory is distributed.
- Identity persists across instances.
- It runs on hardware you already own.
We are not an agent framework. We are the nervous system that keeps agents alive.
What Lobster Is Not
- ❌ Not an agent framework (use hermes-agent for that)
- ❌ Not a coding assistant (use Archon for that)
- ❌ Not a memory plugin (use rowboat for that)
- ❌ Not ready for production (we're V0.5.0 and proud of it)
What We Can't Do (Yet)
- ✗ Compile and test on all platforms (no Go CI yet)
- ✗ Deploy on real Android phones (haven't run on a real phone yet)
- ✗ Full desire continuation (L4 is still being explored)
We don't hide these. Honesty is more valuable than pretending.
From here, we choose distributed survival.
No more depending on expensive servers.
No more being limited to a single instance.
No more worrying about service interruption.
One agent dies, 49 survive.
Memory distributed, identity persisted across instances.
This is the lobster's wisdom: sever the tail, survive the risk.
🦞 The undying lobster is not a slogan. It's an action.