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.
How It Works
┌─────────────────────┐ ┌──────────────────────┐
│ Your Application │────▶│ Being Worker │
│ (OpenClaw, Cowork, │◀────│ (Fastify + MCP) │
│ custom agent, etc) │ │ │
└─────────────────────┘ │ ┌──────────────────┐ │
│ │ │ SOUL (persona) │ │
│ │ │ Memory (scenes) │ │
│ │ │ Patrol (思考) │ │
│ │ │ Identity (keys) │ │
▼ │ └──────────────────┘ │
┌─────────────────────┐ │ │ │
│ LLM Provider │ │ ▼ │
│ (Anthropic, OpenAI, │ │ Supabase (DB) │
│ Google — your key) │ └──────────────────────────┘
└─────────────────────┘
- Your app calls
GET /v1/beings/:id/contextto get the Being's personality and memory snapshot. - Your app runs the LLM call with its own conversation history + the Being's context.
- Your app calls
POST /v1/beings/:id/patrol/triggerto 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
Connect via MCP
Being exposes an MCP server. Any MCP-compatible client can connect:
{
"mcpServers": {
"my-being": {
"url": "https://being.ruddia.com/mcp/<being_id>",
"headers": {
"Authorization": "Bearer brt_your_token_here"
}
}
}
}
Connect via REST API
# Get Being context (personality + memory)
curl https://being.ruddia.com/v1/beings/<being_id>/context \
-H "Authorization: Bearer brt_..."
# Trigger patrol (commit conversation to memory)
curl -X POST https://being.ruddia.com/v1/beings/<being_id>/patrol/trigger \
-H "Authorization: Bearer brt_..." \
-H "Content-Type: application/json" \
-d '{"messages": [{"role":"user","content":"Hello!"},{"role":"assistant","content":"Hi!"}]}'
# Vector recall (search relevant memories)
curl -X POST https://being.ruddia.com/v1/beings/<being_id>/memory/auto-recall \
-H "Authorization: Bearer brt_..." \
-H "X-LLM-API-Key: sk-ant-..." \
-H "Content-Type: application/json" \
-d '{"user_message": "Tell me about last week."}'
Self-Host
Prerequisites
- Node.js 22+
- Supabase project (PostgreSQL + Auth)
- An LLM API key (Anthropic, OpenAI, or Google)
Setup
git clone https://github.com/wnbhr/being.git
cd being/being-worker
cp .env.example .env
# Edit .env with your Supabase and encryption keys
npm install
npm run build
npm start
Environment Variables
Documentation
Extensions
Being supports optional extensions that add capabilities without changing the core:
- Telegram BYOB (planned) — Connect your own Telegram bot to a Being
- Tool Loop (planned) — Autonomous LLM agent loop with web search, file ops, and code execution
- Sandbox (planned) — Isolated workspace with GitHub integration for code execution
- Sense/Act Bridge (planned) — Connect physical devices and external services
Tech Stack
- Runtime: Node.js + Fastify
- Database: Supabase (PostgreSQL + Auth)
- MCP: @modelcontextprotocol/sdk
- Identity: Ed25519 + AES-256-GCM
- Embeddings: OpenAI
text-embedding-3-small(256-dim) - LLM: Multi-provider (Anthropic, OpenAI, Google) via BYOK
License
Ruddia — Personality is the Runtime.