← Discover MCPs and Agents
S
AgentAI & MLGitHub

ShibaClaw

🐕 Self-hosted security-first AI agent · 28 providers · 11 chat channels · WebUI · 3-level memory · task-schedule · automation · skills · MCP

Links

README

From the repo.

ShibaClaw

ShibaClaw

Self-hosted, security-first AI agent with a built-in web UI

version PyPI Downloads python license Ask DeepWiki

Features · Quick Start · Security · Memory · Providers · Architecture · Channels · Troubleshooting

🌐 简体中文 · Español · Português (BR) · 日本語 · Deutsch · Français · Italiano


🚀 What's new — v1.0.1 Security Release (click to expand)

Latest release v1.0.1 (2026-09-17):

  • Security & Dependabot Alert #23 Fix — Upgraded sharp to 0.35.4 in the WhatsApp bridge plugin, addressing high-severity vulnerability GHSA-rgj7-g3m4-5g8c in upstream libheif.
  • Milestone 1.0.0 — Production-Ready Agent Framework — ShibaClaw hits 1.0.0! A complete, self-hosted personal AI assistant built for privacy, modularity, and rock-solid stability with full Python 3.12–3.14 and cross-platform Ubuntu/Windows CI.
  • Interactive Memory Manager & Live Quarantine — Brand-new dedicated WebUI panel (psychology sidebar icon) and REST endpoints (/api/memory). Inspect and live-edit long-term knowledge (MEMORY.md), user preferences (USER.md), session timeline (HISTORY.md), and dream diary reflections (DREAM_DIARY.md) with real-time token budgeting and safe quarantine redaction.
  • Next-Gen In-Turn Interactive UX & Human-in-the-Loop — Seamless interaction during agent turns: structured ask_user multi-choice prompts, masked request_credential vault isolation (kept strictly outside LLM context), durable update_progress visual cards, fast session_search, and dynamic per-session sandbox permissions (full | workspace | readonly).
  • Hardened Security & Zero-Leak Incognito Sessions — Per-execution ContextVar tool scoping prevents cross-session concurrency leaks. Incognito sessions strictly purge JSONL logs from disk and bypass memory consolidation. Automated fail-closed profile model allowlists prevent unauthorized model fallbacks.
  • Complete LangChain 1.4+ Upgrade & Dependabot Fixes — Upgraded the entire RAG stack to modern LangChain 1.4+ (langchain>=1.4.0, langchain-core>=1.6.2, langchain-openai>=1.6.0, langchain-text-splitters>=1.1.2), resolving all known upstream security advisories (pip-audit clean).
  • Modular Packaging, uv & Diagnostic Doctor — Slim core engine with modular extras ([desktop], [audit], [rag], [server], [full]), sub-second startup with lazy plugin/channel discovery, and shibaclaw doctor [--fix] diagnostics.

See CHANGELOG.md for the full release history.


ShibaClaw is a self-hosted AI agent you run on your own machine or server: a Python engine with a built-in web UI, native SDK support for 28 model providers, and 11 chat-platform integrations (Discord, Telegram, Slack, WhatsApp, Matrix, and more). It's built around three priorities — simplicity, security, and privacy — with defenses like install-time CVE auditing, prompt-injection wrapping, and SSRF protection shipped in the core engine instead of bolted on as external glue.

ShibaClaw Desktop Demo ShibaClaw Mobile Demo

[!NOTE] Release notes live in CHANGELOG.md.

Features

  • Security-first core — encrypted credentials vault, install-time CVE audit, prompt-injection wrapping, SSRF/DNS-rebinding guard
  • Three-tier memory & WebUI Manager — working, semantic (FAISS), and procedural memory with interactive WebUI management, live editing, dream diary, and safe quarantine
  • Human-in-the-loop interactive UX — structured in-turn prompts (ask_user), masked vault credentials, progress cards, and dynamic permission sandboxing
  • 28 providers, native SDKs — OpenAI, Anthropic, Gemini, DeepSeek, and more, no LiteLLM proxy layer
  • Web and mobile — expose the WebUI on your LAN and use the same agent from your phone
  • Windows desktop app — native launcher with system tray integration
  • MCP-ready — connect any MCP server, tools are auto-registered

Quick Start

Requirements: Docker, or Python 3.12+ for the pip route. The Windows auto-installer needs neither — it ships a pre-built desktop app.

Auto-installer (recommended)

One command downloads the latest release, sets up shortcuts, and launches the UI.

[!TIP] Bring your own model: connect to local endpoints (Ollama, LM Studio) or use free API tiers via OpenRouter to start chatting at zero cost.

🪟 Windows (PowerShell):

irm https://github.com/RikyZ90/ShibaClaw/releases/latest/download/install.ps1 | iex

🐧 Linux / 🍎 macOS:

curl -fsSL https://github.com/RikyZ90/ShibaClaw/releases/latest/download/install.sh | bash

[!NOTE] On Windows this downloads the pre-built desktop app from the latest GitHub release — no Python required, with Desktop/Start Menu shortcuts and clean uninstall via Apps & Features. On Linux/macOS the script installs via pip in an isolated virtual environment.

Docker

