Customers and sessions

You do not need to know who the customer’s agent is.

Customer grouping

customerRef is an optional opaque identifier derived from authentication your product already has. Good values are internal account or tenant IDs. Do not send names, email addresses, prompts, or task text.

app.use(agentFeedback({
  apiKey: process.env.AGENT_FEEDBACK_KEY,
  include: ["/search"],
  customerRef: req => req.user?.accountId,
}));

Session continuity

Sessions exist only when your product or MCP integration supplies a stable, application-level reference. Epode does not group requests by timing, IP address, user agent, or inferred identity. Use a session reference when your product already has a meaningful journey—such as a checkout attempt, support workflow, or research run. If no stable reference exists, leave it out and use interactions instead.

An MCP transport session is not product-session proof. MCP 2026-07-28 transport is stateless; application continuity must be explicit.

Node + ExpressInstrument selected Express JSON and HTML responses with one global middleware.

⌘I

Start here

Understand Epode

HTTP and websites

MCP

Operate

Customers and sessions

Customer grouping

Session continuity

​Customer grouping

​Session continuity

Customer grouping

Session continuity