Expand description
Canonical text-transcript rendering for pond_search / pond_get_session /
pond_get_message
responses, shared by the MCP transport and the pond CLI so both surfaces
emit one identical readable format (spec.md#protocol). The structured
HTTP/JSON path renders nothing here; this is the plain-text view.
Enums§
- Surface
- Which surface a transcript renders for. The format is identical; only the
follow-up vocabulary differs - the MCP tools are
pond_get_session/pond_get_message/pond_sqlwithkey=valueargs, the CLI verbs arepond get-session <ID>/pond get-message <ID>/pond sql. Without this a human at the terminal is told to run tool syntax their shell rejects.
Functions§
- render_
get_ transcript - render_
search_ transcript - render_
subagents_ footer - Footer for a
pond_get_sessionresponse listing the session’s spawn-only subagents. Each subagent is its own session (spec.md#datasets) addressable by the printed id, so the caller can open any withpond_get_session; without this they are invisible from the MCP surface.