Pasted a Sume thread link and landed on New Agent? Workspace
A Sume thread stamped with another workspace answers 404 workspace_mismatch and the app redirects to New Agent. Switch workspace, then reopen the link.
If a Sume thread link sends you to a blank New Agent page, you are probably in the wrong workspace. Personal and Team are separate partitions. A thread stamped with a workspace you are not currently in returns 404 workspace_mismatch, and the web app redirects to New Agent instead of showing an error. Switch workspace and open the link again.
Two partitions, not one list
Since the 2026-08-02 decision, the active workspace is the partition key for every workspace-scoped list: threads, Products, Actions and Skills. Personal lists rows where workspace_id is null. A team lists rows where workspace_id equals the organization id. Switching between them is meant to feel like switching accounts.
Why it redirects
The thread endpoint checks the stamp after access. The client treats the workspace_mismatch status specially: it replaces the route with the New Agent page. This covers pasted URLs, bookmarks, and tabs whose Clerk session changed in another window, which the workspace switcher's own reset cannot reach.
What stays true across the switch
- Billing follows the thread's stamp. An org-stamped thread still bills the team wallet, even if it is opened from a personal session, so a footer and an error cannot disagree about whose wallet pays.
- Inside the correct team workspace, any member can read the thread. Writing and running still need Creator or Admin.
- Public share links are a different feature: a tokenized URL, not workspace membership.
Checklist when a link fails
Check which workspace the sender was in. Switch to it from the workspace switcher. If you were never added to that team, you will not have access, and an Admin needs to invite you. If you are building your own client, do not retry a workspace_mismatch; it will not change until the active workspace does. Older threads created while a team was forced on are not backfilled to Personal, so they stay under Team.
Lists versus agent tools
The partition applies to the lists you browse. Some callers have no workspace context, such as agent tools, action runs and dashboard overview reads, and these keep the older behavior of returning every row the owner owns across both partitions. That difference is deliberate: null means resolved Personal, while an omitted workspace means owner-wide. If a thread appears in a tool result but not in your Home list, this is why, and switching workspace will show it in its own partition.
One more symptom is worth naming: the footer or an error mentioning the team wallet while you believe you are in Personal. Because billing follows the thread stamp rather than the screen you are on, that message comes from the thread, and switching to the matching workspace makes the footer agree. Also remember that direct jobs read through the jobs API follow the job's thread, not its owner, so a teammate who can open the thread can read the job.
Related posts
More in Agents
- tts_create dry_run will not warn about a voice-language mismatch
A cost-only dry_run on Sume's tts_create stays a preview; the language double-check runs on submission. How to preflight voice, language and cost together.
- tts_source_get and verify_spine: check a voiceover vs its script
Sume's hosted MCP has two free read tools for voiceover work. One returns the accepted script for tts_create, the other compares chosen TTS jobs to it.
- Use a saved workspace voice in Sume chat: @ mention it in the turn
Tag a saved voice with @ in a Sume chat turn and the agent prefers that voice for speech. Here is what it reads from the voice and what a mismatch looks like.
- voices_create persona: 20 characters minimum, one variant in chat
To invent a Sume voice from words, voices_create needs a persona of 20+ characters or invent:true. Chat makes one variant by default, three only if you ask.
Written by Sume