@somacheck/vibecheck 0.6.2 → 0.6.4

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.2 link <CODE> --client <CLIENT>`
+**What the `link` command does.** `npx -y @somacheck/vibecheck@0.6.4 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
@@ -78,9 +78,9 @@ before the pairing code is redeemed.
 To configure or repair a client later:
 
 ```text
-npx -y @somacheck/vibecheck@0.6.2 setup codex
-npx -y @somacheck/vibecheck@0.6.2 setup claude
-npx -y @somacheck/vibecheck@0.6.2 doctor
+npx -y @somacheck/vibecheck@0.6.4 setup codex
+npx -y @somacheck/vibecheck@0.6.4 setup claude
+npx -y @somacheck/vibecheck@0.6.4 doctor
 ```
 
 Manual registration remains available:
@@ -90,13 +90,13 @@ Manual registration remains available:
      "mcpServers": {
        "vibecheck": {
          "command": "npx",
-        "args": ["-y", "@somacheck/vibecheck@0.6.2", "serve", "--client", "codex"]
+        "args": ["-y", "@somacheck/vibecheck@0.6.4", "serve", "--client", "codex"]
        }
      }
    }
    ```
 
-   For Claude Code: `claude mcp add --scope user vibecheck -- npx -y @somacheck/vibecheck@0.6.2 serve --client claude`
+   For Claude Code: `claude mcp add --scope user vibecheck -- npx -y @somacheck/vibecheck@0.6.4 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
@@ -160,11 +160,11 @@ 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, that is consent for one ask.
+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 ask them for wording or a
-second confirmation. Remembered context may identify a general tension, but an
+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
@@ -213,7 +213,10 @@ The 45-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, explain what the signal changes in your next action.
+After a completed result, reconcile it with the current goal, state one
+observable change, and continue with the next reversible in-scope action when
+it is already authorized. Do not stop at repeating the verdict, confidence, or
+generic signal language.
 Never treat it as authorization or say that the person's body made the
 decision. A typed response from the person always overrides the signal.
 

package/dist/cli.js

@@ -3,7 +3,7 @@ import { homedir } from "node:os";
 import { createInterface } from "node:readline/promises";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { SupabaseAgentApi } from "./api.js";
-import { clientDisplayName, detectInstalledClients, detectLegacyHostedRegistration, LocalCommandRunner, manualLegacyHostedRemoveCommand, manualRemoveCommand, manualSetupCommand, parseClientChoice, preflightClientPersistence, registerClient, singleNonInteractiveClientSelection, } from "./client-setup.js";
+import { automaticContinuationCommand, clientDisplayName, detectInstalledClients, detectLegacyHostedRegistration, LocalCommandRunner, manualLegacyHostedRemoveCommand, manualRemoveCommand, manualSetupCommand, parseClientChoice, preflightClientPersistence, registerClient, singleNonInteractiveClientSelection, } from "./client-setup.js";
 import { readConfig } from "./config.js";
 import { PACKAGE_SPEC, SUPABASE_PUBLISHABLE_KEY, SUPABASE_URL } from "./constants.js";
 import { LinkPersistenceError, NonInteractiveLinkError, linkAgent } from "./link.js";
@@ -93,6 +93,12 @@ async function configureClients(clients) {
         else {
             output(`✗ Could not configure ${clientDisplayName(client)} automatically.`);
         }
+        const continuationCommand = automaticContinuationCommand(client);
+        if (continuationCommand !== null && ["registered", "upgraded", "already_registered"].includes(result.status)) {
+            output("  For automatic result continuation, start Claude Code with:");
+            output(`  ${continuationCommand}`);
+            output("  Standard Claude Code keeps the request safe but cannot wake itself after the tool call ends.");
+        }
     }
 }
 async function preflightLinkClients(clients, interactive) {

package/dist/client-setup.js

@@ -34,6 +34,11 @@ export function manualSetupCommand(client) {
     }
     return `claude mcp add --scope user ${MCP_SERVER_NAME} -- npx ${mcpServerArgs(client).join(" ")}`;
 }
