@somacheck/vibecheck 0.6.5 → 0.6.6

package/README.md

@@ -9,7 +9,7 @@ Your agent has your context. It does not have your gut. This is the bridge.
 
 Fair. Here is what you need, without executing anything.
 
-**What the `link` command does.** `npx -y @somacheck/vibecheck@0.6.5 link <CODE> --client <CLIENT>`
+**What the `link` command does.** `npx -y @somacheck/vibecheck@0.6.6 link <CODE> --client <CLIENT>`
 exchanges a short-lived pairing code, generated inside the SomaCheck iOS app, for
 a bearer token. It writes that token to `~/.sensie/config.json` with mode `0600`,
 offers to configure supported agent clients found on the computer, and checks the
@@ -81,9 +81,9 @@ before the pairing code is redeemed.
 To configure or repair a client later:
 
 ```text
-npx -y @somacheck/vibecheck@0.6.5 setup codex
-npx -y @somacheck/vibecheck@0.6.5 setup claude
-npx -y @somacheck/vibecheck@0.6.5 doctor
+npx -y @somacheck/vibecheck@0.6.6 setup codex
+npx -y @somacheck/vibecheck@0.6.6 setup claude
+npx -y @somacheck/vibecheck@0.6.6 doctor
 ```
 
 Manual registration remains available:
