feat: support claude-code setup and status

docs-site/content/docs/cli-reference/ktx-setup.mdx

@@ -51,7 +51,8 @@ scripted project creation. They are not shown in `ktx setup --help`.
 
 | Flag | Description |
 |------|-------------|
-| `--llm-backend <backend>` | LLM backend: `anthropic` or `vertex` |
+| `--llm-backend <backend>` | LLM backend: `anthropic`, `vertex`, or `claude-code` |
+| `--llm-backend claude-code` | Use the local Claude Code session for KTX LLM calls |
 | `--anthropic-api-key-env <name>` | Environment variable containing the Anthropic API key |
 | `--anthropic-api-key-file <path>` | File containing the Anthropic API key |
 | `--anthropic-model <model>` | Anthropic model ID to validate and save |
@@ -61,7 +62,8 @@ scripted project creation. They are not shown in `ktx setup --help`.
 
 Choose only one Anthropic credential source. Anthropic credential flags are only
 valid with the Anthropic backend; Vertex flags are only valid with the Vertex
-backend.
+backend. The `claude-code` backend uses local Claude Code authentication instead
+of Anthropic API key or Vertex flags.
 
 ### Embeddings
 

docs-site/content/docs/cli-reference/ktx-status.mdx

@@ -47,6 +47,10 @@ ktx status --project-dir ./analytics
 `ktx status` prints grouped doctor checks. Agents should use
 `ktx status --json --no-input` when they need to branch on readiness state.
 
+For `llm.provider.backend: claude-code`, `ktx status` checks that the local
+Claude Code session is usable. If auth fails, run the Claude Code CLI login
+flow, then rerun `ktx status`.
+
 ```json
 {
   "title": "KTX project doctor",

docs-site/content/docs/getting-started/quickstart.mdx

@@ -59,12 +59,13 @@ completed setup steps and resumes from the remaining work.
 KTX uses a Claude model for ingest agents that turn schemas, SQL, BI metadata,
 and documents into semantic-layer sources and wiki context.
 
-Setup supports two LLM provider paths:
+Setup supports three LLM provider paths:
 
 | Provider | Use when | Credential model |
 |----------|----------|------------------|
 | Anthropic API | You have an Anthropic API key | `ANTHROPIC_API_KEY` or a local `file:` secret |
 | Google Vertex AI for Anthropic Claude | Your organization runs Claude through Google Cloud | Application Default Credentials plus Vertex project and location |
+| Claude Code | You want KTX to use your local Claude Code session | Claude Code local authentication |
 
 For Anthropic API, setup can read the key from the environment or save a pasted
 key to `.ktx/secrets/anthropic-api-key`. `ktx.yaml` stores an `env:` or `file:`
@@ -74,6 +75,25 @@ For Vertex AI, setup uses Google Application Default Credentials. It can read
 your active `gcloud` project, list visible projects, or accept explicit
 `--vertex-project` and `--vertex-location` values.
 
+To use your local Claude Code session instead of an API key, set:
+
+```yaml
+llm:
+  provider:
+    backend: claude-code
+  models:
+    default: sonnet
+    triage: haiku
+    candidateExtraction: sonnet
+    curator: sonnet
+    reconcile: sonnet
+    repair: sonnet
+```
+
+`claude-code` uses the Claude Code authentication already configured on your
+machine. It doesn't use `ANTHROPIC_API_KEY`, Vertex credentials, AI Gateway
+tokens, or Bedrock credentials.
+
 Setup checks the selected model before saving. Anthropic API setup fetches live
 Claude model choices when possible and falls back to bundled defaults if model
 discovery is unavailable.

docs-site/content/docs/guides/building-context.mdx

@@ -58,6 +58,10 @@ ktx ingest --all --deep
 Deep ingest needs LLM and embedding readiness. If those providers are not
 configured, run `ktx setup` or use `--fast`.
 
+When you use `claude-code`, KTX still controls the tool surface for ingest and
+memory capture. Claude Code built-in tools, discovered MCP servers, hooks,
+skills, plugins, agents, and slash commands are not exposed to KTX agent loops.
+
 ## Query history
 
 PostgreSQL, BigQuery, and Snowflake can add query-history context. This helps

docs-site/content/docs/guides/llm-configuration.mdx

@@ -0,0 +1,48 @@
+---
+title: LLM configuration
+description: Configure KTX LLM providers, model roles, and prompt caching.
+---
+
+KTX uses the top-level `llm` block in `ktx.yaml` for text generation,
+structured extraction, and ingest or memory agent loops.
+
+## Backends
+
+Set `llm.provider.backend` to one of these values:
+
+- `anthropic`: Use the Anthropic API through `ANTHROPIC_API_KEY` or the
+  configured `api_key` reference.
+- `vertex`: Use Vertex AI Anthropic models through Google Cloud credentials.
+- `gateway`: Use AI Gateway-compatible Anthropic model ids.
+- `claude-code`: Use your local Claude Code session through the Claude Agent
+  SDK. KTX removes provider-routing environment variables from Claude Code
+  child processes, so this backend doesn't silently fall back to
+  `ANTHROPIC_API_KEY`, Vertex, Gateway, or Bedrock credentials.
+
+## Claude Code
+
+Use aliases or full Claude model ids in `llm.models`:
+
+```yaml
+llm:
+  provider:
+    backend: claude-code
+  models:
+    default: sonnet
+    triage: haiku
+    candidateExtraction: sonnet
+    curator: sonnet
+    reconcile: sonnet
+    repair: sonnet
+```
+
+`claude-code` keeps KTX tool boundaries intact. KTX exposes only the MCP tools
+needed for the current KTX agent loop and disables Claude Code built-in tools,
+filesystem settings, skills, plugins, agents, hooks, and slash commands.
+
+## Prompt caching
+
+`llm.promptCaching` has partial parity on `claude-code`. KTX doesn't pass
+Anthropic cache-control markers to the Claude Agent SDK. Status and doctor warn
+when you configure prompt-cache TTL, tool, or history fields that the Claude
+Agent SDK backend ignores.

docs-site/content/docs/guides/meta.json

@@ -1,5 +1,5 @@
 {
   "title": "Guides",
   "defaultOpen": true,
-  "pages": ["building-context", "writing-context", "serving-agents"]
+  "pages": ["building-context", "llm-configuration", "writing-context", "serving-agents"]
 }