Skip to main content

Use Vox chats, history, and cancellation

Selecting + New chat resets the composer and opens the empty Vox route. It does not immediately create a database thread. The thread is created only when you send the first message, which prevents unused chats from filling the history sidebar.

After the first send, the URL includes the workspace and thread ID:

/w/{workspaceId}/vox/{threadId}

The thread belongs to the current user in the active workspace. Its initial title is derived from the first message and shortened to at most 64 characters.

History boundaries​

  • The sidebar returns up to 100 used threads.
  • A thread can contain up to 200 total messages.
  • A user message can contain up to 12,000 characters.
  • The current interface does not expose rename, archive, or delete controls for Vox threads.
  • Switching workspaces clears the current Vox state and cancels the active browser request.

The full thread may be stored, but each response uses only a bounded recent context selected for that request mode.

Compose and send​

Press Enter to send and Shift+Enter for a new line. While Vox is working, the send button becomes a red stop control. Progress text reports relevant reads, searches, and viewed sources. The final response is revealed progressively, while the underlying response is already complete.

What Stop guarantees​

Stop cancels the browser request and restores the composer when possible. Cancellation is best-effort: server-side analysis, persistence, credit settlement, or an already-started external read may finish before the abort is observed. Stop does not reverse an action you separately approved.