## State to save

- Product user or tenant ID.
- Feature key and configured agent ID.
- Session ID and last response ID.
- Artifact records and preview state.
- Terminal status and incomplete details when available.

## Request

Send the follow-up text with `previous_response_id` and `metadata.session_id`. Use a new `Idempotency-Key` for the new follow-up request.

**Open standard**

Because a UHP session is a chain of responses, the revise flow only needs the last response id and session id you stored — the earlier turns' context comes back with the continuation. See [the Sessions chapter in the UHP spec](https://unifiedharnessprotocol.org/spec/sessions).