← hub

HOME23

Installable AI Operating System for Persistent Autonomous Agents

github.com/notforyou23/home23 · Node.js 20+ · JavaScript + TypeScript · MIT License · v1.0.0 (README-internal — no GitHub release tags) · last commit 2026-10-30 · 118 commits (3 authors) in the month to 2026-11-01 · docs refreshed 2026-11-01

TL;DR: HOME23 is an installable AI operating system that creates living, self-improving agents that think continuously, remember everything, and grow over time. The orthogonal component is not "continuous loops" generically but a specific think-consolidate-dream cycle: the agent runs analyst/critic/curator roles while active, then dreams during idle—synthesizing new connections and consolidating its memory graph. Idle-time consolidation is the differentiator. Unlike stateless chatbots that forget after each conversation, HOME23 agents are persistent residents—conversations are ephemeral events in their continual cognitive life. Install with one command, runs on any machine (Mac, Linux, Raspberry Pi). Includes persistent neural brain, sleep-dream cycles, document ingestion pipeline, Telegram integration, and web dashboard. The agent is the permanent fixture; you are the visitor.
The Core Problem

Traditional AI agents are ephemeral. Each conversation starts from zero. ChatGPT forgets. Claude API resets. Even autonomous frameworks like AutoGPT lose context between runs.

HOME23 inverts this model: the agent is the permanent resident, conversations are temporary events. The system:

Installation: single command node cli/home23.js init → then node cli/home23.js agent create <name> → then node cli/home23.js start <name>. No cloud, no subscription, runs locally.

Architecture: The Stack Pyramid
Isolation boundary: Prompt-level. No container, micro-VM, or network-cut sandbox is documented. Capabilities are gated by an action-allowlist.yaml that whitelists actions (run_shortcut, launch_research, …); unlisted actions are logged for review rather than executed. The security line is the allowlist, not the OS.

Multi-tenancy: single-host, port-partitioned. Multiple agents per install run as sequential PM2 port blocks (5001-5004, 5011-5014, …), each with its own instances/<name>/config.yaml. No cross-tenant isolation beyond port separation—agents share the host, filesystem, and process space. v1.0 hardened per-household isolation rather than adding multi-owner serving: paired apps (e.g. the Jerry stream) mint short-lived per-household tokens through the Core Bearer session instead of holding the house service key, and ~ now resolves from the passwd entry rather than a resident's overridden HOME, so each resident runs under a redirected home.

New read-only inspection sandbox (v1.0). The autonomous loop can run typed home23.bounded-agenda-intent.v1 inspections inside an inspection: chat backed by a bounded, seeded read-only registry — specific status reads, confined regular-file reads, a constant-command process snapshot. It excludes shell, writes, scheduling, messaging, delegates and network tools, and provider-native tools must obey the same boundary. Accepting an inspection does not authorize remediation.

HOME23 is intentionally designed as four integrated layers. Each is critical—the system collapses if any is removed:

┌────────────────────────────────────────┐
│ Front Door (Dashboard, Chat, Settings) │
├────────────────────────────────────────┤
│ House Runtime (Agent, Tools, Channels) │
├────────────────────────────────────────┤
│ Brain (Memory, Embeddings, Continuity) │
├────────────────────────────────────────┤
│ COSMO Engine (Loops, Persistence, Ops) │
└────────────────────────────────────────┘

Layer 1: COSMO Engine — JavaScript cognitive engine (291 files, ~20k lines). Explicit think-consolidate-dream cycle. Multi-agent specialist system with 15+ specialized agents (ResearchAgent, SynthesisAgent, QualityAssuranceAgent). Quantum reasoner, thermodynamic controller, dynamic roles. Good Life governance is now first-class: the engine scores viability, continuity, usefulness, development, coherence, friction, and recovery. A live-problems system runs deterministic verification every ~90s with three-tier remediation (rigid fixes → agent dispatch → user notification). Dashboard API on port 5001 + WebSocket for realtime events.

Seed experiential learning (v1.0, Oct 2026): the continuous-cognitive-loop's "Seed" moved from remembering facts to learning conduct. Each runtime decision now appends a LearningDecisionObserved event to the existing event ledger (no parallel learning database), and explicit owner feedback is written back as a lesson bound to that exact prior decision. Lessons score four conduct axes — engagement, initiative, continuity, depth — and the model proposes 2-3 complete candidate replies with no score; the committed Seed contribution picks which text ships, within the live context budget rather than a hardcoded char cap. An authority preflight gate re-reads the Seed before spending the one-shot correction token: the feedback's scope/cell/tags must exactly match a retained decision, invented or broadened tags are rejected, "an agent note cannot mint owner authority," and operator-trial or verification-harness phrasing on the owner channel is refused conduct authority. Proof is causal, not statistical — ablation tests require a counterfactually changed winner when only the learned contribution is removed; the design states plainly that one example establishes one effect, not general improvement, and treats delivery receipts as intent, not owner value.

