From 6bfc3debf57d2ab5b5873f572d8d6e93de759a22 Mon Sep 17 00:00:00 2001 From: Toray Altas <6816042+taltas@users.noreply.github.com> Date: Tue, 21 Jul 2026 14:52:17 +0000 Subject: [PATCH] docs: update per-task profile persistence resume behavior --- docs/features/api-configuration-profiles.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/api-configuration-profiles.mdx b/docs/features/api-configuration-profiles.mdx index 4cd96226..e7f23f94 100644 --- a/docs/features/api-configuration-profiles.mdx +++ b/docs/features/api-configuration-profiles.mdx @@ -123,7 +123,7 @@ In the Prompts tab, you can explicitly associate a s Each task remembers which profile it started with. This "sticky" behavior means: -- **Reopening from history**: When you resume a task from history, it uses the same profile it had originally—even if you've since changed the global selection. +- **Reopening from history**: When you resume a task from history, it honors your current global profile selection. If you've switched profiles since the task was last saved (for example, to a provider with a larger context window), the resumed task uses the newly selected profile and remembers it going forward. - **Multi-workspace consistency**: If you switch profiles in another workspace window, existing tasks in the first window keep their original profile. - **Orchestrator subtasks**: Child tasks created by the orchestrator inherit the parent's profile and retain it for their lifetime.