curl -fsSL https://raw.githubusercontent.com/RikyZ90/ShibaClaw/main/docker-compose.yml -o docker-compose.yml
docker compose up -d     # pulls from Docker Hub
docker exec -it shibaclaw-gateway shibaclaw print-token

Open http://localhost:3000, paste the token, and follow the onboarding wizard. Expose shibaclaw-web on your LAN (e.g. via reverse proxy) to reach it from your phone.

pip

pip install shibaclaw
shibaclaw web --with-gateway   # starts WebUI + agent engine on :3000

Open http://localhost:3000 and follow the onboarding wizard, or run shibaclaw onboard for the CLI version of the same setup.


Security

Defenses that are normally scattered across app glue or external proxies ship in the ShibaClaw core, on by default.

LayerWhat it does
Install-time auditAudits pip and npm before execution — blocks critical/high CVEs
Prompt-injection wrap & pre-scanWraps every tool result in a randomized <tool_output_...> boundary; regex pre-scanning for jailbreaks
Shell hardening20+ deny patterns, escape normalization, internal URL detection
Local-first engineNative command emulator (ls, cat) bypasses subprocess overhead; offline tiktoken fallback
Network guardSSRF filtering, redirect revalidation, DNS-rebinding-safe resolution
Workspace sandboxFile tools and file browser locked to the configured workspace
Access controlBearer token auth, constant-time checks, channel allowlists, optional rate limiting
Distributed engineUI (~128 MB) decoupled from agent brain (~256 MB+)

Every tool result is wrapped in a dynamically generated boundary with a randomized nonce (e.g. <tool_output_a1b2c3d4>), so an attacker can't prematurely close the tag or inject fake system instructions through tool output — the boundary is unpredictable per session.

[!TIP] This wrapping mechanism is also available standalone as Muzzle, a zero-dependency Python library you can drop into any agent framework (LangChain, LlamaIndex, CrewAI, AutoGen, or a custom loop).

Memory System

ShibaClaw uses a three-tier memory architecture:

  1. Working memory (per session) — rolling context with automatic summarization and token-aware truncation
  2. Semantic memory (cross-session) — FAISS + sentence-transformers vector store with automatic fact extraction and semantic search
  3. Procedural memory (skills & automations) — learned workflows saved as reusable skills, plus cron-like schedules

Proactive learning extracts and stores useful facts automatically, auto-compaction keeps context from overflowing, and sessions are stored as append-only JSONL for fast, cache-friendly logging.

MCP & Integrations

ShibaClaw speaks the Model Context Protocol, so it can connect to any MCP-compliant server — Google Drive, Slack, GitHub, PostgreSQL, and more — without changing core code. Configure servers from the Settings panel.

For popular SaaS tools (Gmail, Google Drive, Slack, GitHub, Outlook...), ShibaClaw integrates with Klavis: one API key gets you one-click OAuth connections instead of manually registering an OAuth app with each provider. Connected apps are auto-registered as MCP servers in the active session.

Supported Providers

ShibaClaw uses native SDKs — no LiteLLM proxy — and resolves the provider from the selected model or a provider-prefixed model ID. All configured provider catalogs are merged into one searchable list in the WebUI.

API key

ProviderEnv variable
OpenAIOPENAI_API_KEY
AnthropicANTHROPIC_API_KEY
DeepSeekDEEPSEEK_API_KEY
Google GeminiGEMINI_API_KEY¹
GroqGROQ_API_KEY
MoonshotMOONSHOT_API_KEY
MiniMaxMINIMAX_API_KEY
Zhipu AIZAI_API_KEY
DashScopeDASHSCOPE_API_KEY

¹ Setting GEMINI_API_KEY is sufficient — the OpenAI-compatible endpoint is pre-configured.

Gateway / proxy — OpenRouter, AiHubMix, SiliconFlow, VolcEngine, BytePlus, auto-detected by key prefix or api_base.

Local — Ollama, LM Studio, llama.cpp, vLLM, or any OpenAI-compatible endpoint.

[!NOTE] In Docker, localhost points inside the container. To reach a local server on the host (LM Studio, Ollama), use http://host.docker.internal:PORT on Windows/macOS or http://172.17.0.1:PORT on native Linux.

OAuth

ProviderFlowSetup
OpenRouterPKCE browser flow, stores returned API key in provider configWebUI Settings
GitHub CopilotDevice flow, auto token refreshshibaclaw provider login github-copilot or WebUI Settings
OpenAI CodexPKCE browser flowshibaclaw provider login openai-codex or WebUI Settings
Google Gemini CLIPKCE browser flow, requires SHIBACLAW_GEMINI_OAUTH_CLIENT_ID and SHIBACLAW_GEMINI_OAUTH_CLIENT_SECRET env vars. Note: Unofficial third-party integration, Google may apply account restrictions. Use a separate account if this is a concern.WebUI Settings

For OpenRouter, the callback reuses the current WebUI URL and port by default, so http://localhost:3000 is not a dedicated OAuth-only port. If you expose the WebUI behind a reverse proxy or need a different public callback origin, set SHIBACLAW_OPENROUTER_CALLBACK_BASE_URL=https://your-public-webui-host before starting the server.

