Skip to main content

​
Prerequisites

  • Node.js >= 22.12.0
  • An LLM API key (Anthropic, OpenAI, or any OpenAI-compatible provider)

​
Install

mkdir -p ~/siclaw-work
cd ~/siclaw-work
npm install -g siclaw

siclaw local
Launches the Web UI at http://localhost:3000. On first launch, open the page and register the first user — that account becomes the admin. After that, new registrations require admin authentication.

​
CLI

siclaw
TUI mode for personal terminal diagnostics.

​
From Source

git clone https://github.com/scitix/siclaw.git
cd siclaw
npm ci
make build-portal-web
npm run build
node siclaw.mjs

​
Configure Your LLM

On first run, Siclaw launches a setup wizard to configure your LLM provider.
If you started siclaw local first (recommended for teams), the wizard detects the running Portal and redirects provider setup to the Portal Web UI’s Models page. One configuration in Portal serves every paired TUI — no per-workstation settings.json to drift out of sync.
If you prefer the standalone TUI path, you can also edit .siclaw/config/settings.json manually: 
{
  "providers": {
    "default": {
      "baseUrl": "https://api.anthropic.com/v1",
      "apiKey": "sk-ant-...",
      "api": "anthropic",
      "models": [{ "id": "claude-sonnet-4-20250514", "name": "Claude Sonnet 4" }]
    }
  }
}
Siclaw supports any OpenAI-compatible API. See LLM Providers for Ollama, vLLM, Azure, and other setups.

​
Run Your First Investigation

Describe an issue: 
? What would you like to investigate?
> Pod CrashLoopBackOff in production cluster after deployment
For complex issues, activate Deep Investigation mode (/dp or Ctrl+I) to run a structured investigation — the agent triages, proposes hypotheses for your review, validates in parallel after your confirmation, and produces a structured report with root cause, confidence score, and remediation steps. Investigation traces are saved to .siclaw/traces/ (relative to where Siclaw was launched).

​
Add Cluster Access

To investigate Kubernetes issues, import a kubeconfig into Siclaw:
  • Standalone TUI (no local Portal): /setup inside the session
  • Local Server, or TUI paired with one: Clusters / Hosts in the Web UI — paired TUIs pick up the imports on the next launch
Siclaw uses its stored credentials when running diagnostic tools.

​
What’s Next?