@usercase/mcp 0.2.2-next.1 → 0.2.2-next.2

package/agents/focus.md

@@ -17,6 +17,10 @@ Split how they arrive, about half and half:
 
 If the focus is only reachable when signed in, everyone is a member — this replaces "keep some as newcomers". Add newcomers only if the user asks for them (to see the sign-in wall). And cast the members to fit what the account has really done: if the user did not say a demo account already joined the room or saved the item, do not write people who are "already in the room" or "checking their saved list" — write people who join, save or start there on this visit.
 
+Write the focus into the goal itself, including the step it takes to get in: if reading or writing in it needs joining, saving or signing up first, the goal says the person means to do that if it looks worthwhile ("see what the holders are saying, and join and say hello if it looks lively") — not only "look whether there are posts", which ends at the first Join button. Mention the focused action itself (e.g. the chat), not just the area around it.
+
+A second thing on their mind stays inside the focus or leads into it (reading the chat and then the room's notices; a news card that sends them looking for the room) — never another part of the site (the calendar, the price list). Here that would be an easy way out of the focus, and the run would lose the visit.
+
 Do not add people who have nothing to do with the focus. In later rounds, cast new people for the same focus.
 
 **Step 4 — unchanged.** The visitors are never told about the focus.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usercase/mcp",
-  "version": "0.2.2-next.1",
+  "version": "0.2.2-next.2",
   "description": "Virtual users that browse your website and tell you what they thought — an MCP server for Claude Code",
   "license": "UNLICENSED",
   "homepage": "https://usercase.io",