@addai/node 0.30.16-msp.0 → 0.30.16-msp.10

package/dist/time-context.d.ts

@@ -3,6 +3,16 @@
  * omit them to get the machine clock and zone at spawn time.
  */
 export declare function currentTimeBlock(now?: Date, timeZone?: string): string;
+/**
+ * The block for a chat that resumes. Claude reuses a conversation's first system
+ * prompt on every later turn, so a "now" written here goes stale, and the model
+ * would believe it over the message in front of it. Every chat message carries
+ * its own UTC time, so this says to use that, and keeps only what stays true:
+ * where the entity is running and that zone's offset.
+ */
+export declare function chatTimeBlock(now?: Date, timeZone?: string): string;
+/** appendTimeContext for a chat turn; see chatTimeBlock. */
+export declare function appendChatTimeContext(systemPrompt: string | null | undefined, now?: Date, timeZone?: string): string;
 /**
  * Append the time block to a request's system prompt (or stand alone when the
  * request has none). Used at every agent spawn site in session-runner.

package/dist/time-context.js

@@ -13,6 +13,8 @@
 // Each request is a fresh CLI invocation, so the block is per-turn fresh.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.currentTimeBlock = currentTimeBlock;
+exports.chatTimeBlock = chatTimeBlock;
+exports.appendChatTimeContext = appendChatTimeContext;
 exports.appendTimeContext = appendTimeContext;
 function machineTimeZone() {
     try {
@@ -60,6 +62,35 @@ function currentTimeBlock(now = new Date(), timeZone = machineTimeZone()) {
         'Timestamps on chat messages, records and logs may be stored in UTC — convert them to this timezone before repeating them to users. Never read a UTC timestamp as if it were local time.',
     ].join('\n');
 }
+/**
+ * The block for a chat that resumes. Claude reuses a conversation's first system
+ * prompt on every later turn, so a "now" written here goes stale, and the model
+ * would believe it over the message in front of it. Every chat message carries
+ * its own UTC time, so this says to use that, and keeps only what stays true:
+ * where the entity is running and that zone's offset.
+ */
+function chatTimeBlock(now = new Date(), timeZone = machineTimeZone()) {
+    let tz = timeZone;
+    let fmt;
+    try {
+        fmt = formatParts(now, tz);
+    }
+    catch {
+        tz = 'UTC';
+        fmt = formatParts(now, tz);
+    }
+    return [
+        '## Current date & time',
+        `For the current time, use the time in the header of the newest message, which is in UTC. These instructions were written at ${fmt.stamp} ${fmt.zone} and can be hours or days old in a long chat, so only fall back on that if a message has no time.`,
+        `Local time where you are running is ${tz} (${fmt.offset} when this was written). Convert UTC times from messages, records and logs to it before telling people a time. Never read a UTC timestamp as if it were local time.`,
+    ].join('\n');
+}
+/** appendTimeContext for a chat turn; see chatTimeBlock. */
+function appendChatTimeContext(systemPrompt, now, timeZone) {
+    const block = chatTimeBlock(now, timeZone);
+    const sp = (systemPrompt ?? '').trim();
+    return sp ? `${systemPrompt}\n\n${block}` : block;
+}
 /**
  * Append the time block to a request's system prompt (or stand alone when the
  * request has none). Used at every agent spawn site in session-runner.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@addai/node",
-  "version": "0.30.16-msp.0",
+  "version": "0.30.16-msp.10",
   "description": "Daemon that pairs a machine with your +Ai account and runs Claude / Codex / Kimi / Gemini agents on its behalf. Reachable via Supabase from Vault, Entity Studio, or any other +Ai surface.",
   "license": "MIT",
   "keywords": [