Reference
Reference content is for looking things up. If you want to know what a flag does, what a config key controls, or which channels exist, you are in the right section.
| Page | Covers |
|---|---|
| CLI | Every command and flag |
| Configuration | config.toml schema |
| Providers | Built-in providers and their settings |
| Channels | Built-in channels and their settings |
| Tools | Built-in tools and their parameter schemas |
| Skills | SKILL.toml / SKILL.md schema |
| Troubleshooting | Common failures and remediation |
| Knowledge Base | Document ingest, retrieval, and the KB_* reference |
Where this content comes from
The CLI, Config, Providers, Channels, Tools, Skills, and Troubleshooting pages are maintained hand-written references, kept in sync with the rantaiclaw crate rather than left as placeholders. Where a page cites a crate path (e.g. “defined in src/config/schema.rs”), that path is the source of truth. Some pages may later be generated from rantaiclaw source — --help output, JSON Schema export, tool registry introspection — as an extra guard against drift.
Maintenance status:
| Page | Future generation source | Status |
|---|---|---|
| CLI | rantaiclaw --help parsed by scripts/gen-cli.ts | hand-written (maintained) |
| Config | cargo run --bin rantaiclaw -- config schema --json (uses schemars) | hand-written (maintained) |
| Providers | Trait scan + per-provider config block | hand-written (maintained) |
| Channels | Same | hand-written (maintained) |
| Tools | Tool registry dump | hand-written (maintained) |
| Skills | Hand-written from spec; the schema itself rarely changes | hand-written (maintained) |
| Troubleshooting | Hand-written; aggregates known issues | hand-written (maintained) |
Last updated on