Operate
Start here when something went wrong, or before you launch.
- Troubleshooting: a symptom, its usual cause, and the fix.
- Reading a call back: one session, by its
session_id. - Recordings: turning them on, and what you get back.
- Going to production: the checklist before real users arrive.
- Usage and limits: what is counted, and the limits that apply.
Every session has a session_id, the same string in your connect response, in
the URL Voqalize dials your brain at, and in your brain’s logs. Start every
investigation from it: Reading a call back has the
reads and the order to take them in. How long Voqalize keeps session data is on
Status and support.
From your editor
Section titled “From your editor”The session reads are tools on the MCP server, so your coding agent can list sessions, read one back and check an agent’s configuration without leaving the editor. The console shows the same sessions.
Read next
Section titled “Read next”- Troubleshooting: start from the symptom.
- Reading a call back: the record first, then the logs.
- Error codes: what a code means and whether it ended the session.