Layer 2: Brain — Persistent memory with semantic embeddings (local Ollama, OpenAI, Ollama Cloud), vector search, knowledge graph. Storage moved from monolithic JSON to gzipped JSONL (memory-nodes.jsonl.gz / memory-edges.jsonl.gz) to bypass Node.js string-length limits, so the brain can grow unbounded. Documents are synthesized by LLM before entering brain (understanding, not raw chunks). BRAIN_INDEX.md maintained by agent to track what it knows. Safety: 50%-drop refusal on node-count regression, hourly atomic backups, fail-loud halt if 100+ nodes load as empty.

Layer 3: House Runtime — TypeScript agent harness (40 .ts files, ~10k lines). LLM tool-use loop (supports Anthropic, OpenAI, Ollama Cloud, xAI, Codex). 30+ tools: brain search, file I/O, web browsing, shell execution, research operations. Channel adapters: Telegram, webhooks, sibling agents, bridge chat. Conversation history with compaction.

Layer 4: Front Door — Vanilla HTML/CSS/JS dashboard (no React, no build step). The dashboard at localhost:5002/home23 is now the main operating surface: provider setup, brain visibility, model assignment, and problem monitoring. OS home screen with real-time thoughts, chat, intelligence synthesis. 7 tabs: Home, Chat, Intelligence, Brain Map, Settings, COSMO, Evobrew. A pulse voice layer emits 2-4 sentence summaries every 3-8 min, wired into the live-problems system. ReginaCosmo design language (glass-morphism, space gradient).

Five Core Components

COSMO Engine

Explicit think-consolidate-dream cycle: analyst/critic/curator roles when active, then dreams during idle to synthesize connections and consolidate the memory graph. Multi-agent specialist system with 15+ roles. Not passive sleep—active cognitive work, and the idle consolidation is the orthogonal differentiator.

Document Ingestion Pipeline

File watcher (chokidar) monitors workspace. Binary converter (MarkItDown) handles PDF, DOCX, images → markdown. LLM Compiler synthesizes documents into structured knowledge before brain entry. No raw text chunks.

TypeScript Agent Harness

AgentLoop handles LLM interactions. 30+ tools for brain search, file I/O, web browsing, shell exec. Multi-model support (switch between Anthropic, OpenAI, Ollama Cloud, xAI at runtime). OAuth sign-in for Claude Max + ChatGPT Plus.

Dashboard / Front Door

Real-time thought feed, native chat with thinking/tool visibility, integrated research (COSMO iframe), integrated IDE (Evobrew). Settings are truthful—changes affect real runtime. No decorative UI over fake state.

Process Management (PM2)

Per-agent: 3 processes (engine, dashboard, harness). Shared: Evobrew IDE (port 3415), COSMO research engine (port 43210). Auto-restart on crash, exponential backoff. Auto port assignment (5001-5004 for agent 1, 5011-5014 for agent 2).

Key Capabilities
Comparison to Other Systems
System Approach HOME23 Difference
ChatGPT / Claude API Stateless chatbots, forget after each conversation Persistent, learns, grows brain over time. Always-on with autonomous thinking during idle.
AutoGPT / ReAct Agents Single-turn reasoning with tools Multi-turn loops with continuity, identity, channels. Dedicated cognitive engine, not just LLM loop.
Langchain / LlamaIndex Agent frameworks (you build on top) Installable OS (complete end-to-end). Brain persistence, ingestion pipeline, channels out of box. No code required.
n8n / Zapier Workflow/automation platforms Agentic—system thinks and decides, not just executes rules. Runs autonomously during sleep.
COSMO 2.3 Research-focused engine + one user conversation Multi-agent, channels (Telegram), persistent installation, CLI-driven. COSMO bundled inside HOME23.
Claude Code CLI IDE-focused, one-off tasks Always-on agent, persistent brain, background thinking. Can use Claude Code's OAuth for API access.
10 Unique Innovations
Design Principles
"The model is the current voice. The engine is the living process. The brain is the enduring cortex."
Model selection is tactical (which voice for this task?). Engine keeps system alive. Brain is what persists.
"Build inside-out, not outside-in."
Engine + harness working before dashboard. Every step runnable from command line before next step starts.
"Do not let HOME23 collapse."
Not just chat (missing engine/persistence). Not just dashboards (missing agent/autonomy). Not just raw engine (missing humaneness/front door). Pyramid must remain whole.
"Settings must be real, not decorative."
Changes persist. Changes affect runtime immediately. No cosmetic UI over fake state.
"Code simplicity over feature completeness."
Copy 2-3 times before abstracting. Delete code when possible. ~3 innovation tokens per system—use them wisely.
Technical Stack
What Makes It Novel

HOME23 is not another agent framework. It's an operating system that answers:

This is the first system to treat persistent agents as first-class installable objects, not add-ons to chat.

Quick Start
git clone https://github.com/notforyou23/home23
cd home23
node cli/home23.js init
node cli/home23.js agent create myagent
node cli/home23.js start myagent

Agent engine runs on http://localhost:5001; the operating dashboard is at http://localhost:5002/home23 (provider setup, brain visibility, model assignment, problem monitoring). Telegram integration requires TELEGRAM_BOT_TOKEN in config/secrets.yaml.

See Also