Patch Changes
-
5714397: Add a Memory toggle to the agent builder, shown once the tenant has a memory provider. In OSS, admins configure Zep in Settings → Memory (
/api/v1/settings/memory-providers); in TrueFoundry mode it comes fromTRUEFOUNDRY_MEMORY_*env. A tenant-wide memory switch, off by default, gates memory in chats, ingestion, and agent specs. -
475c0c2: Add POST
/api/internal/sessions/{session_id}/turns(service API key): non-streaming body, getSessionById, requires external_id + non-null source (skips memory ingest), SessionSourceservicearm. -
1998de5: Turns now pause, instead of finishing, while waiting for user input such as tool approvals, questions, or MCP authentication. The same turn resumes once every required interaction is answered. Clients send those answers as events on the paused turn and can reconnect to its event stream at any point.
- While a turn is paused, its cost and time so far stay visible. Time spent waiting on the user does not count. Cancelling a paused turn still shows its final cost and time.
- Conversations that were already waiting on the user stay waiting after upgrade, with the same cost, time, and status.
- The chat shows a waiting notice instead of a running indicator while a turn is paused or cannot continue.
- A conversation is saved to memory only after it finishes, not while it is waiting on the user.
- Creating a turn requires a user message. Omitting
inputor sending an empty message is rejected. - Sending a new message while a sub-agent is waiting runs that message, instead of leaving the turn stuck.
- A conversation paused longer than the memory window is still saved once it finishes.
- An old
pause_timeout_msmemory setting is ignored, instead of stopping startup.
Breaking changes for package consumers:
@truefoundry/trueforge-assistant-ui-runtime:useTrueForgeResumeMcpAuthis renamed touseTrueForgeContinueMcpAuth, andfindCurrentPausedAssistantMessagetofindPausedAssistantMessage.collectRequiredActionInputs,collectApprovalInputs,toTrueForgeApprovalInputs,collectResponseInputs, andTOOL_RESPONSE_THREAD_ID_CUSTOM_KEYare removed; answer approvals and questions withuseTrueForgeRespondToToolApprovalanduseTrueForgeRespondToToolResponseinstead.- Custom chat servers must implement
sendTurnEventsto deliver answers to a paused turn.CreateTurnRequest.inputis required. @truefoundry/trueforge-ui:ToolApprovalContainertakesapprovalIdandonRespondinstead ofoptionsandonSelectOption.
-
8ef66cc: Replace the session sharing capability's enabled flag with required tenant or subject granularity across the API and UI contracts, and use subject granularity to enable user invitations.