From 53b429b105b6719832c32e8c9ec98daa45e36e77 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Arnaud=20H=C3=A9ritier?= Date: Tue, 4 Aug 2026 04:01:50 +0000 Subject: [PATCH] docs: update for PR #3878 - feat(tui): make current session plans editable Reflects changes from docker/docker-agent#3878. Source PR: https://github.com/docker/docker-agent/pull/3878 The TUI now supports editing session plan bodies via the 'e' key in the /plans browser and detail view. Session plans were previously described as read-only from the host, but now the plan body can be edited (while status and delete operations remain unsupported). --- docs/tools/session_plan/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tools/session_plan/index.md b/docs/tools/session_plan/index.md index ad186a199..ea4c8e497 100644 --- a/docs/tools/session_plan/index.md +++ b/docs/tools/session_plan/index.md @@ -81,7 +81,7 @@ Embedders that render the plan inline can subscribe and update without re-readin A session plan belongs to its session: hosts can read and export it, never change it. - **CLI** — the [`docker agent plans`](../../features/cli/index.md#docker-agent-plans) command group lists, reads (`get --session `), and exports session plans alongside shared plans. Mutations (`update`, `status`, `delete`) are refused with an `unsupported` error explaining the ownership rule. -- **TUI** — the `/plans` browser (see the [plan toolset docs](../plan/index.md#the-plans-browser-in-the-tui) for the full keybinding table) includes the **current session's** plan as the `session` scope row; plans of other sessions are never enumerated. Its identity is the session ID and its version column shows `-` — session plans have no versions. Enter opens the read-only detail (scope, session ID, update time, scrollable markdown) and x exports to `session-plan-.md` in the working directory (refusing to overwrite an existing file). Status, edit, and delete visibly report that session plans don't support them instead of attempting the write. The browser refreshes live on the `session_plan_updated` event, so a plan the agent just wrote appears without reopening. +- **TUI** — the `/plans` browser (see the [plan toolset docs](../plan/index.md#the-plans-browser-in-the-tui) for the full keybinding table) includes the **current session's** plan as the `session` scope row; plans of other sessions are never enumerated. Its identity is the session ID and its version column shows `-` — session plans have no versions. Enter opens the detail view (scope, session ID, update time, scrollable markdown) and x exports to `session-plan-.md` in the working directory (refusing to overwrite an existing file). e opens the plan body in your external editor (`$VISUAL` or `$EDITOR`) for editing — the write is unguarded and last-write-wins by design. Status and delete visibly report that session plans don't support them (session plans belong to their session and carry no shared-plan metadata). The browser refreshes live on the `session_plan_updated` event, so a plan the agent just wrote appears without reopening. ## Example