Work in the chat workspace

Start and continue threads

1. Open a new thread.
2. Select Auto for policy-based routing or choose an exact live catalog model.
3. Optionally choose Search, Think, or Canvas, then send the prompt.
4. Wait for streaming to complete and verify the answer, requested model label, and any available cost, latency, or citation details.

Use copy, retry, or regenerate when you want a fresh answer. Editing an earlier message creates a fork; use the branch controls to move between sibling paths without rewriting the original history.

Compare two to four models

1. Open the Compare workspace.
2. Select two to four models, enter one prompt, and start the run.
3. Inspect each independent stream, citation set, cost, and latency; stop an individual column if needed.
4. Export the comparison as JSON or continue the chosen result into its own thread.

Organize work in a Space

1. Open Spaces and create a Space.
2. Set its name, description, system prompt, and default model.
3. Start a thread from that Space and confirm the default model and Space instructions are applied.
4. Return to the Space to filter its threads, review citations, or pin available asset metadata.

Space instructions take precedence over account-level custom instructions for a thread inside that Space.

Share a frozen snapshot

1. Open the thread you want to publish and choose Share.
2. Copy the generated unguessable public URL and open it in a signed-out window to verify the read-only view.
3. Share that URL only with the intended audience. Later edits to the source thread do not silently rewrite the frozen snapshot; create a new share when the published content must change.

A signed-in reader can fork a shared snapshot into their own account.

Find and maintain prior work

Use the Library to search and filter threads by archive state, model, Space, date, citations, or tags. Select rows for bulk archive, restore, move, tag, or delete actions; use CSV export when you need an offline inventory.

Understand app modes

Search, Think, and Canvas are Singular app instructions layered onto the request, not universal provider APIs. Search can render citations when supplied, Think requests a reasoning-oriented presentation, and Canvas requests artifact-oriented HTML or code. Do not infer that every catalog model implements a native tool merely because a mode is selectable.

Product/API boundary

The browser talks to internal /api/web/* backend-for-frontend routes. Those routes are not a public developer API or compatibility promise. Programmatic integrations must use the canonical Singular API origin documented in the quickstart.