You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installer resolves the latest stable release tag and installs that version by default.
63
+
To pin a version: `SWARMCLAW_VERSION=v0.1.0 curl ... | bash`
64
+
62
65
Or run locally from the repo (friendly for non-technical users):
63
66
64
67
```bash
@@ -290,7 +293,7 @@ Token usage and estimated costs are tracked per message for API-based providers
290
293
The daemon auto-processes queued tasks from the scheduler on a 30-second interval. It also runs recurring health checks that detect stale heartbeat sessions and can send proactive WhatsApp alerts when issues are detected. Toggle the daemon from the sidebar indicator or via API.
291
294
292
295
-**API:**`GET /api/daemon` (status), `POST /api/daemon` with `{"action": "start"}` or `{"action": "stop"}`
293
-
- Auto-starts on boot if queued tasks are found
296
+
- Auto-starts on first authenticated runtime traffic (`/api/auth` or `/api/daemon`) unless `SWARMCLAW_DAEMON_AUTOSTART=0`
You can also tune shell timeout, Claude Code delegation timeout, and CLI provider process timeout from the same settings panel.
318
321
322
+
## Capability Policy
323
+
324
+
Configure this in **Settings → Capability Policy** to centrally govern tool access:
325
+
326
+
-**Mode:**`permissive`, `balanced`, or `strict`
327
+
-**Blocked categories:** e.g. `execution`, `filesystem`, `platform`, `outbound`
328
+
-**Blocked tools:** specific tool families or concrete tool names
329
+
-**Allowed tools:** explicit overrides when running stricter modes
330
+
331
+
Policy is enforced in both session tool construction and direct forced tool invocations, so auto-routing and explicit tool requests use the same guardrails.
332
+
319
333
## CLI Troubleshooting
320
334
321
335
-**Claude delegate returns no output or fails quickly:** verify Claude auth on the host with:
@@ -419,6 +433,18 @@ docker compose up -d
419
433
420
434
Data is persisted in `data/` and `.env.local` via volume mounts. Updates: `git pull && docker compose up -d --build`.
421
435
436
+
For prebuilt images (recommended for non-technical users after releases):
437
+
438
+
```bash
439
+
docker pull ghcr.io/swarmclawai/swarmclaw:latest
440
+
docker run -d \
441
+
--name swarmclaw \
442
+
-p 3456:3456 \
443
+
-v "$(pwd)/data:/app/data" \
444
+
-v "$(pwd)/.env.local:/app/.env.local" \
445
+
ghcr.io/swarmclawai/swarmclaw:latest
446
+
```
447
+
422
448
### Updating
423
449
424
450
SwarmClaw has a built-in update checker — a banner appears in the sidebar when new commits are available, with a one-click update button. Your data in `data/` and `.env.local` is never touched by updates.
@@ -429,7 +455,7 @@ For terminal users, run:
429
455
npm run update:easy
430
456
```
431
457
432
-
This command fetches/pulls `origin/main`, installs dependencies when needed, and runs a production build check before restart.
458
+
This command updates to the latest stable release tag when available (fallback: `origin/main`), installs dependencies when needed, and runs a production build check before restart.
433
459
434
460
## Development
435
461
@@ -472,6 +498,21 @@ npm run quickstart:prod # setup + build + start production server
472
498
npm run update:easy # safe update helper for local installs
473
499
```
474
500
501
+
### Release Process (Maintainers)
502
+
503
+
SwarmClaw uses tag-based releases (`vX.Y.Z`) as the stable channel.
504
+
505
+
```bash
506
+
# example patch release
507
+
npm version patch
508
+
git push origin main --follow-tags
509
+
```
510
+
511
+
On `v*` tags, GitHub Actions will:
512
+
1. Run CI checks
513
+
2. Create a GitHub Release
514
+
3. Build and publish Docker images to `ghcr.io/swarmclawai/swarmclaw` (`:vX.Y.Z`, `:latest`, `:sha-*`)
515
+
475
516
## CLI
476
517
477
518
SwarmClaw ships a built-in CLI for core operational workflows:
0 commit comments