@prohost/cli 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -4,6 +4,21 @@ Versions follow [semver](https://semver.org/). Publishing is automated: merging
 a version bump to `main` triggers `.github/workflows/npm-publish-cli.yml`, which
 builds via `prepack`, runs the suite, publishes, and tags `cli-v<version>`.
 
+## 0.8.1
+
+A long message no longer reaches a paired agent as a fragment it can't recover.
+
+- **Clipped trigger text is called out.** When the server reports that the
+  message that woke the agent was clipped (`trigger.text_truncated: true`, new
+  in the run event), the prompt says so and, when the agent has ProhostAI tools
+  and a conversation, tells it to read the full message with
+  `get_conversation_messages` before answering. An agent without tools is told
+  to say the message reached it truncated instead of answering the fragment.
+  Keyed on the explicit flag, never on a trailing `…` a person could have typed;
+  a server that predates the flag reads as "not clipped". Pairs with the server raising the excerpt
+  cap from 500 to 16,000 characters and returning full message bodies from
+  `get_conversation_messages`, so this path is now rare.
+
 ## 0.8.0
 
 A paired agent woken as a bystander can now stay silent.

package/dist/agent/contract.d.ts

@@ -235,6 +235,12 @@ export interface AgentRunRequest {
     trigger_message_id?: string;
     /** Capped inline excerpt of the message that woke the agent. */
     trigger_text?: string;
+    /**
+     * The server clipped `trigger_text` (`trigger.text_truncated`). Explicit
+     * metadata rather than a guess from a trailing ellipsis, which a person can
+     * also type. Absent on servers that predate it — read as "not clipped".
+     */
+    trigger_text_truncated?: boolean;
     /**
      * Images and files on the message that woke the agent.
      *

package/dist/agent/contract.js

@@ -337,6 +337,8 @@ export function parseRunRequest(data) {
         trigger_source: str(trigger.source) ?? str(data.trigger_source),
         trigger_message_id: str(trigger.message_id),
         trigger_text: str(trigger.text_excerpt),
+        // Only an explicit `true` counts: anything else is an unclipped message.
+        trigger_text_truncated: trigger.text_truncated === true,
         trigger_attachments: attachmentList(trigger.attachments ?? data.trigger_attachments),
         trigger_user_id: str(trigger.user_id),
         trigger_brief: brief(trigger.brief),

package/dist/agent/prompt.js

@@ -207,6 +207,23 @@ export function buildPrompt(run, context) {
         // The server caps this excerpt, so say so rather than let an agent assume
         // it has the whole message.
         lines.push('Message that woke you (may be truncated by the server):', run.trigger_text, '');
+        // An agent that is only told the text "may be" truncated answers the
+        // fragment — or asks the sender to repost — when the whole message is one
+        // tool call away. Keyed on the server's explicit flag, never on a trailing
+        // ellipsis a person could have typed.
+        if (run.trigger_text_truncated) {
+            lines.push(...(context.mcpServerName && run.conversation_id
+                ? [
+                    'ProhostAI cut that message short. Before answering, read it in full with',
+                    `the ProhostAI get_conversation_messages tool (conversation ${run.conversation_id})`,
+                    'and answer the whole message, not the excerpt above.',
+                ]
+                : [
+                    'ProhostAI cut that message short, and you have no tool to read the rest.',
+                    'Answer what you can see and say plainly that the message reached you',
+                    'truncated.',
+                ]), '');
+        }
     }
     else if (triggerAttachments.length > 0) {
         // Distinct from "the server didn't send the text": here the message really

package/dist/version.d.ts

@@ -7,6 +7,6 @@
  * `package.json`, so a release bump that forgets this file fails the suite
  * instead of shipping a `User-Agent` that lies about which build is calling.
  */
-export declare const CLI_VERSION = "0.8.0";
+export declare const CLI_VERSION = "0.8.1";
 /** Sent on every HTTP request the CLI makes back into ProhostAI. */
-export declare const USER_AGENT = "prohost-cli/0.8.0";
+export declare const USER_AGENT = "prohost-cli/0.8.1";

package/dist/version.js

@@ -7,6 +7,6 @@
  * `package.json`, so a release bump that forgets this file fails the suite
  * instead of shipping a `User-Agent` that lies about which build is calling.
  */
-export const CLI_VERSION = '0.8.0';
+export const CLI_VERSION = '0.8.1';
 /** Sent on every HTTP request the CLI makes back into ProhostAI. */
 export const USER_AGENT = `prohost-cli/${CLI_VERSION}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prohost/cli",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "description": "Run your own AI agent as a ProhostAI teammate, and stream your account's webhooks to your laptop.",
   "type": "module",
   "license": "MIT",