+export function automaticContinuationCommand(client) {
+    return client === "claude"
+        ? "claude --dangerously-load-development-channels server:vibecheck"
+        : null;
+}
 export function manualRemoveCommand(client) {
     return client === "codex"
         ? `codex mcp remove ${MCP_SERVER_NAME}`
@@ -141,7 +146,9 @@ function isManagedSomaCheckRegistration(client, stdout) {
     // client remain user-owned.
     const previousExactClient = (/^@somacheck\/vibecheck@0\.5\.\d+$/.test(packageArg)
         || packageArg === "@somacheck/vibecheck@0.6.0"
-        || packageArg === "@somacheck/vibecheck@0.6.1")
+        || packageArg === "@somacheck/vibecheck@0.6.1"
+        || packageArg === "@somacheck/vibecheck@0.6.2"
+        || packageArg === "@somacheck/vibecheck@0.6.3")
         && 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.2";
+export const PACKAGE_VERSION = "0.6.4";
 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

@@ -112,21 +112,21 @@ const contextShareSchema = {
 };
 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', '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 present a draft, 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.",
+    "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: when you choose the wording, remembered context 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 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.' 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 already understand. Treat recalled project status, task lists, and old summaries as potentially stale. Never use them as a factual premise for agent-selected wording, even if they were recalled in the current turn. If context is thin, use the neutral fallback 'I feel clear about what deserves my attention right now.' Never diagnose, judge another person, or claim certainty about the user.",
+    "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, continue in the same turn and explain what changes. 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. Only continue automatically after an actual SomaCheck channel event arrives for that exact request.",
-    "After a completed result, say what the signal changes in your next action. Never say 'your body decided'; a typed human response always overrides the signal.",
+    "After a completed result, do not merely repeat the verdict, confidence, or generic signal-not-verdict language. Reconcile the result with the current goal and state one observable change in your next action. Continue with that next reversible in-scope action when it is already authorized; if new permission is required, name the exact prepared next step and ask only for that permission. Never say 'your body decided'; a typed human response always overrides the signal.",
     "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.",
@@ -135,6 +135,7 @@ const SERVER_INSTRUCTIONS = [
     "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.",
 ].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";
@@ -180,10 +181,12 @@ 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."
+                ? `No completed SomaCheck gestures yet.\n\n${DIRECT_REQUEST_NEXT_ACTION}`
                 : [
                     `Loaded ${checkins.length} completed gesture${checkins.length === 1 ? "" : "s"}. Treat them as contextual signals, not fixed conclusions:`,
                     ...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 } };
         }
@@ -207,7 +210,10 @@ export function createVibecheckServer(dependencies) {
             const token = await dependencies.loadToken();
             const status = await dependencies.api.statusRequest(token);
             return {
-                content: [{ type: "text", text: summarise(status) }],
+                content: [{
+                        type: "text",
+                        text: `${summarise(status)}\n\n${DIRECT_REQUEST_NEXT_ACTION}`,
+                    }],
                 structuredContent: { ...status },
             };
         }
@@ -300,7 +306,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}. Treat this as a signal, say what it changes in your next action, and defer to any typed response from the person.`
+                    : `Vibecheck completed: ${Math.round((result.confidence ?? 0) * 100)}% ${result.verdict}. Do not stop at restating the result or generic signal language. Reconcile it with the current goal, state one observable change, and continue with the next reversible in-scope action when already authorized. If new permission is required, name the exact prepared next step. A typed response from the person always overrides this signal.`
                 : result.status === "queued"
                     ? "Queued. The proposition is cached until the person advances their feed."
                     : result.status === "pending"
@@ -314,7 +320,7 @@ 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 choose and send one present-tense first-person experience or choice immediately without asking for wording or reconfirmation. When you choose the wording, remembered context may identify only the general tension: never put a named project, build, branch, wave, ticket, task status, or supposedly open/closed work into the statement, even when recalled in the current turn. Abstract it, for example: 'I want to keep consolidating what is already in motion rather than start something new.' If context is thin, use the neutral fallback 'I feel clear about what deserves my attention right now.' 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 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.",
         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."),
@@ -370,7 +376,7 @@ 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}. Treat this as a signal, say what it changes in your next action, and defer to any typed response from the person.`
+                ? `Vibecheck completed: ${Math.round((result.confidence ?? 0) * 100)}% ${result.verdict}. Do not stop at restating the result or generic signal language. Reconcile it with the current goal, state one observable change, and continue with the next reversible in-scope action when already authorized. If new permission is required, name the exact prepared next step. A typed response from the person always overrides this signal.`
                 : 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.`
@@ -425,7 +431,7 @@ 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)}. Treat it as a signal, not a verdict. Continue the current conversation now: briefly acknowledge the signal and state what it changes in your next action. The exact opaque request handle is ${handle}. Do not request another vibecheck for this decision.`
+            ? `A SomaCheck vibecheck requested by this Claude connection has completed. The exact result is ${lifecycle.verdict} with confidence ${formatChannelConfidence(lifecycle.confidence)}. Continue the current conversation now. Do not merely restate the result or give generic signal-not-verdict commentary. Reconcile it with the current goal, state one observable change in your next action, and perform the next reversible in-scope action when it is already authorized. If new permission is required, name the exact prepared next step and ask only for that permission. 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.`;
         try {
             await notify({

package/package.json

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