Skip to main content
Binding is how one session owns an artifact — a pull request, Slack thread, Linear issue — so follow-up events fold into the same conversational memory instead of spawning duplicates. See routing for when to use bind versus deliver, and triggers and events for bind-at-spawn and folding mechanics. The chat assistant pattern is the canonical spawn/deliver split around a thread binding:
Reach for binding when follow-ups need context: a conversation, a PR that accumulates review feedback, an issue with a back-and-forth. Chat assistant is the purest demonstration; handoff applies it to PR ownership, and code review uses bind with onUnmatched: spawn so one reviewer session owns a PR across pushes instead of spawning a fresh review per head. Agents can also bind and release targets at runtime with auto.bind and auto.unbind. Session bindings are durable until explicitly released — see sessions.