Verifying changes in Honcho

Prerequisites

Docker Compose is the preferred way to run the stack — docker-compose.yml at the repo root brings up Postgres (pgvector), Redis, the API server, and the deriver worker together. If Docker Compose isn't available, the stack can also run directly on the host (see Launch below); you'll need Postgres with pgvector and Redis reachable, plus a .env with connection strings and an LLM provider key for any flow that hits a model (deriver, dialectic, dreamer).

Working in a worktree? It carries neither .env nor node_modules. Copy .env from the main checkout (that's where the provider keys live), and run bun install in sdks/typescript if you'll run the full test suite — otherwise the pre-push gate fails on a phantom Cannot find package 'zod'.

Launch

First check whether the stack is already running via Docker Compose: