> ## Documentation Index
> Fetch the complete documentation index at: https://docs.siclaw.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started

> Install Siclaw and run your first investigation in under 5 minutes.

## Prerequisites

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

## Install

```bash theme={null}
mkdir -p ~/siclaw-work
cd ~/siclaw-work
npm install -g siclaw
```

### Local Server (recommended for teams)

```bash theme={null}
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

```bash theme={null}
siclaw
```

TUI mode for personal terminal diagnostics.

### From Source

```bash theme={null}
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.

<Note>
  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.
</Note>

If you prefer the standalone TUI path, you can also edit `.siclaw/config/settings.json` manually:

```json theme={null}
{
  "providers": {
    "default": {
      "baseUrl": "https://api.anthropic.com/v1",
      "apiKey": "sk-ant-...",
      "api": "anthropic",
      "models": [{ "id": "claude-sonnet-4-20250514", "name": "Claude Sonnet 4" }]
    }
  }
}
```

<Note>
  Siclaw supports any OpenAI-compatible API. See [LLM Providers](/configuration/providers) for Ollama, vLLM, Azure, and other setups.
</Note>

## 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](/features/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?

* [Core Concepts](/start/core-concepts) — understand the investigation engine
* [Your First Investigation](/start/first-investigation) — walk through a complete diagnosis
* [LLM Providers](/configuration/providers) — detailed provider configuration
* [Deploy for your team](/install/kubernetes) — production multi-user deployment