For: everyone. All three roles hit this, and it happens in all three channels. Causes 5 and 6 only apply if you use MCP.
A playbook you can see in the webapp is missing from the extension, from Chat or from your MCP tool. Almost always it is one of the following, and they are listed in the order in which they actually happen rather than in order of how interesting they are.
1. You are in a different workspace
A playbook belongs to exactly one workspace. If you have more than one, the extension or the MCP connection may be pointed at a different one than the browser tab you are looking at. Switch workspaces in the sidebar and check whether the playbook is where you think it is.
2. The playbook is not published
An unpublished playbook is a draft. It stays visible to you in the webapp, and the extension does not show it at all — the extension only ever reads published ones. This is the single most common cause, because the webapp gives you no reason to notice the difference while you are editing.
3. Its access is restricted
Every playbook is in one of three states, and the card in the playbook list tells you which by carrying a badge:
No badge — open to everyone in the workspace.
Restricted — only the people and groups named on it, plus whoever created it.
Only me — the creator and nobody else. Not editors, and not admins either. That surprises people who assume an admin sees everything; here the promise to one person wins.
Being an admin or an editor does not grant access to a playbook on its own. Access is the creator plus whoever is explicitly named.
4. A persona is missing one of its steps
This is the quiet one. A persona's routes are always filtered against your rights, never against the rights of the person who built it. So a persona shared with the whole team can carry a route to a playbook that is restricted to its author — and you receive the persona without that route, with no error and no gap where it used to be.
That behaviour is deliberate: attaching a playbook to a persona must never widen who can read it, or building a persona would quietly become a way to hand out permissions. If a persona seems to skip a step it should be doing, ask its author whether the playbook behind that step is restricted.
5. The MCP connection belongs to someone else
Every MCP connection belongs to exactly one person, and the server shows that person's playbooks — not the workspace's. If you are using a connection string a colleague sent you, you are seeing what they can see. Create your own under Settings → MCP Server; every role may hold one, including members.
6. The MCP connection has gone dormant
A connection that has not been used for 90 days is refused rather than deleted. If a tool that worked months ago suddenly returns nothing, this is a likely cause. The quickest way out is a new connection under Settings → MCP Server.
7. You are looking for the wrong thing in the wrong channel
Two limits that are easy to mistake for bugs. Personas do not appear in the browser extension — they work in sqemes Chat and over MCP. And skills need extension version 2.6.6 or newer; on an older install the extension simply does not know that kind exists. Check your version in Chrome before looking any further.
Narrowing it down in a minute
Open the playbook in the webapp. Is it published, and which badge does its card carry?
Check that the workspace name at the top matches the one your other tool is connected to.
Ask a colleague to look for the same playbook. If they can see it and you cannot, it is access. If neither of you can, it is publishing or the channel.
If none of these fits, the playbook is genuinely missing rather than hidden, and that is worth reporting.
Updated 27 September 2026 · Article version 1