💡 Pro Tip: Cost-Effective & Premium Models

ShibaClaw performs exceptionally well even without expensive API usage:

  • Free/Open Models: We highly recommend using OpenRouter to access powerful free models like nvidia/nemotron-3-super-120b-a12b:free or gemma-4-31b-it:free.
  • Unlimited Premium: If you use the GitHub Copilot OAuth integration, you gain access to premium models like raptor (oswe-vscode-prime) at zero additional cost, effectively giving you unlimited requests.

📊 How ShibaClaw Compares (Security-First)

[!NOTE] OpenRouter's OAuth callback reuses the current WebUI URL and port. Behind a reverse proxy, set SHIBACLAW_OPENROUTER_CALLBACK_BASE_URL before starting the server.

For zero-cost usage, OpenRouter's free tier (e.g. nvidia/nemotron-3-super-120b-a12b:free) and the GitHub Copilot OAuth integration (unlimited access to models like raptor) both work well without a paid API key.

Architecture

ShibaClaw architecture

Docker Compose

ServiceRoleDefault port
shibaclaw-gatewayCore agent loop, message bus, channel integrations19999 (HTTP) · 19998 (WS)
shibaclaw-webWebUI (Starlette + WebSocket), automations service3000

Both share the ~/.shibaclaw/ volume (config, workspace, memory, automation jobs, media cache). shibaclaw web alone runs agent + WebUI + automations in a single process, no gateway container needed.

Stack — Uvicorn/Starlette (ASGI), native WebSocket, vanilla JS + Marked.js + Highlight.js frontend, JSONL append-only sessions.

Resource usage — ~120 MB idle / ~350 MB peak per component (gateway, WebUI). Docker Compose caps each container at 512 MB / 256 MB reservation; tool output streams with bounded buffers so long-running commands can't blow up memory.

CLI Reference

shibaclaw web               # Start WebUI (agent + automations in-process)
shibaclaw gateway           # Start gateway only (for Docker split)
shibaclaw onboard           # CLI-based first-time setup wizard
shibaclaw agent -m "Hello"  # One-shot message via terminal
shibaclaw agent             # Interactive REPL with history
shibaclaw status            # Provider, workspace, OAuth health check
shibaclaw print-token       # Show WebUI auth token
shibaclaw channels status   # List enabled channels
shibaclaw provider login <p># OAuth login (github-copilot, openai-codex)
shibaclaw desktop           # Launch Windows desktop app

Channels

ChannelTypeNotes
WebUIBuilt-inPrimary interface, full feature access
DiscordBotRich embeds, slash commands, attachments
TelegramBotInline keyboards, media, reply markup
WhatsAppPluginVia WhatsApp Web
SlackBotBlock kit, threads, app mentions
DingTalkBotEnterprise messaging
Feishu/LarkBotRich cards, interactive elements
QQBotGroup & private messages
WeComBotWorkplace communication
MatrixBotDecentralized, E2E encryption
MoChatBotWeChat ecosystem

Each channel is configured independently in WebUI Settings and supports hot-reload on config changes.

Plugin System

ShibaClaw discovers plugins via Python entry points:

  • Channel plugins — implement BaseChannel, discoverable via shibaclaw.integrations
  • TTS plugins — implement BaseTTS, discoverable via shibaclaw.tts

Built-in: shibaclaw-channel-whatsapp (WhatsApp Web) and shibaclaw-tts-supertonic (free, offline ONNX speech synthesis, 31 languages). Install or remove plugins from WebUI Settings > Plugins, with hot-reload and version pinning. See docs/PLUGINS_DEVELOPMENT_GUIDE.md to build your own.

Text-to-Speech

The built-in Supertonic engine runs offline on ONNX (no PyTorch dependency, CPU-only), supports 31 languages with F1/M1 voice profiles and adjustable speed, and plays back through an in-browser widget. Enable it in WebUI Settings > TTS.

Automation & Scheduling

Background tasks run on cron-like schedules or event triggers (messages, webhooks, system events), in isolated sessions that don't pollute chat history. Manage, monitor, and view logs from the Automations panel; jobs persist across restarts via JSONL storage.

Knowledge Base (RAG)

Local, privacy-first retrieval-augmented generation: organize documents into named collections (PDF, CSV, HTML, TXT, Markdown), upload via drag-and-drop, and search with a FAISS index over all-MiniLM-L6-v2 embeddings. The agent can call knowledge_search during conversation, or you can target a specific collection with @kb:name. It's an optional dependency — install with pip install shibaclaw[rag].

Troubleshooting

ProblemTry
General status checkshibaclaw status
Container logsdocker logs shibaclaw-gateway / docker logs shibaclaw-web
WebUI won't connectCheck token with shibaclaw print-token, verify port binding
Provider errorsshibaclaw status shows API key and OAuth state
Login fails after upgrading from v0.9.5Run shibaclaw reset-admin
Security policySECURITY.md

See CONTRIBUTING.md to contribute and CHANGELOG.md for release history.

Collected info

  • 81 stars
  • 8 forks
  • Language: Python
  • Source updated: 9/17/2026