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. A regenerated answer is added as a branch sibling instead of replacing the previous one, so both attempts stay reachable. Editing an earlier message creates a fork; use the branch controls to move between sibling paths without rewriting the original history.

Attach files and images

1. Use the composer attachment control, or drag files onto the composer, to add up to 4 files per message at up to 3.5MB each.
2. Accepted types are PNG, JPEG, WebP, and GIF images, PDF documents, and plain text, Markdown, or CSV files.
3. Send the message. Attachments are stored in tenant-scoped storage and their contents are sent to model inference.

Images are delivered to the model as image content parts. With Auto selected, a vision-capable model is chosen for you. If you pin a text-only model and attach an image, the provider can reject the request, and that rejection surfaces as an ordinary thread error. PDF and text files have their text extracted on the server and shared with the assistant; a long document is truncated before it reaches the prompt.

Record a voice note

The microphone control records up to 90 seconds of real audio, converts it to WAV in the browser, and sends it as audio input. Audio prompts are answered by an audio-capable catalog model, and the recording is stored with the message so it stays playable after a reload. A browser without microphone support reports an error rather than recording silently.

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.

Stopping a column is a terminal user action: if no response arrived, that column is shown as stopped with an explicit no-response message, while the other columns remain available.

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 add files.

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

The Add file control uploads and stores the real file. Pinning decides whether it reaches the model: a pinned text or PDF file has its contents joined to the Space context of every thread in that Space, and a pinned image is visible to vision-capable models. A stored file that is not pinned stays available for reference and is not injected into any thread.

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.

Render rich responses

Assistant Markdown is rendered as sanitized GitHub-Flavored Markdown. Headings, emphasis, links, quotes, tables, and fenced syntax-highlighted code blocks are supported; code blocks and tables include copy controls.

Provider responses can opt into Singular's chart and media renderers with the documented chart and media fences. Charts render as bounded bar or line visualizations. Media responses can expose a variation strip, download control, regenerate control, and an image lightbox. Regenerate re-runs the source prompt and delivers the new response as a branch sibling, so the earlier result stays reachable through the branch controls and each regeneration is a fresh billed request.

Citation chips appear only when the response includes citation metadata. A selectable Search or Canvas mode does not guarantee citations, live browsing, or a native provider tool.

Authored Markdown images are lazy-loaded and contained within the conversation layout (maximum 320px height) so a large remote SVG cannot take over the viewport. That containment is a presentation guard and is separate from attachments: an image referenced by Markdown is a link, while a file added through the composer is uploaded and its bytes are sent to model inference. See Limitations for the remaining attachment boundaries.

Manage your account

Account-wide controls live under Settings → Profile.

Export all data downloads a JSON file immediately. It enumerates your profile, linked account providers, threads with their messages, Spaces, artifacts, asset metadata, tags, settings, API key metadata, masked provider-credential references, and a billing snapshot. Asset file bytes are excluded; download those files individually where they are attached. There is no ZIP archive and no emailed delivery.

Delete account is immediate and irreversible. Deletion revokes your API access and removes your stored data before the sign-in identity is removed, so keys issued under the account stop working as part of the same action. Export first if you want a copy.

Liking an assistant message saves that state to your account, so likes survive a reload and are present when you sign in from another device.

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.