> ## Documentation Index
> Fetch the complete documentation index at: https://docs.subconscious.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Request correlation

> Group requests into conversations and label your client in usage views, so multi-turn traffic is readable turn by turn.

Our gateway groups requests from the same session into a conversation. A conversation shows its indidvidual requests, tokens, background tokens, tool calls, and a context-over-time chart. The conversation page shows off the benefits of our context-compression.

![Conversation dashboard showing turns, tokens, background tokens, trace time, tool calls, and a context-over-time chart for one session](https://mintcdn.com/subconscious/iEX0mGdicHxQ4XNa/images/session-context-over-time.png?fit=max\&auto=format\&n=iEX0mGdicHxQ4XNa\&q=85\&s=0b62daf9027db01c5378ab78af616afd)

Context growth for a single session in the conversations page. Session affinity keeps follow-up requests on the worker that holds the conversation's KV cache, so cached context accumulates instead of being re-sent.

Send one stable session value per conversation, either in a header or in the body. The gateway accepts several forms, listed in [Session affinity](https://docs.subconscious.dev/features/session-affinity.md#identify-your-session) with the resolution order between them.

## Name your client

Send `x-subconscious-client` to label your traffic in usage views:

```
x-subconscious-client: my-agent
```

Any value works. The value becomes the agent label shown next to your conversations. Labels are lowercased, separators are collapsed to hyphens, and the stored label is at most 64 characters. For example, `My Agent!` shows as `my-agent`.

A present `x-subconscious-client` is the only way a request carrying generic session signals (the body session id, `x-session-id`, or `x-session-affinity`) gets a label.

The client header is terminal: when it is present, its value is the label, regardless of what other signals suggest.

## Conversations without a session signal

A request that sends no session signal still gets a conversation. The gateway hashes the assistant turns it served and matches them against the history the request sends back, so the conversation is derived from the conversation itself. Read [Sessions without a session signal](https://docs.subconscious.dev/features/session-affinity.md#sessions-without-a-session-signal) for the mechanism.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.