Session management
Chat sessions persist your conversations with the agent. Each session keeps its own message history, action log, and trace data.
Session lifecycle
| Action | Endpoint |
|---|---|
| Create | POST /pfw/v1/chat-sessions |
| List | GET /pfw/v1/chat-sessions |
| Get | GET /pfw/v1/chat-sessions/{id} |
| Rename | PATCH /pfw/v1/chat-sessions/{id} |
| Delete | DELETE /pfw/v1/chat-sessions/{id} (cascades to messages, actions, traces) |
| Purge | POST /pfw/v1/chat-sessions/purge (sessions older than N days, default 7) |
Session data
- Label — your name for the session (max 190 chars).
- Owner — the WordPress user who created it.
- Workflow (optional) — an associated workflow for context.
- Messages — user prompts and assistant responses in order.
- Actions — every action the agent proposed with arguments and outcome.
- Traces — timing, tokens, cost, and outcome per turn.
Access control
By default only the session owner can read or modify a session. Site builders can broaden this — e.g. allow administrators to read any session, or share sessions across a team — through the documented access-control extension point.
Secret redaction
Anything that looks like an API key (e.g. sk-…, sk-ant-…) is automatically redacted from stored messages and traces. You can paste a key into a chat to ask "is this format correct?" without the literal value being persisted anywhere on disk.