smoke-test

name

smoke-test

description

Run and interpret scripts/smoke_test.sh, the on-demand checks for optional dependencies that CI and the default docker compose don't cover: the Postgres and MongoDB checkpointers, the AG-UI endpoint, and LangFuse tracing. Use when you've touched the memory/checkpointer layer, service startup/health, the AG-UI adapter, LangFuse tracing, or bumped one of those dependencies — and want to confirm the real integration still works without waiting for a full CI run. Also use when deciding WHETHER such a check is even warranted for a change.

Optional-dependency smoke tests

scripts/smoke_test.sh exercises the parts of this project that aren't in the fast unit suite or the default CI path because they need real infrastructure: the Postgres and MongoDB checkpointers, the AG-UI endpoint, and LangFuse tracing. It spins up the real dependency in Docker, runs the service against it, and verifies the integration end-to-end, then tears everything down.

"Smoke test" here means a quick is-this-obviously-broken confidence check, not exhaustive integration coverage. It's deliberately cheap to run one target and skip the rest.

First: should you run this at all?

Most changes do not need it. It pulls images, starts containers, and takes minutes — that time and token cost isn't worth it for work that doesn't touch these paths. Skip it for: adding or editing an agent graph, prompts, or tools; docs; client/Streamlit-only changes; anything already covered by uv run pytest and normal CI.

Run the relevant target when your change touches its path:

You changed…	Run
src/memory/*, initialize_database, a saver/store class, checkpointer wiring	postgres and/or