company logo

sqemes Help Center

Go to sqemes Web App
All collectionsFirst stepsWhere will I actually use my playbooks — browser, Chat, or MCP?

Where will I actually use my playbooks — browser, Chat, or MCP?

Three channels, and you do not have to pick just one. What each is good at, what each costs you, and the two limits that decide it for some teams.

For: everyone. The choice is an admin's during setup, but everybody needs to know which one their team picked — it decides where you go looking.

This is the one decision in sqemes that shapes everything else. You can pick more than one, and you can change your mind later; nothing is locked in.

In your browser — the extension

Your playbooks appear inside ChatGPT, Claude and Gemini. You keep working exactly where you work now; sqemes adds a shelf next to the input box.

Good for teams who already live in one of those tools and are not going to move. It has the lowest friction of the three, and nobody has to learn a new place.

The costs. It is a Chrome extension, so everyone needs Chrome and needs to install it. The AI is whatever that site gives you — sqemes contributes the playbook, not the model. And personas do not work here; the extension serves playbooks only.

In sqemes Chat

A chat in the webapp itself, using an AI provider you connect or the credits in your plan.

Good for teams who want one place where everything is together: playbooks, personas, files and connectors, with nothing to install.

The costs. It is a new habit — somebody used to ChatGPT has to remember to come here instead. And it needs either plan credits or a provider key before it does anything at all.

In Claude Code, Cursor and Codex — MCP

Your playbooks and personas become tools inside any client that speaks MCP: Claude Code, Claude Desktop, Cursor, VS Code, Codex and others.

Good for developers and anyone whose real work already happens in such a tool. It is the most capable of the three: the client can search your playbooks and pull the right one in mid-task, without anybody clicking.

The costs. Every person sets up their own connection, and connections are per person on purpose — one shows that person's playbooks, not the workspace's. There is a config step in the other tool, which is a small hurdle for non-technical colleagues.

Two limits worth knowing before you choose

  • Personas work in Chat and over MCP, not in the extension. If personas are the reason you are here, the browser alone will not do.

  • Skills need extension version 2.6.6 or newer. An older install shows prompts and silently knows nothing about skills.

A reasonable default

If you genuinely do not know: pick the channel your team already spends its day in, and add a second one only when somebody asks for it. Setting up all three at once means three things to explain on day one, and the usual result is that none of them gets used.

You can add a channel at any time from Settings; the wizard is just the first pass.

Updated 27 September 2026 · Article version 1

Did this answer your question?
😞
😐
😁