You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1133ad4
Browse filesBrowse the repository at this point in the historyBrowse files
feat(core,sdk,webapp): version skew protection for chat.agent sessions
Chat sessions can now be pinned to a deployment, so a conversation keeps
talking to the agent version its release shipped with, across every
turn, idle suspend and recovery. The deployment id is resolved wherever
you start the session, exactly as it is for `trigger()`, so there is no
chat-specific setup — pass `triggerConfig: { externalDeploymentId: null
}` to opt a chat out. A pinned session also follows its pin on its own:
when your app redeploys and re-pins it, the agent hands the conversation
over at the next turn boundary instead of the new pin only applying to
the next run. Set `versionSkew: "hold"` on an agent that should stay
put. If a handover lands on a deployment that is still building, the
chat reports a pending version rather than going quiet, and messages
sent meanwhile are kept. Also fixes `AgentChat` ignoring `maxDuration`,
`region` and `lockToVersion` set on its `triggerConfig`, and a chat
agent answering the same message twice after a conversation moved to a
new run.
Mono-RevId: 1c6e161b3e4f6c3e81a50a7f24d08a43b0ba0057
Chat sessions can now be pinned to a deployment, so a conversation keeps talking to the agent version its release shipped with, and follows the pin on its own when your app redeploys. Opt out with `triggerConfig: { externalDeploymentId: null }` or `versionSkew: "hold"`. Also fixes `AgentChat` ignoring `maxDuration`, `region` and `lockToVersion`, and a restored `AgentChat` session never picking up a new deployment id.
0 commit comments