Inside the AI: Wie clawbot funktioniert

🌐 The Gateway: Central Command

The Gateway is the heart of clawbot—a persistent Node.js process that never sleeps. Why a dedicated service instead of running AI directly in each channel? Three critical reasons:

• Unified State : Single source of truth for conversation history across all channels
• Resource Efficiency : One connection to AI APIs instead of 15+ separate connections
• Fault Isolation : If WhatsApp crashes, Telegram keeps working—channels are replaceable plugins

The Gateway communicates via WebSockets, not HTTP. Why? HTTP requires the client to constantly ask "any updates?" (polling). WebSockets maintain a persistent two-way connection—the Gateway can push messages to channels the instant they're ready, enabling real-time streaming responses.

💬 Channels: The Sensory Interface

Channels are independent processes that translate between messaging platform protocols and the Gateway's unified message format. Think of them as protocol adapters —WhatsApp speaks Baileys, Telegram speaks Bot API, but both present messages to the Gateway in identical JSON structure.

Diese Abstraktion ist leistungsstark: Das Hinzufügen einer neuen Messaging-Plattform erfordert das Schreiben eines Kanal-Plugins, nicht die Änderung des gesamten Systems. Jeder Kanal ist sandboxed – wenn er abstürzt, versucht das Gateway automatisch eine Wiederverbindung, ohne andere Kanäle zu beeinträchtigen.

🧠 AI Model Router: The Intelligence Backbone

clawbot doesn't lock you into a single AI provider. The model router implements dynamic provider selection : choose Claude for complex reasoning, GPT-4 for creative tasks, or local Ollama for privacy-critical operations—all within the same conversation.

How does this work technically? Each AI provider has a standardized interface (following the OpenAI Completion API pattern). The router maintains connection pools to all configured providers, routes requests based on configured preferences, and handles automatic failover if a provider is unavailable.

💾 Persistent Memory: Conversation State Management

Unlike stateless AI APIs that forget everything between requests, clawbot maintains durable conversation history stored in Markdown files at ~/.clawbot/conversations/ . Each conversation is a complete log of messages, tool executions, and AI responses.

Why Markdown instead of a database? Three reasons:

• Human-Readable : You can grep, search, and version control your AI conversations
• Portable : Move your entire conversation history by copying a folder
• AI-Friendly : AI models can natively understand Markdown formatting for context retrieval

Das Gateway verwaltet automatisch Kontextfenster – wenn eine Konversation das Token-Limit des Modells überschreitet, fasst es ältere Nachrichten intelligent zusammen und bewahrt dabei kritischen Kontext. Dies ermöglicht Konversationen, die sich über Wochen erstrecken, ohne Qualitätsverlust.

⚙️ Execution Engine: Safe System Control

This is where clawbot differentiates from chatbots: genuine task execution . When the AI decides a shell command is needed, the execution engine handles it safely through multiple protection layers:

• Sandboxing : Commands run in restricted environments with limited file system access
• Permission Gates : User-configurable allowlists/denylists for command patterns
• Confirmation Prompts : Destructive operations require explicit user approval
• Audit Logging : Every executed command is logged with timestamp, user, and result
• Timeout Protection : Commands automatically terminate after configurable duration

🔌 Skills System: Extensible Capabilities

Skills are clawbot's plugin system—folders containing SKILL.md files that teach the AI new capabilities. How does a Markdown file extend functionality? The AI reads the skill definition and learns:

• What the skill does and when to use it
• What parameters it accepts
• Example commands that trigger it
• Expected behavior and edge cases

Skills können Shell-Skripte, Node.js-Module oder API-Integrationscode enthalten. Die KI ruft diese Tools über strukturierte Funktionsaufrufe auf, empfängt Ergebnisse und integriert sie in Antworten. So kann clawbot Smart Homes steuern, Cloud-Infrastrukturen verwalten oder sich in proprietäre interne Systeme integrieren – jeder kann einen Skill schreiben.