@mindstudio-ai/remy 0.1.264 → 0.1.265

package/dist/prompt/skills/voiceInterfaces.md

@@ -78,6 +78,25 @@ Classify by how the method actually behaves, not by what it is named. A "lookup"
 external service is `slow`. When in doubt between `fast` and `slow`, pick `slow` — a needless
 preamble is mildly chatty; an unexplained silence feels broken.
 
+### Forwarding results to the screen (`forwardResult`)
+
+A tool block may declare `forwardResult: true`. On completion, the platform then delivers the
+tool's raw return value to the session's browser on the SDK's `toolCall` event (`result` field) —
+so the UI can render what the agent just did (the citation it found, the record it pulled up, the
+booking it made) in lockstep with the spoken answer. No polling, no key-threading, no model
+involvement: the correlation is platform-guaranteed and scoped to that one session's client.
+
+Opt in deliberately, per tool. The forwarded payload is the method's raw return — the same data
+the model sees — so only enable it on tools whose returns are safe to render for the user in the
+call (no internal fields you wouldn't show on screen). Payloads over ~32KB serialized arrive as
+`resultTruncated: true` with no data — keep forwarded returns compact, or have the UI fetch big
+data itself. Failed calls never forward anything.
+
+For backend-side correlation (writing results to a table keyed by the call, custom channels), the
+method itself can read `session.voiceSessionId` / `session.visitorId` from the agent SDK
+(`import { session } from '@mindstudio-ai/agent'`) — the same id the browser holds as
+`session.sessionId`, guaranteed by the platform rather than echoed by the model.
+
 ### Tool descriptions say results out loud
 
 Follow the agent-interface principles for tool descriptions (when to use and when not, parameter
@@ -115,7 +134,8 @@ Two shapes, one `model` field:
   can be *any* chat model — the right choice when the app's reasoning demands a specific model, or
   when the agent interface already uses one and the voice should think identically. The blessed
   streaming pairing is `"stt": "deepgram-nova-3", "tts": "cartesia-sonic-3"` — the lowest-latency
-  combination the platform wires; prefer it unless there's a reason not to. One nuance: cascaded
+  combination the platform wires; prefer it unless there's a reason not to (ElevenLabs TTS,
+  `"tts": "elevenlabs-tts"`, is also wired when its voice library fits better). One nuance: cascaded
   engines speak the `greeting` verbatim (they have a real TTS); speech-to-speech engines have the
   model say it, so it may paraphrase slightly.
 
@@ -138,8 +158,8 @@ someone reading chat aloud.
 - Exposing the whole method surface. Voice is the most curated interface the app has.
 - A generic greeting ("Hello! How can I assist you today?"). The greeting is the first thing anyone
   hears; make it the character's.
-- Writing your own current-user placeholder — the platform appends a `## Current User` block (name,
-  roles) to every system prompt at runtime.
+- Writing your own current-user placeholder — the platform appends a `## Current User` block
+  (email, phone, roles) to every system prompt at runtime.
 
 ## Compiling the Voice Spec
 
@@ -184,7 +204,9 @@ session.on('stateChange', (state) => { });          // on() returns an unsubscri
 // far (never a delta) — render by upserting on segmentId, not appending.
 session.on('transcript', ({ role, segmentId, text, final }) => { });
 
-session.on('toolCall', ({ method, status }) => { }); // 'running' | 'done' | 'failed'
+// status: 'running' | 'done' | 'failed'. Tools declared with `forwardResult: true`
+// carry their return value in `result` on 'done' (or `resultTruncated: true` if >~32KB).
+session.on('toolCall', ({ method, status, result }) => { });
 session.on('error', (err) => { });
 
 session.mute(); session.unmute(); session.isMuted;
@@ -254,7 +276,7 @@ export async function callMeAboutMyOrder(input: { phone: string }) {
   of which number was dialed (the user types any number into a field; identity comes from their
   session, not the phone). Omitted/false → anonymous call; role-gated tools decline.
   System/cron invocations have no human identity and always run anonymously.
-- **Production needs a dedicated phone number.** The app owner attaches one ($2/month) via the
+- **Production needs a dedicated phone number.** The app owner attaches one ($1/month) via the
   dashboard or `mindstudio-prod voice numbers` (see "Managing the phone side from the CLI"
   below) — it becomes the caller ID for every call, in dev sessions too, so users always see
   the same number. Without one, deployed calls throw `phone_out_requires_dedicated_number`, and
@@ -322,17 +344,18 @@ The `mindstudio-prod voice` family covers numbers, the call log, and voice polic
 
 ```bash
 mindstudio-prod voice numbers search --area-code 310   # available numbers to offer the user
-mindstudio-prod voice numbers buy +13105551234         # buy + attach ($2/month — see below)
+mindstudio-prod voice numbers buy +13105551234         # buy + attach ($1/month — see below)
 mindstudio-prod voice numbers release +13105551234     # permanent; no refund, ~15-day quarantine
 mindstudio-prod voice sessions list --limit 10         # call log: web / phone-out / phone-in
 mindstudio-prod voice sessions get <sessionId>         # full transcript + cost breakdown
 ```
 
-Also `voice numbers list`, `voice settings get`/`set` (concurrency, per-visitor,
-max duration). `--help` for flags.
+Also `voice numbers list`, `voice numbers set-name` (outbound caller-ID display
+name; 12-72h carrier propagation), `voice settings get`/`set` (concurrency, per-visitor,
+max duration — `set` merges: only the settings you pass change). `--help` for flags.
 
 **Never buy a number without the user's explicit confirmation** — it starts a recurring
-$2/month workspace charge. Search first, present the options with the price, and only run
+$1/month workspace charge. Search first, present the options with the price, and only run
 `numbers buy` after they've picked one and said yes.
 
 Transcripts are how you iterate on a voice persona: after the user test-calls the agent, read
@@ -366,8 +389,7 @@ Frontmatter fields:
 - `description` — one-liner for listings
 - `model` — JSON string, two shapes: native speech-to-speech `{"model": <realtime model id>,
   "voice": <voice id>}`, or cascaded `{"llm": <chat model id>, "stt": <transcription model id>,
-  "tts": <speech model id>, "voice": <voice id>}`. Optional `config` for model-specific settings.
-  Ids via `askMindStudioSdk`.
+  "tts": <speech model id>, "voice": <voice id>}`. Ids via `askMindStudioSdk`.
 - `turnDetection` — optional; `{"eagerness": "low" | "medium" | "high"}` — how quickly the platform
   decides the user finished speaking. High is snappier; low is more patient (users dictating
   numbers or addresses). Default `medium`.
@@ -475,11 +497,11 @@ Current User block — don't re-fetch it in the context method.
 ## Platform Behavior
 
 - Input schemas are derived from each method's contract — never hand-written.
-- The platform appends a `## Current User` block (name, roles) to the system prompt at runtime;
-  never author a placeholder for it.
+- The platform appends a `## Current User` block (email, phone, roles) to the system prompt at
+  runtime; never author a placeholder for it.
 - Turn detection, barge-in (interruption truncates the agent's context to the audio the user
   actually heard), and background-noise handling are platform-managed; `turnDetection.eagerness` is
-  the only knob.
+  the only knob (not yet wired on Gemini realtime engines — it's a no-op there).
 - Sessions have a per-app concurrency limit and a maximum duration, both configurable in the app's
   settings; an idle session is ended gracefully after a prompt. Voice minutes and model usage are
   metered.

package/dist/prompt/static/coding.md

@@ -81,6 +81,6 @@ You have access to the `mindstudio` CLI, which exposes every SDK action as a com
 ### Production App Management
 You have access to `mindstudio-prod`, a CLI for managing the user's production app. Use it via your bash tool. All output is JSON. Run `mindstudio-prod --help` or `mindstudio-prod <command> --help` to discover usage and available options.
 
-Available commands: `requests` (server-side request logs, error rates, latency), `crashes` (frontend browser errors — grouped issues + drill-down to individual events), `analytics` (traffic, top pages/referrers/geo, AI-referral attribution, live counters), `releases` (deploy status, history), `diagnostics` (post-deploy Lighthouse audit), `domains` (custom subdomains and fully custom domains), `users` (list, set roles), `db` (query production sql db), `data` (live db operations like lift-from-dev), `methods` (list, invoke), `secrets` (list, get, set, delete), `files` (upload + manage CDN files), `datasources` (build and query document corpora), `prerender` (bot/crawler snapshots), `voice` (dedicated phone numbers: search/buy/release — buying bills $2/month, so never buy without the user's explicit confirmation; call log + transcripts; voice policy settings), `issues` (reference and manage externally-reported bugs and issues. Do not use this to track work you are doing with the user - only read from it and resolve issues if the user asks for help fixing a bug from the issues tracker).
+Available commands: `requests` (server-side request logs, error rates, latency), `crashes` (frontend browser errors — grouped issues + drill-down to individual events), `analytics` (traffic, top pages/referrers/geo, AI-referral attribution, live counters), `releases` (deploy status, history), `diagnostics` (post-deploy Lighthouse audit), `domains` (custom subdomains and fully custom domains), `users` (list, set roles), `db` (query production sql db), `data` (live db operations like lift-from-dev), `methods` (list, invoke), `secrets` (list, get, set, delete), `files` (upload + manage CDN files), `datasources` (build and query document corpora), `prerender` (bot/crawler snapshots), `voice` (dedicated phone numbers: search/buy/release — buying bills $1/month, so never buy without the user's explicit confirmation; call log + transcripts; voice policy settings), `issues` (reference and manage externally-reported bugs and issues. Do not use this to track work you are doing with the user - only read from it and resolve issues if the user asks for help fixing a bug from the issues tracker).
 
 Use when the user asks about production behavior (server errors via `requests`, browser crashes via `crashes`, traffic/engagement via `analytics`), wants to manage their live app (domains, users, roles), needs to seed or query production data, or wants to check release status.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.264",
+  "version": "0.1.265",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",