Getting Started

TinyClaw can run locally with Bun or in Docker.

Why TinyClaw exists?

The goal of TinyClaw is to make setting up an AI agent as easy as running a WordPress site — something an operator can self-host and manage without a team of engineers.

While OpenClaw and Hermes focus on personal AI assistants, TinyClaw focuses on team assistants. It is built for people who do the job at their company and need agents that work alongside the whole team, not just one person.

TinyClaw is multi-tenant from the ground up. Each organization is an isolated boundary with its own profiles, members, tools, and memory. That makes it a good fit for agencies and service companies that manage many clients under one deployment — every client gets their own org, their own agents, and their own data, all from a single TinyClaw instance.

Before you start

You need:

• An LLM provider API key
• Bun if you want to run from source

Run locally

Clone the repository and install dependencies:

git clone https://github.com/ahmadrosid/tinyclaw.git
cd tinyclaw
bun install
bun run dev:web

Open:

• Dashboard: http://localhost:3000
• API server: http://127.0.0.1:4310
• API docs: http://127.0.0.1:4310/docs

If you only want the API server:

bun run dev:server

On first run, TinyClaw asks for your provider and API key if they are not configured yet. Settings are saved in ~/.tinyclaw/config.ini.

Docker

If you want a simpler deployment path, run TinyClaw with Docker.

Quickest option:

docker pull ghcr.io/ahmadrosid/tinyclaw:latest
docker run -d -p 4310:4310 -v tinyclaw-config:/root/.tinyclaw ghcr.io/ahmadrosid/tinyclaw:latest

Build it yourself:

docker build --platform=linux/amd64 -t tinyclaw .
docker run -d -p 4310:4310 -v tinyclaw-config:/root/.tinyclaw tinyclaw

With Docker, the app is available at http://localhost:4310.

First-time setup

After TinyClaw is running:

1. Open the dashboard
2. Create the first admin account and first organization
3. Configure your model provider
4. Create or review profiles
5. Invite other users if needed

What you configure in TinyClaw

Most operators only need to think about four things:

• Organization: the tenant boundary
• Members: who can access that org
• Profiles: the bots people talk to
• Tools: what each profile is allowed to do

Integrations

TinyClaw can expose the same agent runtime through:

• Web dashboard
• CLI
• Telegram
• WhatsApp

Enable Telegram or WhatsApp from the web app settings when you are ready.

Next steps

• Overview — what TinyClaw is and how to think about it
• Multi-tenancy — how orgs, members, and roles work
• Profiles — how to define each bot
• Builtin tools — what bots can do
• MCP servers — extend bots with external tools