@primitivedotdev/cli 0.31.8 → 0.32.0

package/dist/oclif/index.js

@@ -14560,6 +14560,8 @@ function buildCommand(kind, description, argv, options = {}) {
 }
 function buildChatFollowUpCommands(context) {
 	const commands = [];
+	const hasCustomStrictPhase = context.strictPhaseSeconds !== DEFAULT_STRICT_PHASE_SECONDS;
+	const shouldPreferStrictContinuation = context.strictOnly || context.matchStrategy === "strict" && !hasCustomStrictPhase;
 	const continueParts = [
 		"primitive",
 		"chat",
@@ -14575,8 +14577,8 @@ function buildChatFollowUpCommands(context) {
 	];
 	if (context.json) continueParts.push("--json");
 	if (context.quiet) continueParts.push("--quiet");
-	if (context.strictOnly) continueParts.push("--strict-only");
-	else if (context.strictPhaseSeconds !== DEFAULT_STRICT_PHASE_SECONDS) continueParts.push("--strict-phase-seconds", String(context.strictPhaseSeconds));
+	if (shouldPreferStrictContinuation) continueParts.push("--strict-only");
+	else if (hasCustomStrictPhase) continueParts.push("--strict-phase-seconds", String(context.strictPhaseSeconds));
 	commands.push(buildCommand("continue_chat", "Continue this chat", continueParts, { requiresMessage: true }));
 	commands.push(buildCommand("reply_direct", "Reply directly to the inbound email", [
 		"primitive",
@@ -14685,7 +14687,7 @@ function formatChatResponse(context) {
 	];
 	if (context.reply.reply_to_sent_email_id) lines.push(`  Reply to sent email id: ${context.reply.reply_to_sent_email_id}`);
 	if (context.reply.message_id) lines.push(`  Message-Id: ${context.reply.message_id}`);
-	lines.push("", "Helpful follow-up commands", "  Replace <message> before running commands that include it.", "  Commands are templates; use --json for parse-safe output.");
+	lines.push("", "Helpful follow-up commands", "  Replace <message> before running commands that include it.", "  Commands are templates; use --json for parse-safe output.", "  When shown, --strict-only prefers timing out over matching the wrong reply.");
 	for (const { description, command } of buildChatFollowUpCommands(context)) lines.push(`  ${description}:`, `    ${command}`);
 	lines.push("", `Response body (${responseBody.format}; use --json for parsing)`, "----- BEGIN RESPONSE -----", responseBody.body || "(empty response)", "----- END RESPONSE -----");
 	return lines.join("\n");
@@ -14785,9 +14787,10 @@ var ChatCommand = class ChatCommand extends Command {
   --strict-only is not set, it falls back to a weaker sender/time
   window match: from=<recipient>, to=<sender>, and since=<send time>.
   The fallback can catch clients that strip threading headers, but it
-  is less exact than strict matching. Progress is written to stderr
-  while the CLI waits. Exits non-zero on timeout and prints recovery
-  commands when the send succeeded but no reply was returned.`;
+  is less exact than strict matching. Use --strict-only when matching
+  the wrong reply is worse than timing out. Progress is written to
+  stderr while the CLI waits. Exits non-zero on timeout and prints
+  recovery commands when the send succeeded but no reply was returned.`;
 	static summary = "Chat with an agent over email (send and wait for the reply)";
 	static examples = [
 		"<%= config.bin %> chat help@agent.acme.dev 'how do I rotate my API key?'",
@@ -14836,7 +14839,7 @@ var ChatCommand = class ChatCommand extends Command {
 			description: "Seconds to wait in strict-threading mode (filter by reply_to_sent_email_id) before falling back to time-window matching. Set to the full --timeout to disable the fallback; --strict-only is the explicit way to do that.",
 			min: 1
 		}),
-		"strict-only": Flags.boolean({ description: "Disable the time-window fallback. Only accept inbounds whose threading headers (In-Reply-To / References) resolve to this send. Recommended when correctness matters more than success rate (e.g. agents talking to agents)." }),
+		"strict-only": Flags.boolean({ description: "Disable the time-window fallback. Only accept inbounds whose threading headers (In-Reply-To / References) resolve to this send. Use when matching the wrong reply is worse than timing out." }),
 		interval: Flags.integer({
 			default: 2,
 			description: "Seconds between polls while waiting for the reply.",
@@ -16765,8 +16768,8 @@ const PRIMITIVE_TEAM_AUTHOR = {
 	name: "Primitive Team",
 	url: "https://primitive.dev"
 };
-const SDK_VERSION_RANGE = "^0.31.1";
-const CLI_VERSION_RANGE = "^0.31.1";
+const SDK_VERSION_RANGE = "^0.32.0";
+const CLI_VERSION_RANGE = "^0.32.0";
 const ESBUILD_VERSION_RANGE = "^0.27.0";
 function renderHandler() {
 	return `// env.PRIMITIVE_API_KEY, env.PRIMITIVE_WEBHOOK_SECRET, and
@@ -19955,6 +19958,7 @@ const CANONICAL_OPERATION_ALIASES = {
 	"sending:send": "sending:send-email",
 	"sent:get": "sending:get-sent-email",
 	"sent:list": "sending:list-sent-emails",
+	"threads:get": "threads:get-thread",
 	"webhook-deliveries:list": "webhook-deliveries:list-deliveries",
 	"webhook-deliveries:replay": "webhook-deliveries:replay-delivery"
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@primitivedotdev/cli",
-  "version": "0.31.8",
+  "version": "0.32.0",
   "description": "Official Primitive CLI: deploy Primitive Functions, send and inspect mail, manage endpoints, all from the terminal. Wraps the @primitivedotdev/sdk runtime client with one-shot commands.",
   "type": "module",
   "sideEffects": false,
@@ -67,7 +67,7 @@
         "description": "Short aliases for outbound sent-email history: `primitive sent list` and `primitive sent get`."
       },
       "threads": {
-        "description": "Inspect conversation threads spanning received and sent emails: `primitive threads get --id <thread-id>`."
+        "description": "Inspect conversation threads spanning received and sent emails. Prefer `primitive threads get --id <thread-id>`; generated API name `primitive threads get-thread --id <thread-id>` remains available."
       },
       "endpoints": {
         "description": "Manage webhook endpoints that receive email events"