@ammduncan/easel 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to easel. This project adheres to [Semantic Versioning](https://semver.org/).
 
+## 0.6.1 — 2026-06-04
+
+### Changed
+- **The "different session" push hint now requires the surface-the-tab question to be asked ALONE.** When a push lands while easel is open on another session, the tool result tells the agent to ask the user whether to (a) switch the open tab or (b) open a fresh one. Agents were bundling that question into a multi-question prompt alongside follow-ups that assumed the user had already *seen* the pushed content — which they hadn't, since the tab wasn't surfaced yet. The hint now spells it out: ask this one question first, by itself; once the tab is visible, ask the rest. Prompt-text only; no runtime change.
+
 ## 0.6.0 — 2026-06-03
 
 ### Fixed

package/dist/mcp.js

@@ -314,7 +314,7 @@ export async function main() {
         }
         else if (openResult.kind === "other-session") {
             tabHint =
-                " · easel is open in another tab, but on a DIFFERENT session — so this push isn't visible yet. ASK THE USER how to surface it, and if your client has an interactive question/prompt tool (e.g. AskUserQuestion), USE IT to offer the choice as clickable options rather than burying it in prose: (a) switch the open tab to this session via the topbar 'switch ▾' dropdown, or (b) have you call the `open` tool to launch a fresh tab. Do not auto-open or pick for them.";
+                " · easel is open in another tab, but on a DIFFERENT session — so this push isn't visible yet. ASK THE USER how to surface it, and if your client has an interactive question/prompt tool (e.g. AskUserQuestion), USE IT to offer the choice as clickable options rather than burying it in prose: (a) switch the open tab to this session via the topbar 'switch ▾' dropdown, or (b) have you call the `open` tool to launch a fresh tab. Do not auto-open or pick for them. This question MUST be asked ALONE — never bundle it with other questions in the same prompt call. Any other question you'd ask alongside it almost certainly assumes the user has already seen the pushed content, which they haven't until they surface the tab. Ask this one first, by itself; once the tab is visible, ask the rest.";
         }
         else if (result.sessionTabs === 0) {
             tabHint =

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ammduncan/easel",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "A live browser tab for every Claude Code (and MCP) session. The push MCP tool appends HTML cards to a scrolling feed you keep open in split-screen.",
   "type": "module",
   "license": "MIT",