threads

Overview ¶

threads demonstrates persistent, resume-only, and forked conversation Threads on host-owned keys.

The SDK keeps exactly two consumer-visible identity layers: the thread key (the host's own business string) and the run ID. The provider session id is demoted to an audit detail reachable through th.Checkpoint(ctx).

Usage:

go run ./examples/threads -agent=codex -key=support/issue-42