AIKoClaw spins up self-destroying agent sandboxes, remembers your full context, and executes real tasks — across every messaging app you already use.
Privacy by design · Self-destroying sandboxes · Zero trace sessions
Works where you already work
Every AIKoClaw agent runs with the full SOUL.md spec — lane queues, semantic snapshots, self-destroying sandboxes, and circuit breakers out of the box.
Redis ephemeral sessions, PostgreSQL episodic logs, Qdrant semantic vectors, and snapshot deltas. Your agent never forgets.
Sub-agents spin up isolated K8s pods, execute tasks, then destroy themselves — zero session traces, zero residual data.
Vault-backed secrets, HMAC-signed A2A messages, circuit breakers, and budget hard-stops. Your cloud. Your rules.
P0 critical to P3 low-priority lanes with exponential backoff, dead-letter queues, and human-review escalation built in.
Agents communicate peer-to-peer over signed Telegram messages. Task delegation, snapshot refs, and TTL-bounded payloads.
Loki logging, Prometheus metrics, PagerDuty alerts. Lane depth, error rate, circuit breakers — visible in your dashboard live.
Every deployed AIKoClaw instance runs this exact production-grade stack from your SOUL.md specification.
Six precise lifecycle steps — spawn, execute, snapshot, persist, unregister, destroy.
Run the one-line install. Your root agent registers on Telegram, verifies all memory tiers, and announces via A2A broadcast.
Share your division, budget limits, goals. Qdrant stores semantic vectors. Every interaction sharpens the context model.
Your message is classified P0–P3. Concurrency, retry policy, and timeout auto-apply. Circuit breakers protect downstream.
A fresh K8s pod instantiates, inherits the agent soul, executes with real-time semantic snapshots every 5 seconds.
Task output sent back via Telegram / Slack / WhatsApp. Snapshot delta stored to PostgreSQL and Qdrant for future learning.
Container wiped. Session traces purged. A2A registry updated. Zero residual data. Ready for the next task instantly.
finance-001 spawned · P1 lane · Budget circuit: $5,000 hard-stop set · Registered at agent.aikoclaw.local · Telegram linked. Ready.
Choose your deployment method. From local Docker to full Kubernetes production — all from your SOUL.md spec.
# One-line install — spins up full AIKoClaw stack
curl -fsSL https://aikoclaw.io/install | bash
# Then configure your bot token
aikoclaw init \
--telegram-token YOUR_BOT_TOKEN \
--domain your-domain.com \
--enable-telemetry
# Start your first agent
aikoclaw spawn --name root --division headquarters
# Pull and run with Docker Compose
curl -fsSL https://aikoclaw.io/docker-compose.yml -o docker-compose.yml
# Set environment variables
export AIKOCLAW_VERSION=1.0.0
export TELEGRAM_BOT_TOKEN=your_token_here
export ENCRYPTION_KEY=$(openssl rand -hex 32)
export JWT_SECRET=$(openssl rand -hex 32)
# Spin up Redis + PostgreSQL + Qdrant + AIKoClaw
docker compose up -d
# Check status
docker compose ps
docker compose logs aikoclaw --follow
# Apply namespace and secrets
kubectl create namespace aikoclaw
kubectl create secret generic aikoclaw-secrets \
--from-literal=telegram-token=YOUR_BOT_TOKEN \
--from-literal=encryption-key=$(openssl rand -hex 32) \
--namespace aikoclaw
# Deploy the full stack
kubectl apply -f https://aikoclaw.io/k8s/manifests.yaml
# Verify pods are running
kubectl get pods -n aikoclaw
# View live logs
kubectl logs -f deployment/aikoclaw-root -n aikoclaw
# Add AIKoClaw Helm repo
helm repo add aikoclaw https://charts.aikoclaw.io
helm repo update
# Install with production values
helm upgrade --install aikoclaw aikoclaw/aikoclaw \
--namespace aikoclaw \
--create-namespace \
--set telegram.botToken=YOUR_BOT_TOKEN \
--set domain=your-domain.com \
--set telemetry.enabled=true \
--set resources.cpu=8 \
--set resources.memory=16Gi
# Or deploy via ArgoCD
argocd app create aikoclaw \
-f https://aikoclaw.io/argocd/app.yaml \
--sync-policy automated
AIKoClaw is production-ready. SOUL.md is loaded. Your sandboxes are waiting.