Configuration

Krait works with zero config for single-language projects. For monorepos or custom setups, krait.toml gives you full control.

Generating Config

krait init           # auto-detect and write krait.toml
krait init --dry-run # preview without writing
krait init --force   # overwrite existing config

Config Location

Krait looks for config in this order:

1. krait.toml in the project root
2. .krait/config.toml in the project root
3. Auto-detection (fallback)

Schema

# krait.toml — generated by `krait init`

# Optional: override the project root
# root = "."

# Workspaces to index. Each gets its own LSP server.
[[workspace]]
path = "packages/api"
language = "typescript"

[[workspace]]
path = "packages/web"
language = "typescript"

[[workspace]]
path = "backend"
language = "go"

# Optional: server overrides
# [servers.typescript]
# binary = "vtsls"
# args = ["--stdio"]

Fields

workspace

Field	Type	Required	Description
path	string	Yes	Relative path to workspace root
language	string	Yes	Language: typescript, javascript, go, rust, cpp
server	string	No	LSP server binary override for this workspace

servers.<lang>

Field	Type	Description
binary	string	Server binary name (must be in PATH or managed dir)
args	string[]	Arguments (default: ["--stdio"])

Status Output

When config is loaded, krait status shows:

daemon: pid=12345 uptime=5m
config: krait.toml (5 workspaces)
lsp: 5 sessions

When auto-detected:

daemon: pid=12345 uptime=5m
lsp: 5 sessions

Committing to Git

It’s recommended to commit krait.toml to your repository. This ensures the whole team uses the same workspace configuration:

git add krait.toml
git commit -m "chore: add krait config"