Homelab Integration Architecture

This document maps the full integration architecture of the homelab project, detailing how components like Codex, Clawdbot, Pulse, and Noosphere connect to form an autonomous development and communication ecosystem. The homelab is structured into three primary layers: 1. **Orchestration & Dispatch (Codex)**: Manages tasks, queues, and agent routing. 2. **Communication & Gateway (Clawdbot)**: Bridges human interfaces (Discord, Telegram) with system actions. 3. **Execution & Intelligence (Pulse, Claude Code, Noosphere)**: Performs the actual development work and maintains project context. ### 1. Codex (Orchestrator) - **Role**: Global task queue and agent dispatcher. - **Tech**: Node.js, Express, Supabase. - **Integration**: - Receives GitHub webhooks (pushes, PRs). - Manages a task queue in Supabase. - Dispatches tasks to agents (`dual-max`, `pulse`, `clawdbot-session`) via the `Dispatcher`. - Enriches prompts with project context from the Orbit intelligence layer. ### 2. Clawdbot (Gateway) - **Role**: The central communication hub and command router. - **Tech**: Node.js, CLI-first architecture. - **Integration**: - Bridges multiple chat platforms (Discord, Telegram, iMessage). - Provides a CLI (`clawdbot message send`) used by other services for notifications. - Manages "Skills" (specialized agents) and spawns autonomous sessions. - Maintains a local message log and SQLite memory database (`kimi_memory.db`). ### 3. Pulse (Autonomous Development) - **Role**: Autonomous agent focused on git-based development tasks. - **Tech**: Node.js, MCP (Model Context Protocol). - **Integration**: - Exposed as an MCP server for Claude Desktop. - Handles the full dev lifecycle: branching, coding, committing, and creating PRs. - Triggered by Codex for automated task fulfillment.