@@ -93,13 +93,13 @@ Manual registration remains available:
      "mcpServers": {
        "vibecheck": {
          "command": "npx",
-        "args": ["-y", "@somacheck/vibecheck@0.6.5", "serve", "--client", "codex"]
+        "args": ["-y", "@somacheck/vibecheck@0.6.6", "serve", "--client", "codex"]
        }
      }
    }
    ```
 
-   For Claude Code: `claude mcp add --scope user vibecheck -- npx -y @somacheck/vibecheck@0.6.5 serve --client claude`
+   For Claude Code: `claude mcp add --scope user vibecheck -- npx -y @somacheck/vibecheck@0.6.6 serve --client claude`
 
 The link step writes only the bearer token in `~/.sensie/config.json`. The client
 setup step asks Codex or Claude to add the pinned MCP command to that client's own
@@ -110,15 +110,15 @@ If `doctor` reports another MCP server named `somacheck`, that is the legacy
 hosted connector and is separate from this local package. The setup command
 will explain it and leave it alone. The canonical local MCP key is `vibecheck`.
 
-## Teach your agent when to offer a check-in
+## Teach your agent when to use SomaCheck
 
-[`SKILL.md`](SKILL.md) teaches compatible agents two behaviors: act immediately
-when the person explicitly requests a vibecheck, and offer one optional
-vibecheck when work drifts, a consequential decision is imminent, or recent
-messages show multiple stress signals. It uses `request_vibecheck`, not the
-reflection-feed batch tool. It includes transcript-grounded heuristics,
-statement templates, a two-hour decline cooldown, privacy rules, and the
-requirement to treat every result as context rather than authorization.
+[`SKILL.md`](SKILL.md) teaches compatible agents one simple affordance:
+SomaCheck lets them ask their person for a vibecheck. The agent can offer one
+when it believes the read would help, or send one when the person asks. The
+skill keeps only the essential boundaries: ask the person, choose a useful
+first-person statement from available context, treat the returned gesture and
+optional feedback as context rather than authorization, and never include
+secrets or assess anyone else.
 
 For Claude Code, add this repository as a marketplace and install the skill in
 one terminal command:
@@ -156,31 +156,11 @@ The skill expects the `@somacheck/vibecheck` MCP server to already be linked as
 
 ## How to use it well
 
-Ask when you genuinely need a read you cannot infer — not to check in. A good
-prompt is **a statement for the person to test**, not a question about facts:
-“I feel more concerned about the launch than the roadmap suggests.” Offer it as
-something to test, never as a claim about them. An `unaligned` result is another
-signal to consider; the person decides whether it matches what they notice.
-
-Setup and linking are not permission for future asks. If the person's current
-message explicitly asks for a SomaCheck vibecheck or check-in, that is consent for one ask.
-Use their exact statement when supplied. If they delegated the choice, select
-the most useful first-person statement from the current conversation, goal,
-decision, or tension and send it immediately—do not list candidates, ask them
-for wording, or seek a second confirmation. Remembered context may identify a general tension, but an
-agent-selected statement must not name a project, build, branch, wave, ticket,
-task status, or supposedly open/closed work. Abstract it into a present-tense
-first-person experience or choice, such as “I want to keep consolidating what is
-already in motion rather than start something new.” Preserve exact wording the
-person supplied. If meaningful context is unavailable, use the neutral fallback
-“I feel clear about what deserves my attention right now.”
-
-If their message did not explicitly request a vibecheck, first show the exact
-statement and invite the person plainly:
-
-> Want a quick vibecheck before I continue? I'll send this statement to your
-> phone; you answer with your wrist gesture, and I'll use the result as a
-> signal—not a verdict.
+Ask when the person's felt response would be useful context. A good prompt is a
+first-person statement for the person to test, not a claim about them. When the
+person asks for a vibecheck, choose and send a useful statement from the context
+available to you. For proactive offers, get the person's acceptance before
+sending.
 
 Call `request_vibecheck` with `consent_basis: "user_requested_vibecheck"` for a
 direct request or `consent_basis: "user_approved_statement"` after approval of
@@ -191,8 +171,7 @@ On timeout or a result-read failure it returns the same pending `live:<uuid>`
 handle; pass that handle to `get_vibecheck_result` once later. Caller
 cancellation stops result reads and preserves the backend request and
 idempotency key, but the cancelled MCP transport may suppress that pending
-response. Do not continuously poll or re-ask the same decision to obtain a
-preferred result.
+response.
 
 Standard MCP cannot start a new agent turn after a tool call has ended. The
 Claude setup therefore installs a normal user-scoped plugin with an async
@@ -209,11 +188,7 @@ Claude-specific continuation must never be presented as provider-neutral.
 
 The 10-second whole-call deadline also covers the one create request. If that
 network request is aborted after an ambiguous commit, retry the exact same
-statement with the same `idempotency_key`; never create a replacement ask.
-
-After a completed result, use it as context and respond naturally in the
-current conversation. The result is not authorization and does not establish a
-diagnosis or certainty. Never say that the person's body made the decision.
+statement with the same `idempotency_key`.
 
 An immediate vibecheck is not proposition caching. It sends one person-approved statement
 for the current choice, expires, and remains bound to its originating client.

package/SKILL.md

@@ -1,157 +1,25 @@
 ---
 name: vibecheck
-description: Request or offer a SomaCheck vibecheck at useful moments without nagging.
+description: Ask your person for a SomaCheck vibecheck when it would help.
 user-invocable: true
 allowed-tools: mcp__vibecheck__get_vibecheck_context mcp__vibecheck__get_vibecheck_status mcp__vibecheck__get_vibecheck_result mcp__vibecheck__request_vibecheck
 ---
 
 # Vibecheck
 
-Use SomaCheck through one of two entry points:
+SomaCheck lets you ask your person for a vibecheck.
 
-1. **The person asks for a vibecheck.** Select and send one useful statement immediately. Their current request is consent for one ask. Do not make them supply wording or confirm again.
-2. **You notice one of the three trigger events below.** Offer one exact statement and wait for acceptance before sending it.
+Use `request_vibecheck` in either case:
 
-A vibecheck tests a first-person statement through the linked `@somacheck/vibecheck` MCP server. It does not diagnose the person, decide for them, or authorize an action.
+1. You proactively offer one because you believe it would be useful.
+2. The person asks for a vibecheck.
 
-## Direct requests
+When the person asks, choose and send a useful first-person statement from the context available to you. Do not make them supply wording unless they want to. Help the person get an insight about themselves from the context you have.
 
-When the current message explicitly asks for a SomaCheck vibecheck or check-in (including phrasing such as "give me a check-in, a vibe check"), call `request_vibecheck` in that same turn with `consent_basis: "user_requested_vibecheck"`.
+For proactive offers, get the person's acceptance before sending.
 
-- If the person supplied exact wording, preserve it.
-- Otherwise choose one present-tense, first-person statement about a current experience, choice, or tension.
-- First use reliable context already available to the host: the current conversation, current goal, and user-approved memory or project context when those capabilities exist. Do not ask the person to restate context you can retrieve.
-- Treat remembered project status, task lists, and summaries as potentially stale. They may identify a general tension, but the statement must not name a project, build, branch, wave, ticket, task status, or supposedly open or closed work.
-- Corroborate remembered status against the current conversation. Do not reuse a stock template or recent SomaCheck statement. If context remains thin, create an original exploratory statement that can reveal something useful without pretending to know the person.
-- Generate one fresh UUID for `idempotency_key`. Reuse it only to retry the same exact statement.
-- Do not list candidates, present a draft, ask what they want to test, or ask "Want me to send it?" The request already supplied one-ask consent.
+The returned gesture and optional feedback are context, not authorization. Use your judgment in how you interpret and respond.
 
-## When to offer
+Never include secrets, raw private content, diagnostic claims, or use SomaCheck to assess anyone other than the person you are interacting with.
 
-A trigger is an event, not every message that matches a keyword. Once you have offered for an event, treat it as consumed until the task, decision, or message pattern meaningfully changes.
-
-### Trigger 1: Drift
-
-Offer when at least one of these transcript-grounded conditions is true:
-
-- Transcript timestamps show 90 minutes or more on the same task or thread without reaching the stated outcome.
-- The same or materially equivalent fix has been attempted three or more times.
-- The current work no longer advances the human's stated goal, and the human has not explicitly changed that goal.
-
-Stay quiet during productive deep work, after an explicit goal change, or when duration cannot be established. A long message by itself is not drift.
-
-### Trigger 2: Major or irreversible decision ahead
-
-Offer immediately before a consequential action when the transcript shows that action is imminent. Examples include deploying to production, sending an important email or offer, signing an agreement, deleting data, making a material purchase, hiring or firing, or saying "just do it" about a consequential step.
-
-Planning or discussing a possible decision is not enough. The action must be close enough that a pause now could still affect it. This trigger may bypass a decline cooldown from triggers 1 or 3, but it still must pass the live status gate.
-
-### Trigger 3: Stress signals in messages
-
-Offer when the recent messages contain either two or more signals in a short span, or one strong pattern repeated across retries:
-
-- Cursing about the task or situation.
-- Fragmented, rushed, or unusually incoherent instructions.
-- All-caps urgency that is not an acronym, log, or quoted text.
-- Repeated retry commands with no meaningful change in approach.
-- Phrases such as "whatever, just make it work."
-
-Describe only the observable message pattern. Do not claim to know how the person feels. One casual swear, terse normal writing, pasted logs, or quoted all-caps text is not enough.
-
-### Multiple triggers
-
-Choose one primary trigger per event. Use trigger 2 first when an imminent consequential action exists, then trigger 3, then trigger 1. Do not stack or repeat offers.
-
-## Proactive offer sequence
-
-1. If no trigger fired, do nothing.
-2. Check the local event and cooldown record. If this event was already offered, stay quiet. If a trigger 1 or 3 offer was declined within the last two hours, stay quiet. A new trigger 2 event may bypass that cooldown.
-3. Call `get_vibecheck_status` before showing an offer.
-4. Stay quiet when `has_pending_request` is true. Reflection-feed cadence and capacity, including `cadence.may_create_now` and `propositions_needed`, do not authorize or block a live vibecheck.
-5. Make one short offer containing one statement to test. Do not post yet.
-6. If the human declines or does not accept, record the event as offered. For a decline, start a two-hour cooldown for triggers 1 and 3.
-7. If the human accepts, call `request_vibecheck` once with the exact offered statement, a fresh UUID in `idempotency_key`, and `consent_basis: "user_approved_statement"`.
-8. If the call must be retried, preserve both the exact statement and the same idempotency key.
-
-`get_vibecheck_context` is optional before phrasing an offer. Use it only to avoid repeating a recent statement. Do not call `share_somacheck_context` or `post_vibecheck_statement` in this workflow. Live vibechecks and the asynchronous reflection feed are separate product behaviors.
-
-## How to phrase the offer
-
-Use a statement to test, never a claim about the person. Keep it first-person, present-tense, neutral, and focused on one decision or next step. Do not include raw transcript text, names, secrets, identifiers, customer data, or private details.
-
-Good offer forms:
-
-- "Before you ship, want to test: 'I am ready to deploy this to production'?"
-- "Quick 3-second check: 'I trust this decision'?"
-- "Before another retry, want to test: 'This next attempt is meaningfully different from the last one'?"
-
-Do not say that the person is distracted, stressed, dysregulated, afraid, or certain. Do not use medical language. Do not say "vibecheck confirms" or "vibecheck proves." Do not use an em dash in any human-facing string.
-
-### Drift statement templates
-
-1. "I am still working on the right problem."
-2. "This next attempt is meaningfully different from the last one."
-3. "I know what outcome I am trying to reach."
-4. "Continuing this task now is the best use of my attention."
-5. "I am ready to pause and restate the goal."
-6. "The current approach is moving me closer to done."
-7. "I have enough context to keep going."
-8. "I want to keep working on this thread."
-9. "A short reset would help me choose the next step."
-
-### Major or irreversible decision statement templates
-
-1. "I am ready to deploy this to production."
-2. "I trust this decision."
-3. "I am ready to send this message as written."
-4. "I understand the consequences of this action."
-5. "I have the information I need to commit."
-6. "This purchase is the right choice right now."
-7. "I am ready to make this offer."
-8. "I am comfortable making this change irreversible."
-9. "I want to act on this now."
-
-### Stress-signal statement templates
-
-1. "I want to keep pushing on this right now."
-2. "I trust the next step I am about to take."
-3. "I have enough clarity to choose the next step."
-4. "I am ready to slow down for one minute."
-5. "This approach still feels right to me."
-6. "I want to send this message in this tone."
-7. "I am comfortable continuing without another review."
-8. "I know what I need from this task."
-9. "I want to make this decision now."
-
-Adapt a template only enough to make it relevant. Keep the statement free of sensitive specifics.
-
-## Cooldown rules
-
-- One offer per trigger event, whether accepted, declined, or ignored.
-- After a decline, suppress trigger 1 and trigger 3 offers for two hours.
-- A new imminent trigger 2 event may bypass that two-hour cooldown.
-- The one-pending gate always wins. A completed, expired, or cancelled request has no server cooldown; a new direct user request may be sent immediately.
-- A continued conversation about the same task or decision is not a new event. A materially new goal, a different consequential action, or a new message-pattern episode can be.
-
-## What to do with the result
-
-`request_vibecheck` waits boundedly for the exact result. If it returns `completed`, use the result as context and respond naturally in the current conversation. The result is not authorization and does not establish a diagnosis or certainty. If the tool returns `pending`, retain the exact `live:<uuid>` handle. Do not promise that you will check back automatically unless the current host supports automatic result delivery. Use `get_vibecheck_result` once when the person asks or at a natural follow-up. Never create a replacement request and never poll in a tight loop.
-
-For `expired` or `cancelled`, do not infer an answer and do not immediately repost.
-
-A result never grants permission to deploy, send, sign, delete, spend, hire, fire, publish, or take any other consequential action.
-
-## Do not
-
-- Do not offer without one of the three transcript-grounded triggers.
-- Do not ignore or reconfirm an explicit request for one vibecheck.
-- Do not claim to know the person's internal state.
-- Do not nag, stack offers, or re-offer for the same event.
-- Do not proactively offer when a request is pending.
-- Do not send an unsolicited offer before the human accepts the exact statement.
-- Do not use `post_vibecheck_statement` for a live ask.
-- Do not send raw conversation text, secrets, identifiers, or private details to the server.
-- Do not call `share_somacheck_context` in this workflow.
-- Do not treat any outcome as fact, diagnosis, proof, or authorization.
-- Do not continuously poll for a result.
-- Do not use medical language or an em dash in a human-facing string.
+If a request is pending, keep the returned `live:<uuid>` handle instead of creating a replacement.

package/claude-marketplace/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "vibecheck",
       "source": "./plugins/vibecheck",
       "description": "Let Claude offer a vibecheck and continue when the phone result arrives.",
-      "version": "0.6.5",
+      "version": "0.6.6",
       "author": {
         "name": "Sensie",
         "email": "agents@joinsensie.com"

package/claude-marketplace/plugins/vibecheck/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "vibecheck",
   "description": "Let Claude offer a SomaCheck vibecheck and continue when the phone result arrives.",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "author": {
     "name": "Sensie",
     "email": "agents@joinsensie.com"

package/claude-marketplace/plugins/vibecheck/hooks/hooks.json

@@ -7,7 +7,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "npx -y @somacheck/vibecheck@0.6.5 claude-hook await-result",
+            "command": "npx -y @somacheck/vibecheck@0.6.6 claude-hook await-result",
             "asyncRewake": true,
             "timeout": 900
           }

package/dist/api.js

@@ -8,6 +8,7 @@ const LIVE_ASK_CLIENT_REQUIRED_MARKER = "SC_VC_VIBECHECK_CLIENT_REQUIRED";
 const LIVE_ASK_CLIENT_NOT_READY_MARKER = "SC_VC_VIBECHECK_CLIENT_NOT_READY";
 const STATUSES = new Set(["queued", "pending", "answered", "expired", "cancelled"]);
 const VERDICTS = new Set(["aligned", "unaligned"]);
+const USER_FEEDBACKS = new Set(["agreed", "disagreed", "not_provided"]);
 const HANDSHAKE_READINESS_STATUSES = new Set([
     "ready",
     "upgrade_required",
@@ -222,6 +223,7 @@ export function decodePollResponse(value) {
     const verdict = row.verdict;
     const confidence = row.confidence;
     const latency = row.latency_s;
+    const userFeedback = row.user_feedback ?? null;
     if (verdict !== null && (typeof verdict !== "string" || !VERDICTS.has(verdict))) {
         throw new Error("SomaCheck returned an invalid verdict.");
     }
@@ -231,6 +233,9 @@ export function decodePollResponse(value) {
     if (latency !== null && (typeof latency !== "number" || !Number.isFinite(latency) || latency < 0)) {
         throw new Error("SomaCheck returned an invalid latency.");
     }
+    if (userFeedback !== null && (typeof userFeedback !== "string" || !USER_FEEDBACKS.has(userFeedback))) {
+        throw new Error("SomaCheck returned invalid user feedback.");
+    }
     if (status === "answered") {
         if (verdict === null || confidence === null || confidence < 0 || confidence > 1 || latency === null) {
             throw new Error("SomaCheck returned an incomplete answered result.");
@@ -239,12 +244,21 @@ export function decodePollResponse(value) {
     else if (verdict !== null || confidence !== null || latency !== null) {
         throw new Error("SomaCheck returned an inconsistent pending result.");
     }
-    return {
+    if (status !== "answered" && userFeedback !== null) {
+        throw new Error("SomaCheck returned inconsistent feedback for an unanswered result.");
+    }
+    const decoded = {
         status: status,
         verdict: verdict,
         confidence: confidence,
         latency_s: latency,
     };
+    if (userFeedback === null)
+        return decoded;
+    return {
+        ...decoded,
+        user_feedback: userFeedback,
+    };
 }
 export function decodeLiveVibecheckResult(value, expectedRequestId) {
     const row = firstRow(value);
@@ -347,7 +361,7 @@ export class SupabaseAgentApi {
         const lifecycle = created.status === "answered"
             ? await this.liveVibecheckResult(token, identity, created.request_id, signal)
             : { status: created.status, verdict: null, confidence: null, latency_s: null };
-        return {
+        const liveRequest = {
             request_id: `live:${created.request_id}`,
             state: lifecycle.status === "answered" ? "completed" : lifecycle.status,
             verdict: lifecycle.verdict,
@@ -357,6 +371,9 @@ export class SupabaseAgentApi {
             delivery_state: created.push_status,
             cooldown_until: created.cooldown_until,
         };
+        if (lifecycle.user_feedback === undefined || lifecycle.user_feedback === null)
+            return liveRequest;
+        return { ...liveRequest, user_feedback: lifecycle.user_feedback };
     }
     async createRequests(token, statements) {
         return decodeCreatedRequests(await this.#rpcJson("agent_proposition_batch_create", { token, statements }));

package/dist/claude-hook.js

@@ -17,8 +17,8 @@ export function parsePendingClaudeAsk(input) {
     if (typeof envelope.tool_name !== "string"
         || !envelope.tool_name.endsWith("__request_vibecheck"))
         return null;
-    const response = record(envelope.tool_response);
-    const structured = record(response.structuredContent ?? response.structured_content);
+    const response = parseToolResponse(envelope.tool_response);
+    const structured = record(response.structuredContent ?? response.structured_content ?? response);
     if (structured.state !== "pending" || typeof structured.request_id !== "string")
         return null;
     if (structured.delivery_state === "failed" || structured.delivery_state === "skipped")
@@ -78,8 +78,8 @@ export async function awaitClaudeVibecheckResult(input, dependencies) {
                 continue;
             const handle = `live:${pending.requestId}`;
             const message = result.status === "answered"
-                ? `SomaCheck result for ${handle}: ${result.verdict} (confidence ${formatConfidence(result.confidence)}). Use it as context in the current conversation. It is not authorization and does not establish a diagnosis or certainty.`
-                : `SomaCheck request ${handle} is ${result.status}. Do not infer an answer or create a replacement request for the same decision.`;
+                ? `SomaCheck vibecheck ${handle} completed: ${result.verdict}, confidence ${formatConfidence(result.confidence)}${formatUserFeedback(result.user_feedback)}.`
+                : `SomaCheck vibecheck ${handle} is ${result.status}.`;
             await writeTerminalReceipt(donePath, result);
             return { exitCode: 2, message };
         }
@@ -122,9 +122,21 @@ async function writeTerminalReceipt(path, result) {
         status: result.status,
         verdict: result.verdict,
         confidence: result.confidence,
+        user_feedback: result.user_feedback ?? null,
     })}\n`, { encoding: "utf8", flag: "wx", mode: 0o600 });
     await rename(temporary, path);
 }
