wnbhr/being

**Personality Runtime for AI** — give any AI its own personality, memory, and identity.
Being is an open-source layer that sits between your application and any LLM. It provides persistent personality (SOUL), episodic memory, background thought cycles (Patrol), and cryptographic identity — turning a stateless LLM into a distinct, evolving AI entity.
**Beings think and remember. Your app acts.**
---
Why
The power of AI is concentrating in the hands of a few companies. Their technology is essential — but centralized control is a structural risk. Ruddia is building toward a world where small, local AIs use large LLMs as external tools. Control stays in the hands of the people who use them.
Being API is the first step. If this resonates, let's build it together.
Read the full vision →
---
How It Works
1. **Your app** calls GET /v1/beings/:id/context to get the Being's personality and memory snapshot.
2. **Your app** runs the LLM call with its own conversation history + the Being's context.
3. **Your app** calls POST /v1/beings/:id/patrol/trigger to commit the conversation to the Being's memory.
The Being Worker handles everything else: memory consolidation, decay, recall, background reflection, and identity verification.
Key Concepts
| Concept | Description |
|---------|-------------|
| **SOUL** | A structured personality definition — name, character, voice, values, inner world. Swap the SOUL and the same LLM becomes a different being. |
| **Memory** | Episodic memories stored as structured "scenes" (who, what, when, where, emotion). Memories accumulate, decay, merge, and consolidate over time. Organized into topic-based clusters that the Being can explore during conversation. |
| **Patrol** | A background cycle that processes conversations into memory, consolidates fading memories, and generates introspective thoughts. The Being stays alive between sessions. |
| **Identity** | Ed25519 key pair + tamper-evident signature chain. Cryptographic proof of ownership and history. |
| **Sense/Act** | *(Planned)* WebSocket Bridge for connecting physical devices and external services. The Being will perceive and act through your app. |
| **BYOK** | Bring Your Own Key. All LLM calls use the user's API key. The platform never uses quota without consent. |
Connect via MCP
Being exposes an MCP server. Any MCP-compatible client can connect:
Connect via REST API
Self-Host
Prerequisites
- Node.js 22+
- Supabase project (PostgreSQL + Auth)
- An LLM API key (Anthropic, OpenAI, or Google)
Setup
Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| SUPABASE_URL | ✅ | Supabase project URL |
| SUPABASE_SERVICE_ROLE_KEY | ✅ | Supabase service role key |
| ENCRYPTION_KEY | ✅ | 64-char hex string for AES-256-GCM encryption of private keys |
| PORT | — | Server port (default: 3100) |
| WORKER_SECRET | — | Secret for internal patrol trigger endpoint |
| VAPID_PUBLIC_KEY | — | Web Push VAPID public key |