CONFIGURATION

Settings

What this deployment can do, and what it cannot. Missing pieces are shown as-is; nothing is faked around them.

Account

Not signed in. Sign in to use the console.

GitHub connection

disconnectedOAuth not configured

AI provider

not configured

Plans fall back to deterministic rules; patch generation is unavailable. Set ANTHROPIC_API_KEY (default model claude-opus-5) or OPENAI_API_KEY, optionally AI_PROVIDER / ANTHROPIC_MODEL / OPENAI_MODEL.

Execution provider

Execution provider is not configured.

Execution provider is not configured. Set SANDBOX_PROVIDER (e2b | docker | local-dev).

SANDBOX_PROVIDER = e2b (E2B_API_KEY) · docker (SANDBOX_DOCKER_IMAGE) · local-dev (development only).

Database & secrets

PostgreSQL configuredsession secret set

Sessions are HMAC-signed cookies; GitHub tokens are encrypted at rest with a key derived from KIBO_ENCRYPTION_KEY (fallback NEXTAUTH_SECRET). Wallet keys are never stored.

Chains & wallet

Ethereum #1public fallback
Base #8453public fallback
Arbitrum One #42161public fallback
Sepolia #11155111public fallback
Robinhood Chain #4663RPC configured

WalletConnect not configured (injected wallets only)

Command policy

Kibo may propose commands; only these families pass CommandPolicy.validate(). Shell operators, paths outside the repository, network tools, git and privilege escalation are always rejected.

npmNode package managers: install and run package.json scripts.
npxNode binary runners for common toolchains.
forgeFoundry: compile and test Solidity.
cargoRust: cargo test / build / check.
goGo: test / build / vet.
pythonPython test and lint tools.
makeMakefile targets.

Extra families via KIBO_ALLOWED_COMMANDS. App URL: https://www.kibocoderh.xyz

Security model

Server-side authorization on every API route; state-changing routes reject cross-origin requests and are rate-limited.
Inputs are validated with zod; repository paths are normalised and confined; protected files (.env*, keys, .git) are never written.
Generated code never runs on the KiboCode server: verification happens in the configured sandbox provider.
The default branch is never modified. Work lands on kibo/<task> branches and pull requests that are never merged automatically.
Every consequential operation is recorded as an append-only RunEvent and gated by an Approval row.
Wallet interactions are signature-only through your wallet. No seed phrases, no private keys, ever.