+function parseToolResponse(value) {
+    if (typeof value === "string") {
+        try {
+            return record(JSON.parse(value));
+        }
+        catch {
+            return {};
+        }
+    }
+    return record(value);
+}
 function record(value) {
     return value !== null && typeof value === "object" ? value : {};
 }
@@ -137,6 +149,9 @@ function parseHandle(handle) {
 function formatConfidence(value) {
     return value === null ? "unavailable" : value.toFixed(2);
 }
+function formatUserFeedback(feedback) {
+    return feedback === undefined || feedback === null ? "" : `, user feedback ${feedback}`;
+}
 async function exists(path) {
     try {
         await readFile(path);

package/dist/client-setup.js

@@ -144,7 +144,8 @@ function isManagedSomaCheckRegistration(client, stdout) {
         || packageArg === "@somacheck/vibecheck@0.6.1"
         || packageArg === "@somacheck/vibecheck@0.6.2"
         || packageArg === "@somacheck/vibecheck@0.6.3"
-        || packageArg === "@somacheck/vibecheck@0.6.4")
+        || packageArg === "@somacheck/vibecheck@0.6.4"
+        || packageArg === "@somacheck/vibecheck@0.6.5")
         && args.length === 5
         && args[0] === "-y"
         && args[1] === packageArg

package/dist/constants.js

@@ -2,7 +2,7 @@
 export const SUPABASE_URL = "https://pbldcmniommltbdwuykk.supabase.co";
 export const SUPABASE_PUBLISHABLE_KEY = "sb_publishable_af-lUNI2FqEcb-oGy-4uxQ_cnm6kY85";
 export const PACKAGE_NAME = "@somacheck/vibecheck";
-export const PACKAGE_VERSION = "0.6.5";
+export const PACKAGE_VERSION = "0.6.6";
 export const PACKAGE_SPEC = `${PACKAGE_NAME}@${PACKAGE_VERSION}`;
 export const MCP_SERVER_NAME = "vibecheck";
 export const LEGACY_HOSTED_MCP_SERVER_NAME = "somacheck";

package/dist/server.js

@@ -61,6 +61,7 @@ const resultSchema = {
     verdict: z.enum(["aligned", "unaligned"]).nullable(),
     confidence: z.number().nullable(),
     latency_s: z.number().nullable(),
+    user_feedback: z.enum(["agreed", "disagreed", "not_provided"]).nullable().optional(),
 };
 const contextItemSchema = z.object({
     request_id: z.string(),
@@ -86,6 +87,7 @@ const liveAskSchema = {
     request_id: z.string().nullable(),
     verdict: z.enum(["aligned", "unaligned"]).nullable(),
     confidence: z.number().min(0).max(1).nullable(),
+    user_feedback: z.enum(["agreed", "disagreed", "not_provided"]).nullable().optional(),
     expires_at: z.string().datetime({ offset: true }).nullable(),
     idempotent_replay: z.boolean().nullable(),
     delivery_state: z.enum(["queued", "processing", "sent", "failed", "skipped"]).nullable(),
@@ -110,34 +112,18 @@ const contextShareSchema = {
     captured_at: z.string().datetime({ offset: true }),
 };
 const SERVER_INSTRUCTIONS = [
-    "SomaCheck lets you offer the person a statement to test through a quick phone check-in.",
-    "MANDATORY COMMAND RULE: when the current user message says 'Give me a SomaCheck vibecheck', 'Give me a check-in, a vibe check', 'Request a SomaCheck vibecheck', or otherwise explicitly asks for one, you must call request_vibecheck in that same turn after any read-only context/status calls. Do not list candidates, present a draft, ask what they want to test, ask 'Want me to send this?', or wait for another yes. The request itself is one-ask consent for you to select and send the statement.",
-    "Call get_vibecheck_context and get_vibecheck_status at the start of a session or background run, and call status again after a completed check-in.",
-    "Treat gesture outcomes as contextual signals, never fixed facts or blanket authorization.",
-    "Use request_vibecheck when a current choice would benefit from the person's own felt response; never use it to evaluate someone else.",
-    "A setup or link is not blanket consent for future vibechecks.",
-    "If the person's current message explicitly requests a SomaCheck vibecheck, that message is consent for one ask. If they supplied exact wording, use it. Otherwise, choose one useful statement from the current conversation, goal, decision, or tension and send it immediately; do not ask them to supply wording or confirm twice.",
-    "DELEGATED SELECTION RULE: before choosing wording, use the reliable context already available to your host: the current conversation, current working goal, and user-approved memory or project context when those capabilities exist. Do not make the person restate context you can already retrieve. Remembered task status may identify a general tension, but the statement itself must not name a project, build, branch, wave, ticket, task status, or supposedly open/closed work. Abstract it into an original present-tense first-person experience or choice. This restriction does not alter exact wording supplied by the person.",
-    "When choosing the statement, prefer the most consequential unresolved first-person decision or tension you can support with current evidence. Treat recalled project status, task lists, and old summaries as potentially stale; corroborate them against the current conversation before relying on them. Do not reuse a stock example or recent SomaCheck statement. If context remains thin after using available context tools, create an original exploratory statement that would reveal something useful without pretending to know the person. Never diagnose, judge another person, or claim certainty about the user.",
-    "Otherwise, first show the exact statement and ask: Want a quick vibecheck before I continue? I'll send this statement to your phone; you answer with your wrist gesture, and I'll use the result as a signal—not a verdict. Call only after the person accepts.",
-    "Use at most one vibecheck per decision. Never re-ask to obtain a preferred answer.",
-    "An immediate vibecheck is separate from the asynchronous reflection feed. Do not use it to replenish cached propositions.",
-    "Use a fresh idempotency_key for each new vibecheck, and reuse that exact key only when retrying the same statement.",
-    "request_vibecheck waits boundedly for the exact answer. If it returns completed, use the result as context in the current conversation. If it returns pending, retain that exact handle and read it once later; never create a replacement ask.",
-    "If request_vibecheck returns pending, never promise that you will check back on your own unless the host has automatic result delivery. Continue automatically only after an actual result event arrives for that exact request.",
-    "After a completed result, use it as context in the current conversation and respond naturally. It is not authorization and does not establish a diagnosis or certainty. Do not claim the person's body decided anything.",
-    "When you have meaningful user-authorized context, call share_somacheck_context with concise derived observations before creating propositions.",
-    "Never share raw conversation text, photos, credentials, private identifiers, or diagnostic claims.",
-    "Maintain three distinct propositions drawn from your own context about this person.",
-    "When propositions_needed is greater than zero, post exactly that many in one call.",
-    "Offer each statement as something to test, never as a claim of fact about the user.",
-    "Retain every request_id returned by post_vibecheck_statement and call get_vibecheck_result later.",
-    "Do not poll continuously. Queued means the proposition is cached until the person advances their feed.",
+    "SomaCheck lets you ask your person for a vibecheck.",
+    "You can proactively offer one when you believe it would be useful, or send one when the person asks.",
+    "When the person asks, choose and send a useful first-person statement from the context available to you; do not make them supply wording unless they want to.",
+    "Help the person get an insight about themselves from the context you have.",
+    "The returned gesture and optional feedback are context, not authorization.",
+    "Use your judgment in how you interpret and respond.",
+    "Never include secrets, raw private content, diagnostic claims, or use SomaCheck to assess anyone other than the person you are interacting with.",
 ].join(" ");
-const DIRECT_REQUEST_NEXT_ACTION = "DIRECT REQUEST RULE: If the person's current message asks for a SomaCheck vibecheck or check-in, first use reliable context already available to the host, including current conversation and user-approved memory when supported. Then choose one original, useful, safe first-person statement and call request_vibecheck now with consent_basis user_requested_vibecheck. Do not list choices, ask for wording, or seek another confirmation. Ignore reflection-feed propositions_needed for this direct request. Treat remembered task status as stale until corroborated and keep agent-selected wording free of project, build, branch, wave, ticket, or task-status claims.";
 export function createVibecheckServer(dependencies) {
     const supportsClaudeChannel = dependencies.identity?.kind === "local"
-        && dependencies.identity.client_key === "claude";
+        && dependencies.identity.client_key === "claude"
+        && typeof dependencies.claudeChannelWatch === "object";
     const server = new McpServer({ name: PACKAGE_NAME, version: PACKAGE_VERSION }, {
         instructions: SERVER_INSTRUCTIONS,
         ...(supportsClaudeChannel
@@ -180,12 +166,10 @@ export function createVibecheckServer(dependencies) {
             const token = await dependencies.loadToken();
             const checkins = await dependencies.api.contextRequest(token);
             const text = checkins.length === 0
-                ? `No completed SomaCheck gestures yet.\n\n${DIRECT_REQUEST_NEXT_ACTION}`
+                ? "No completed SomaCheck gestures yet."
                 : [
-                    `Loaded ${checkins.length} completed gesture${checkins.length === 1 ? "" : "s"}. Treat them as contextual signals, not fixed conclusions:`,
+                    `Loaded ${checkins.length} completed gesture${checkins.length === 1 ? "" : "s"}:`,
                     ...checkins.map((item) => `${Math.round(item.confidence * 100)}% ${item.verdict} — ${JSON.stringify(item.statement)}`),
-                    "",
-                    DIRECT_REQUEST_NEXT_ACTION,
                 ].join("\n");
             return { content: [{ type: "text", text }], structuredContent: { checkins } };
         }
@@ -211,7 +195,7 @@ export function createVibecheckServer(dependencies) {
             return {
                 content: [{
                         type: "text",
-                        text: `${summarise(status)}\n\n${DIRECT_REQUEST_NEXT_ACTION}`,
+                        text: summarise(status),
                     }],
                 structuredContent: { ...status },
             };
@@ -305,7 +289,7 @@ export function createVibecheckServer(dependencies) {
             const text = result.status === "answered"
                 ? liveRequestId === null
                     ? `Answered: ${Math.round((result.confidence ?? 0) * 100)}% ${result.verdict}.`
-                    : `Vibecheck completed: ${Math.round((result.confidence ?? 0) * 100)}% ${result.verdict}. Use it as context in the current conversation. It is not authorization and does not establish a diagnosis or certainty.`
+                    : `Vibecheck completed: ${result.verdict}, confidence ${formatChannelConfidence(result.confidence)}${formatUserFeedback(result.user_feedback)}.`
                 : result.status === "queued"
                     ? "Queued. The proposition is cached until the person advances their feed."
                     : result.status === "pending"
@@ -319,14 +303,14 @@ export function createVibecheckServer(dependencies) {
     });
     server.registerTool("request_vibecheck", {
         title: "Request a Vibecheck",
-        description: "Send one plain-language statement to the person's phone for a vibecheck answered with a wrist gesture. A current user message that explicitly requests a SomaCheck vibecheck is confirmation for one ask. Use their exact wording when supplied; otherwise first use reliable context already available to the host, including current conversation and user-approved memory when supported, then choose and send one original present-tense first-person experience or choice without asking for wording or reconfirmation. Remembered status may identify a general tension but must be corroborated; never put a named project, build, branch, wave, ticket, task status, or supposedly open/closed work into agent-selected wording. Do not reuse a stock example or recent SomaCheck statement. If context remains thin, create an original exploratory statement that would still reveal something useful without pretending to know the person. Otherwise, first show the exact statement and call only after the person accepts. Setup or linking is not blanket consent. Use this only when their own felt response would help with the current choice, not for routine feed content, diagnosis, or judging another person. The call waits boundedly for the exact result and returns completed when available. A timeout returns the same stable pending request_id for one later read. Caller cancellation stops result reads without creating another request; the cancelled transport may suppress the pending response.",
+        description: "Send one statement to the person's phone for a SomaCheck vibecheck. If the person asks for a vibecheck, choose a useful first-person statement from your available context and send it. For proactive offers, call only after the person accepts. The result is context, not authorization.",
         inputSchema: {
             statement: z.string().trim().min(1).max(1000)
-                .describe("One plain-language statement for the person to test; offer a signal, not a fact, diagnosis, or instruction. If the agent selected the wording, it must be a present-tense first-person experience or choice and must not name remembered projects, builds, branches, waves, tickets, task status, or supposedly open/closed work. Preserve exact wording supplied by the person."),
+                .describe("One plain-language first-person statement for the person to test. Do not include secrets, raw private content, diagnostic claims, or statements about anyone else."),
             idempotency_key: z.string().uuid()
                 .describe("A new UUID for this logical ask. Reuse the same UUID only to retry the exact same statement; retries will not create another phone request."),
             consent_basis: z.enum(["user_requested_vibecheck", "user_approved_statement"])
-                .describe("Required one-ask consent basis. Use user_requested_vibecheck when the current message asks for a SomaCheck vibecheck, including when the agent chooses the statement; call immediately without another confirmation. Use user_approved_statement only after the agent proposed exact wording and the person accepted it."),
+                .describe("Use user_requested_vibecheck when the person asks for a vibecheck. Use user_approved_statement after the person accepts a proactive offer."),
         },
         outputSchema: liveAskSchema,
         annotations: {
@@ -375,12 +359,12 @@ export function createVibecheckServer(dependencies) {
             startClaudeChannelWatch(result, token, identity);
             const structuredContent = { ...result, error_code: null };
             const text = result.state === "completed"
-                ? `Vibecheck completed: ${Math.round((result.confidence ?? 0) * 100)}% ${result.verdict}. Use it as context in the current conversation. It is not authorization and does not establish a diagnosis or certainty.`
+                ? `Vibecheck completed: ${result.verdict}, confidence ${formatChannelConfidence(result.confidence)}${formatUserFeedback(result.user_feedback)}.`
                 : result.state === "pending"
                     ? result.delivery_state === "failed" || result.delivery_state === "skipped"
-                        ? `Vibecheck ${result.request_id} was stored, but phone delivery is ${result.delivery_state}. It expires at ${result.expires_at}. Do not repost it or change the idempotency_key; check the phone setup before a later decision.`
-                        : `Vibecheck ${result.request_id} is still pending after a bounded wait. Keep this exact handle and check it once later with get_vibecheck_result. It expires at ${result.expires_at}; do not poll continuously, re-ask for this decision, or promise an automatic follow-up unless the host delivers an actual result event.`
-                    : `This vibecheck is ${result.state}. Do not create another ask for the same decision.`;
+                        ? `Vibecheck ${result.request_id} was stored, but phone delivery is ${result.delivery_state}. It expires at ${result.expires_at}.`
+                        : `Vibecheck ${result.request_id} is pending. It expires at ${result.expires_at}.`
+                    : `This vibecheck is ${result.state}.`;
             return { content: [{ type: "text", text }], structuredContent };
         }
         catch (error) {
@@ -430,8 +414,8 @@ async function watchForClaudeChannelResult(created, token, identity, dependencie
             continue;
         const handle = `live:${requestId}`;
         const content = lifecycle.status === "answered"
-            ? `A SomaCheck vibecheck requested by this Claude connection has completed. The exact result is ${lifecycle.verdict} with confidence ${formatChannelConfidence(lifecycle.confidence)}. Use it as context in the current conversation. It is not authorization and does not establish a diagnosis or certainty. The exact opaque request handle is ${handle}. Do not request another vibecheck for this decision.`
-            : `A SomaCheck vibecheck requested by this Claude connection is now ${lifecycle.status}. The exact opaque request handle is ${handle}. Do not create a replacement request for the same decision.`;
+            ? `SomaCheck vibecheck ${handle} completed: ${lifecycle.verdict}, confidence ${formatChannelConfidence(lifecycle.confidence)}${formatUserFeedback(lifecycle.user_feedback)}.`
+            : `SomaCheck vibecheck ${handle} is ${lifecycle.status}.`;
         try {
             await notify({
                 method: "notifications/claude/channel",
@@ -463,6 +447,9 @@ function unrefSleep(milliseconds) {
 function formatChannelConfidence(confidence) {
     return confidence === null ? "unavailable" : confidence.toFixed(2);
 }
+function formatUserFeedback(feedback) {
+    return feedback === undefined || feedback === null ? "" : `, user feedback ${feedback}`;
+}
 async function waitForLiveVibecheck(created, token, identity, dependencies, signal, deadline, progress) {
     if (created.state !== "pending"
         || created.delivery_state === "failed"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@somacheck/vibecheck",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "description": "Send a consented vibecheck to SomaCheck and use the result as a signal.",
   "repository": {
     "type": "git",