Kazma is the multi-agent coordinator engineered for production. Secure your workspace with
cryptographic skill signatures, triple-wired human-in-the-loop gates, and real-time telemetry
across Web, Telegram, Slack, and Discord.
Verified 2026-07-10 · 77858fb fix: add all 15 slash commands to TUI autocomplete + help (2026-07-10) — figures derived from git-tracked files via scripts/generate_metrics.py
Never let an LLM run unsafe code or modify production files unsupervised. Kazma intercepts dangerous operations fail-closed at three layers.
Triple-Wired HITL Safety Gates
Three-tier approval gates — graph interrupt, swarm bus, and MCP classification. Danger tools require human approval across Web, Telegram, Discord, and Slack. State is tracked atomically; operations resume exactly where they paused.
Cryptographic Skill Checksums
Every downloaded skill and plugin is validated against a timing-safe HMAC-SHA256 checksum matching your secret. Altered signatures trigger an immediate fail-closed abort.
Authenticated MCP Servers
Bearer tokens, custom headers, and configurable trust tiers. Every MCP tool is classified by risk for appropriate gating.
Self-Healing Circuit Breakers
Real-time status badges — red, yellow, hidden. Automatic recovery with configurable thresholds. Start, stop, cancel, retry with lineage tracking.
Multi-Platform Approvals
Interactive sliding cards over live SSE in the Web client. Inline buttons in Telegram, Discord, and Slack. Approve or deny from any surface.
Idempotent DB Sync & WAL
SQLite WAL mode with a 5000ms busy timeout ensures concurrent multi-user TUI/Web write safety. reconcile_from_yaml() seeds keys without clobbering overrides.
Live telemetry · mock stream
Token throughput
0 tok/s
Active agents
0
p95 response
0 ms
Swarm patterns
0
SSH command console
The dual-command center.
Monitor and command your swarm directly over lightweight SSH sessions or terminal panels. Track multi-step workflows without screen corruption — Kazma isolates complex Mermaid.js rendering to explicit DOM nodes, neutralizing style leakage.
Scrolling metrics sparklines.Real-time CPU, Memory, and VRAM history inside your terminal.
Vim-style console bar.Activate with : to jump tabs, reload themes, clear caches.
ASCII NOC topology map.Inter-node comms and live handoff paths across the swarm.
Bi-lingual RTL mirroring.Perfect layout alignment for Arabic-first environments.
kazma-tui · ssh connected
Zero to autonomous in three steps.
Clone, configure, deploy — three entry points for every workflow.
01
Install & configure
Clone the repo, run uv sync, point at your LLM provider. Web UI, TUI, or CLI — your choice.
02
Connect channels
Plug in Telegram, Discord, or Slack via the headless gateway. One backend, many adapters.
03
Deploy & monitor
Pick a persona, enable RAG, set safety gates, spawn swarm workers. Watch it live via SSE.
The product
One brain, every surface.
A single LangGraph supervisor drives the dashboard, chat, swarm playground, skills, and MCP servers — bilingual, RTL-ready, live.
Workspace
Projects, rules, and context per workspace.
Chat
Streaming agent chat with HITL approval cards.
Swarm Playground
Dispatch patterns with live aggregation.
Skills
Signed, validated skill registry.
MCP Servers
Authenticated external tool servers.
LLM Providers
120+ models via one OpenAI-compatible layer.
The origin
What does “Kazma” mean?
A name rooted in Kuwaiti history — and engineered into architecture.
Kazma (كاظمة) was an ancient coastal region in Kuwait — famed as a vital oasis
network of water wells and a strategic trade gateway connecting distinct civilizations. It was also the site of
the legendary Battle of Chains (Dhat al-Salasil, 633 CE), where strict,
unified coordination broke a rigid defensive line through precise, decentralized maneuvering.
We engineered Kazma.ai on these same legacy pillars — not as metaphor, but as architecture:
The Wells
Deep memory that holds context across sessions — the agent draws from it when it needs to remember, like caravans drawing from oasis wells.
The Gateway
One LangGraph supervisor routed out to many channels — Telegram, Discord, Slack, Web — the way Kazma routed trade between regions.
The Chains
Every skill is HMAC-signed and every dangerous action passes through three human-in-the-loop gates — coordination chains that can’t be quietly broken.
Architecture
Three pillars of production-grade orchestration.
Immutable security, triple-wired HITL gates, and self-healing dual-UI telemetry — layered, decoupled, and independently replaceable.