Docs
Set up TrenchClaw without guessing.
Start with install and keys, then use the architecture page when you want the real explanation of the runtime, instance state, and `.runtime` versus `.runtime-state`.
Setup path
Start with setup.
Read these in order if you are setting up TrenchClaw for the first time.
Power users
Understand how the runtime is actually put together.
Use the reference page when you want the runtime shape, boot flow, instance layout, and the guard rails that separate TrenchClaw from thinner wrappers.
Short version
Use OpenRouter first. Add RPC or Ultra only when you need them.
The default path is simple: install the release, run trenchclaw, create or sign into an instance, save your OpenRouter API Key, set OpenRouter plus Step 3.5 Flash Free, test the AI connection, then stop there unless you specifically want a private RPC or Ultra swaps.
Right now
What you can do with TrenchClaw today.
The scope is intentionally narrow right now. These are the main things the current docs and setup are built around.
Swap with Ultra
Use Jupiter Ultra for the supported swap path when you add an Ultra API key.
Research with AI
Run the recommended OpenRouter setup for chat and scoped Solana workflow help.
Use private RPC when needed
Add Helius or another private RPC only when you want higher quality reads or provider-specific flows.
Manage local instances and wallets
Keep your instance state, vaults, and wallet metadata local to the runtime.