Chat Test

A live chat playground that runs against the project’s current configuration — same prompts, same documents, same tools, same theme as production. There is no separate sandbox config: every change you save in the dashboard is immediately testable here, no redeploy or app rebuild needed.

Chat Test requires an active TEST-type API key. If the project has none, the page shows a “Test API Key Required” screen linking to API Keys to create one.

By default each message is independent — no conversation history is used, and nothing is saved to Conversations. Turn on the History toggle to include prior turns in the request, which is needed to test follow-up questions or anything that depends on multi-turn context; conversations still aren’t persisted.

Text and Voice

Two tabs: Text Chat and Voice Chat. The Voice tab only appears if voice is enabled for the project.

Simulating Context

Two panels let you simulate what a real app would send:

• User Context — free-form key/value pairs sent as context with each message (for example, selectedLocationId). This is the fastest way to verify context-dependent behavior — auth-gated navigation, context-required tools, screen-aware tone — without instrumenting your real app.
• SDK Auto-Context — simulates the SDK’s own built-in context fields (dateTime, timezone, platform, locale). These are not sent to the search query, only to the model.

Debug Info

Assistant replies show an expandable debug panel with the rewritten search query, matched documents, matched tools, and navigation suggestions — the same debug detail available in Conversations.

Other Controls

• Run Initial Message — manually fires the project’s configured Initial Message instruction (disabled if none is set).
• Clear Chat — resets the chat and starts a new test session.
• A Usage counter shows running cost for the session, unless your subscription hides spend.

Sub-Project Testing

Each sub-project has its own Chat Test page, scoped to that sub-project’s configuration.