FastClaw
A self-hosted multi-agent runtime for operating isolated, configurable chat agents from one control plane.
- Source repo
- fastclaw-ai/fastclaw
- Stars
- ★ 1.4k
- Last updated
- 16d ago
- License
- NOASSERTION
- Primary language
- Go
- FA score
- 43/100 · Major gaps
At a glance
- Works with
- Universal · cross-platformOpenAI API · Claude API
- You'll need
- Typical use
- A SaaS team provisioning a separate bot for each customer can use a user API key and
X-Fastclaw-End-Userto lazily create users with isolated sessions, memory, and files. - Main limitation
- The FastClaw Community License adds restrictions: hosting multi-tenant SaaS for unrelated organizations requires a commercial license, and dashboard branding may not be removed or modified.
- Source review
- 43/100 · Major gaps 1 safety controls not found
What does this agent do, and when should you use it?
FastClaw is a lightweight Go AI agent runtime positioned as an Agent Factory for creating, managing, and running agents. Each agent can have its own SOUL.md, memory, skills, tools, model overrides, sessions, and channel bindings, managed through a web dashboard, CLI, and HTTP APIs. The runtime handles LLM communication, tool execution, session isolation, and Docker or E2B sandboxing; SQLite is the default store, with Postgres documented for multi-pod deployments. It exposes Telegram, Discord, and Slack channels plus an OpenAI-compatible chat-completions endpoint, making it a fit for teams building a self-hosted agent backend or application integration layer.
On first launch, fastclaw opens a setup wizard to configure an LLM provider and create a default agent; the dashboard can edit system files such as SOUL.md, IDENTITY.md, and MEMORY.md, and configure models, skills, IM channels, and schedules. For incoming chats, the runtime stores sessions isolated by agent × user and by channel/chatID, and can invoke built-in exec, read_file, write_file, list_dir, web_fetch, web_search, and memory_search tools. With sandboxing enabled, Docker or E2B environments hydrate skills and workspaces, then sync sandbox-side files back to durable storage after each tool call. Applications can call streaming /v1/chat/completions, provision isolated end users through POST /v1/users or X-Fastclaw-End-User, while administrators manage resources through /api/agents, /api/config, /api/skills/install, and /api/apikeys.
- A SaaS team provisioning a separate bot for each customer can use a user API key and
X-Fastclaw-End-Userto lazily create users with isolated sessions, memory, and files. - An internal platform team operating several role-specific assistants can give every agent its own SOUL.md, model settings, skills, and private skill directory.
- A team delivering a focused support or business bot in Telegram, Discord, or Slack can bind that channel to an agent and keep individual chat threads separate.
- An application developer who needs a chat-agent backend can call the streaming OpenAI-compatible
/v1/chat/completionsendpoint instead of driving the web chat UI. - A team that needs agents to run code or manipulate files while constraining execution in hosted deployments can choose Docker or E2B sandboxing with
FASTCLAW_DEPLOY=hosted.
How do you install or deploy this agent?
Install:
curl -fsSL https://raw.githubusercontent.com/fastclaw-ai/fastclaw/main/install.sh | bashRun for the first time:
fastclawConfigure an LLM provider in the wizard; it creates a default agent. To create an OpenAI-backed agent from the CLI, make OPENAI_API_KEY available in the environment, then run:
fastclaw agents init alpha --provider openai --model openai/gpt-4o-mini --api-key-env OPENAI_API_KEYThe dashboard is at http://localhost:18953; use fastclaw daemon start for background execution.
How do you use this agent?
Use fastclaw agents ls to inspect agents, fastclaw agents config alpha set temperature 0.7 to change agent configuration, and fastclaw agents files put alpha SOUL.md ./SOUL.md to upload an identity file. In the dashboard, open an agent to test chat, install private skills, bind Telegram/Discord/Slack, inspect sessions, and manage cron jobs created by that agent. For application integration, send OpenAI-compatible streaming requests to /v1/chat/completions; a multi-tenant app uses a user API key and X-Fastclaw-End-User: <your-app-user-id>.
What are this agent's strengths and limitations?
- A single Go binary combines the dashboard, CLI, runtime, session management, and HTTP API, reducing the amount of infrastructure a team must assemble.
- Agent-level model overrides, skills, identity files, channels, and user-partitioned sessions and memory support multiple independently configured roles in one deployment.
- SQLite provides a simple default path, while Postgres, Redis, object storage, and Kubernetes are explicitly documented for scaled deployments.
- Docker and E2B sandboxing include skill/workspace synchronization; hosted mode can force exec and file calls inside the sandbox.
- The FastClaw Community License adds restrictions: hosting multi-tenant SaaS for unrelated organizations requires a commercial license, and dashboard branding may not be removed or modified.
- LLM providers, bot channels, and external web search/fetch require network access and relevant provider or bot credentials; the supplied material does not establish service costs or quotas.
- On self-hosted installations, host-shell execution is the default unless the model chooses
exec(sandbox:true); deployments exposed to untrusted IM users needFASTCLAW_SANDBOX_ENFORCE=1for hosted-style enforcement. - Multi-pod operation requires Postgres, Redis when shared channel leases and message streams are needed, and S3-compatible object storage for distributed skill/file hydration.
How does this agent compare with similar options?
The repository topics label FastClaw as an OpenClaw alternative; the supplied material does not provide a verifiable feature-by-feature comparison.
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| FastClaw This agent | 43 · Major gaps | ★ 1.4k | 16d ago | Go | OpenAI API · Claude API |
| Shannon | 53 · Major gaps | ★ 2.3k | 18d ago | Go | OpenAI API · Claude API |
| Osaurus | 80 · Good | ★ 8k | 4d ago | Swift | OpenAI API · Claude API |
| TrueForge | 67 · Some gaps | ★ 5.8k | 5d ago | TypeScript | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows role-based API keys (admin/user/agent) and sandbox options, but least privilege defaults not explicit; user confirmation exists (e.g., public access toggle, API key creation) but not systematic; data flow transparency partially described (e.g., storage locations) but lacks detailed data flow diagrams; sensitive data handling mentioned (e.g., API keys shown once) but not deep; dependency security not mentioned vulnerability scanning or pinning; external effects have sandbox and network config but default restrictions not explicit; rollback not mentioned; source attribution has copyright notice but publisher unverified.
Self-consistency good, docs align with code structure, but no test evidence; dependency availability not mentioned version pinning or mirrors; failure messages not provided with examples.
Audience and scenarios clear (developers, enterprises), capability boundaries described (e.g., sandbox boundaries), trigger precision partial (e.g., scheduler), environment fit good (multiple deployment options).
Information architecture clear, install notes detailed, naming stability moderate (version tags), examples and FAQ present, known limitations partial (e.g., sandbox boundaries), license clear, versioning changelog not provided, maintenance responsibility has copyright holder but unverified.
Output usability has API and CLI, marginal value high (multi-agent framework), cost-benefit not quantified.
Claim traceability moderate, cross-source corroboration insufficient, fact-inference separation unclear.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Publisher identity unverified, treat source with caution.
- Dependency security not mentioned vulnerability scanning or pinning, need to check yourself.
- Rollback mechanism not mentioned, assess data loss risk.
- Sandbox default configuration may not be strict enough, adjust based on deployment environment.
FAQ
Which models can FastClaw use?
Can an external application isolate data for its own end users?
X-Fastclaw-End-User, or POST /v1/users, creates a stable internal identity for an external user; sessions, memory, and files are isolated per end user.How safe are shell and file operations?
FASTCLAW_DEPLOY=hosted, exec and file calls are locked in the sandbox. Self-hosted mode defaults to the host shell, unless FASTCLAW_SANDBOX_ENFORCE=1 enables hosted-style lockdown.Can it be operated without the dashboard?
fastclaw agents manages agents, configuration, and system files in the same store, while fastclaw apikey creates, rotates, and deletes API keys.