Documentation

cockpit pinned-answers

Generated reference for cockpit pinned-answers, including its syntax, options, results, and constraints from the canonical cockpit CLI source.

Applies to
CLI
WindowsmacOSLinux

Verified 2026-08-27 · v4.61.0

Markdown

Some screens and steps may differ in the latest version.

This reference is generated from the same canonical source distributed as cockpit CLI help. See Cockpit CLI for concepts and safe operating guidance.

Pin an agent answer inside a Cockpit agent task so it can be found again from a long conversation. Pins are kept per task, survive reopening the task and restarting the app, and are shown on Desktop (the pin control on each answer and the pinned-answers list above the conversation) and in the PWA (marked answers and the pinned-answers bar). Every command returns JSON and is local-only.

cockpit pinned-answers list <task-id> [--all]
cockpit pinned-answers pin <task-id> <message-id>
cockpit pinned-answers unpin <task-id> <message-id>

<task-id> is the task shown by cockpit task list; <message-id> is the id of an assistant turn. cockpit task get <task-id> returns each conversation turn with its id, and list --all returns every assistant answer of the task with its messageId, a short text preview, and whether it is pinned. Only assistant answers can be pinned; user messages and tool calls are not pinnable. Only Cockpit agent tasks have stable answer ids, so other agent types are rejected with unsupported_task.

list returns the pinned answers in pin order. Each entry carries available: true with createdAt and a text preview when the answer is still part of the conversation, or available: false when the message no longer exists (for example after the history was reset or compacted). Such a pin is never re-created and is not offered as a jump target; unpin removes it.

cockpit pinned-answers list task_abc123
{"ok":true,"data":{"taskId":"task_abc123","pinned":[{"messageId":"msg_42","available":true,"createdAt":1789000000000,"text":"The root cause is ..."}]}}

pin requires the message to exist as an assistant answer of the task and answers message_not_found otherwise. unpin succeeds even when the message is gone, so it is the way to clean up a stale pin. Both commands return the updated list data, and the change is pushed to open Desktop windows and connected PWA clients immediately. Pins are removed together with their task.

cockpit pinned-answers list task_abc123 --all
cockpit pinned-answers pin task_abc123 msg_42
cockpit pinned-answers unpin task_abc123 msg_42