insight-chat: document the new system_prompt field in CLAUDE.md
Add system_prompt to the /insights/chat body schema with a one-paragraph note on the append-vs-amend semantics so future readers find the contract alongside the rest of the chat-continuation docs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -658,7 +658,12 @@ clients whether chat is available for a given insight.
|
|||||||
|
|
||||||
- `POST /insights/chat` runs one turn of the agentic loop against the replayed
|
- `POST /insights/chat` runs one turn of the agentic loop against the replayed
|
||||||
history. Body: `{ file_path, library?, user_message, model?, backend?, num_ctx?,
|
history. Body: `{ file_path, library?, user_message, model?, backend?, num_ctx?,
|
||||||
temperature?, top_p?, top_k?, min_p?, max_iterations?, amend? }`.
|
temperature?, top_p?, top_k?, min_p?, max_iterations?, system_prompt?, amend? }`.
|
||||||
|
`system_prompt` is a per-turn override: in append mode (default) it's applied
|
||||||
|
ephemerally — the original system message is restored before persistence so
|
||||||
|
the stored transcript keeps its baked persona. In amend mode the override
|
||||||
|
stays in place and becomes the new insight row's system message. Mirrors the
|
||||||
|
internal `annotate_system_with_budget` swap-and-restore pattern.
|
||||||
- `POST /insights/chat/stream` is the SSE variant — same request body, response
|
- `POST /insights/chat/stream` is the SSE variant — same request body, response
|
||||||
is `text/event-stream` with events: `iteration_start`, `text` (delta), `tool_call`,
|
is `text/event-stream` with events: `iteration_start`, `text` (delta), `tool_call`,
|
||||||
`tool_result`, `truncated`, `done`, plus a server-emitted `error_message` on
|
`tool_result`, `truncated`, `done`, plus a server-emitted `error_message` on
|
||||||
|
|||||||
Reference in New Issue
Block a user