Phantom Router Playground

Connection

Phantom Router API base URLAPI keyNeeds the chat:companion scope — mint one in the Phantom Router admin console (tick chat:debug for the memory view).

Not connected

Vector store

No vector store configured. Phantom Router chat needs one — configure an Upstash Vector index.

Turn options

Chat idThe memory partition. Keep it fixed to build up memory; change it to start fresh.Model overrideBlank → server default (COMPANION_DEFAULT_MODEL).TemperatureSampling temperature for the chat reply (0–2). Default 0.8.Max tokensCap on tokens generated for the chat reply (1–32000).Buffer window (messages)Only the last N messages are sent each turn — memory covers older context. 0 = send the whole buffer (API caps at 100). A short window is ideal for testing recall; it only pauses write-back of NEW memories (existing ones are still retrieved).Extract memoryAsync write-back (cadence-gated)Debug blockReturn retrieved memories, scores, profile, prompt

Persona

Stateless free-text — sent on every turn. No history is stored.

Name *Chat styleSlots into “You are {name}, the user's {chat_style}.”BioAppended to the system prompt as backstory.System promptIf set, REPLACES the generated preamble (chat_style is then ignored).GreetingValidated but currently informational — not injected into the prompt.

💬 Chat0 user turns

Connect to a Phantom Router API first (top-left).

Send a turn to inspect the request, response, and memory pipeline.