For people who want a personal AI assistant they can install and operate on their own machine or server, with a UI and configurable tools ready to use.
One place to work — built-in WebUI, a Windows desktop launcher, and a mobile layout for access over your LAN.
Your choice of model — local LLMs through Ollama or an OpenAI-compatible server; cloud providers and documented OAuth integrations.
— editable memory, reusable skills, and an optional document knowledge base.
Self-hosted personal AI agent with a WebUI, memory, tools, MCP, sub-agents and automations. Connect local or cloud LLMs.
Estrelas
84
Ferramentas
—
Disponibilidade
—
Persistent context
Tools and MCP — file, shell and web tools, plus external tools through the Model Context Protocol.
Multi-agent tasks and automation — isolated or forked sub-agents, scheduled tasks, and optional project verification.
Security controls in the core — an encrypted credential vault, workspace restrictions, SSRF filtering and prompt-injection defenses. See their scope and limits.
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)
Choose the installer for your operating system, or use Docker or pip below.
[!TIP]
Bring your own model: start with Ollama, an OpenAI-compatible endpoint, or a cloud provider such as OpenRouter. Model availability, pricing and limits depend on the provider.
Or download and open ShibaClaw-Setup.exe. The PowerShell command downloads the same setup, verifies its SHA256 against the GitHub release asset digest, and starts it.
curl -fsSL https://raw.githubusercontent.com/RikyZ90/ShibaClaw/main/docker-compose.yml -o docker-compose.yml
docker compose up -d # pulls from Docker Hub
Open http://localhost:3000, create your admin account on first launch (or sign in to an existing account), and follow the onboarding wizard. To reach it from your phone, configure authenticated access over your LAN, for example through an HTTPS reverse proxy.
pip
pip install shibaclaw
shibaclaw web --with-gateway # starts WebUI + agent engine on :3000
Open http://localhost:3000, create your admin account on first launch and follow the onboarding wizard. shibaclaw onboard configures the agent and workspace from the CLI; WebUI account creation still happens in the browser.
Security controls are part of the agent runtime. Their effectiveness depends on configuration, installed audit tools and the tools you authorize.
Layer
What it does
Credential storage
Fernet-encrypted vault; encryption key in the OS keyring when available, with a restricted key-file fallback
Install-time audit
Checks recognized package-install commands; blocks findings at the configured severity when the audit completes. Missing tools, errors or timeouts can allow installation with a warning
Prompt-injection defenses
Randomized tool-output boundaries and pre-scanning of untrusted content
Prompt-injection defenses reduce exposure to untrusted tool output; they cannot guarantee safe model behavior. Protect the host account and vault key, review tool permissions, and use authentication and HTTPS when exposing the WebUI beyond localhost. Using a cloud model or remote MCP service sends relevant content to that service.
Working memory (per session) — rolling context with automatic summarization and token-aware truncation
Long-term memory (cross-session) — editable USER.md, memory/MEMORY.md and memory/HISTORY.md, with fact extraction and ranked history search
Procedural memory (skills & automations) — learned workflows saved as reusable skills, plus cron-like schedules
The WebUI exposes memory editing, the dream diary and quarantined entries; sessions are stored as append-only JSONL. The optional knowledge base adds FAISS document retrieval separately from these memory files.
MCP & Integrations
ShibaClaw is an MCP agent: it connects to external tools using the Model Context Protocol and registers the tools returned by each configured server. Add servers in Settings; transport, authentication and tool behavior must be compatible with the server you choose.
Connected Apps integrates with Klavis for hosted OAuth connections and MCP servers. Available apps and access depend on your Klavis account. Review each server's permissions and data handling before connecting it.
ShibaClaw uses provider-specific adapters and OpenAI-compatible endpoints, without a LiteLLM proxy. It resolves the provider from the selected model or a provider-prefixed model ID. Configured provider catalogs appear in the WebUI; the provider registry is the source of truth for supported routes.
¹ 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. On Docker Desktop, use host.docker.internal to reach a host model server; native Linux needs a reachable host address or host-gateway mapping. See the Ollama networking instructions, including the required /v1 API base.
Account connections — availability and permitted use depend on each provider's current terms and your account.
Provider
Flow
Setup
OpenRouter
PKCE browser flow; returned API key saved in the credential vault
PKCE 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
The integration guides cover callback URLs, Docker networking, account limits and troubleshooting. A successful connection does not imply unlimited requests or access to every model.
Architecture
Docker Compose
Service
Role
Default port
shibaclaw-gateway
Core agent loop, message bus, channel integrations and automations
19999 (HTTP) · 19998 (WS)
shibaclaw-web
WebUI (Starlette + WebSocket), proxy to the gateway
3000
Both mount the host's ./.shibaclaw/ data directory at /root/.shibaclaw for config, workspace, memory, automation jobs and media. Outside Docker, shibaclaw web --with-gateway starts the gateway as a managed background process. shibaclaw web alone expects a running gateway.
Container limits — the supplied Compose file sets a 512 MB limit / 256 MB reservation for the gateway, and a 128 MB limit / 64 MB reservation for the WebUI. These are configuration limits, not measured memory requirements; RAG and local model servers need their own capacity planning.
CLI Reference
shibaclaw web # Start WebUI; requires a running gateway
shibaclaw gateway # Start gateway only (for Docker split)
shibaclaw onboard # CLI-based first-time setup wizard
shibaclaw agent "Hello" # One-shot message via terminal
shibaclaw agent # Interactive REPL with history
shibaclaw status # Provider, workspace, OAuth health check
shibaclaw channels status # List enabled channels
shibaclaw provider login <p># OAuth login (github-copilot, openai-codex)
shibaclaw desktop # Launch Windows desktop app
Channels
Channel
Type
Notes
WebUI
Built-in
Primary interface, full feature access
Discord
Bot
Rich embeds, slash commands, attachments
Telegram
Bot
Inline keyboards, media, reply markup
WhatsApp
Plugin
Via WhatsApp Web
Slack
Bot
Block kit, threads, app mentions
DingTalk
Bot
Enterprise messaging
Feishu/Lark
Bot
Rich cards, interactive elements
QQ
Bot
Group & private messages
WeCom
Bot
Workplace communication
Matrix
Bot
Decentralized, E2E encryption
MoChat
Bot
WeChat 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
Included plugin projects: shibaclaw-channel-whatsapp (WhatsApp Web) and shibaclaw-tts-supertonic (local speech synthesis using Supertonic and ONNX Runtime). Manage plugin installation in WebUI Settings > Plugins. See the plugin development guide to build your own.
Text-to-Speech
The Supertonic plugin synthesizes speech locally and downloads its model assets on first use. Select the engine, voice and language in the WebUI audio settings. Available voices and languages depend on the installed Supertonic model; see the plugin implementation.
Automation & Scheduling
Schedule one-shot, interval or cron tasks, or use heartbeat jobs that read a task file and decide whether to act. Manage jobs in the Automations panel; definitions and state persist in automation.json. Approval requirements and delivery destinations are configured per job. See the automation skill for examples of workflow automation.
Knowledge Base (RAG)
Organize documents into named collections (PDF, CSV, HTML, TXT, Markdown), upload via the WebUI, and search a FAISS index. The agent can call knowledge_search, or you can target a collection with @kb:name.
Install the optional document stack with pip install shibaclaw[rag]. For local embeddings, use pip install "shibaclaw[rag-local]"; the default local model is all-MiniLM-L6-v2 and needs an initial model download. Cloud embedding providers require configuration and send document content to that provider.
Provider endpoints — Configure multiple independently named endpoints, including local servers without API keys; save and enable each endpoint separately.
Model selection — Find endpoints in chat and Agent settings, enter custom model IDs, and return a chat to its default model.
Automation reliability — Preserve approvals, delivery settings and task instructions while scheduling, editing and deleting jobs.
Security fixes — Require patched filelock and pypdf for optional RAG support and refresh the locked setuptools dependency.
Reliable delegation and project checks — Background tasks keep their status across chat reconnects, distinguish execution from optional project verification, and show real exit codes, bounded logs, and check durations. See project verification for setup.
Chat rendering — Restores final responses and missed messages accurately, keeps active input intact when a background result arrives, and renders task details safely on desktop and mobile.
Windows installation — The PowerShell command downloads the per-user setup, verifies its SHA256, and launches it. First-launch startup keeps the native window responsive while the local service starts.
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo ShibaClaw?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
ShibaClaw precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte ShibaClaw usa?
ShibaClaw roda localmente via stdio.
Quando ShibaClaw foi verificado pela última vez?
Última verificação: 2026-10-27. Self-hosted personal AI agent with a WebUI, memory, tools, MCP, sub-agents and automations. Connect local or cloud LLMs.