@dimi-agent/cli 0.6.2 → 0.6.4

package/dist/main.mjs

@@ -123100,7 +123100,7 @@ var init_waitService = __esmMin((() => {
 //#region ../../packages/agent-core-v2/src/agent/tools/wait-for/wait-for.md?raw
 var wait_for_default;
 var init_wait_for = __esmMin((() => {
-	wait_for_default = "Wait for a future notification when no independent work remains. Provide a concise reason and an optional timeout in seconds. The default is 60 seconds; use longer waits only for clearly long-running work, up to 1800 seconds.\n\nCall WaitFor by itself. It waits on the current agent, not a specific task. Any later notification wakes the agent. A timeout wakes the agent with an explicit `wait_expired` message and never cancels background work.\n";
+	wait_for_default = "Wait for a future notification when no independent work remains. Provide a concise reason and an optional timeout in seconds. The default is 60 seconds; use longer waits only for clearly long-running work, up to 1800 seconds.\n\nCall WaitFor by itself. It waits on the current agent, not a specific task. Any later notification wakes the agent. A timeout wakes the agent with an explicit `wait_expired` message and never cancels background work.\n\nWhen you are waiting on an external state that can change on its own (a file being written, a service coming up, a process finishing, a remote resource becoming ready, …), do not just park on a timeout and re-check later. Start a background Bash task that polls exactly the part of that state you care about and exits as soon as it changes — for example a loop that checks every few seconds and breaks on the expected condition, printing what changed. Because a finished background task notifies the agent, the wait then wakes you the moment the state flips instead of on a blind timeout, and you can act immediately. Keep the polling script narrowly scoped to the monitored condition and make sure it terminates on its own (or after the wait timeout); do not leave a watcher running forever.\n";
 }));
 //#endregion
 //#region ../../packages/agent-core-v2/src/agent/tools/wait-for/waitForTool.ts
@@ -224811,17 +224811,22 @@ var init_sdk_rpc_client = __esmMin((() => {
 		}
 		/**
 		* Build one canonical v2 resume snapshot from the live restored scopes.
-		* Replay is the restored context history; task and todo state come from
-		* their owning services instead of a second pass over the wire journal.
+		* Replay is the full message history folded from the agent's wire journal —
+		* NOT the live context memory, which after a compaction collapses into
+		* `[...keptUserMessages, compaction_summary]` and would lose the compacted
+		* prefix. `context` keeps the folded (live) context for token accounting;
+		* task and todo state come from their owning services instead of a second
+		* pass over the wire journal.
 		*/
 		async resumedAgentState(session, agent, type, replayTurnLimit) {
 			const facade = this.klient.session(session.id).agent(agent.id);
 			const ctx = session.accessor.get(ISessionContext);
-			const [context, plan, usage, tasks] = await Promise.all([
+			const [context, plan, usage, tasks, replay] = await Promise.all([
 				facade.getContext(),
 				facade.getPlan(),
 				facade.getUsage(),
-				facade.getTasks({ activeOnly: false })
+				facade.getTasks({ activeOnly: false }),
+				this.buildReplayFromWire(agent)
 			]);
 			const profile = agent.accessor.get(IAgentProfileService).data();
 			return {
@@ -224835,11 +224840,7 @@ var init_sdk_rpc_client = __esmMin((() => {
 					systemPrompt: profile.systemPrompt
 				},
 				context,
-				replay: limitAgentReplayByTurns(context.history.map((message, time) => ({
-					type: "message",
-					message,
-					time
-				})), replayTurnLimit),
+				replay: limitAgentReplayByTurns(replay, replayTurnLimit),
 				permission: {
 					mode: agent.accessor.get(IAgentPermissionModeService).mode,
 					rules: [...agent.accessor.get(IAgentPermissionRulesService).rules]
@@ -224853,6 +224854,63 @@ var init_sdk_rpc_client = __esmMin((() => {
 			};
 		}
 		/**
+		* Fold the agent's full message history from its wire journal.
+		*
+		* The wire journal is the source of truth for message history: it keeps
+		* every `context.append_message` / `context.append_loop_event` record, and
+		* a `context.apply_compaction` record only marks a compaction point instead
+		* of rewriting the past. Folding it yields the complete pre-compaction
+		* history with a summary marker at each compaction, which is what replay
+		* should render. The live context memory (`facade.getContext()`) is the
+		* model's folded context and is deliberately NOT used here — it would hide
+		* everything compacted away.
+		*/
+		async buildReplayFromWire(agent) {
+			await agent.accessor.get(IWireService).flush();
+			const scope = agent.accessor.get(IAgentScopeContext).scope();
+			const reducer = createContextTranscriptReducer();
+			const applyCompactionRecords = [];
+			for await (const record of this.engineAccessor.get(IAppendLogStore).read(scope, AGENT_WIRE_RECORD_KEY)) {
+				if (record.type === "context.apply_compaction") applyCompactionRecords.push(record);
+				reducer.add(record);
+			}
+			const { entries, times } = reducer.result();
+			const replay = [];
+			let compactionIndex = 0;
+			for (let i = 0; i < entries.length; i++) {
+				const message = entries[i];
+				const time = times[i];
+				if (message.origin?.kind === "compaction_summary") {
+					const record = applyCompactionRecords[compactionIndex];
+					compactionIndex += 1;
+					if (record !== void 0) {
+						const compaction = readContextCompactionRecord(record);
+						replay.push({
+							type: "compaction",
+							result: {
+								summary: compaction.summary,
+								contextSummary: compaction.contextSummary,
+								compactedCount: compaction.compactedCount,
+								tokensBefore: compaction.tokensBefore,
+								tokensAfter: compaction.tokensAfter,
+								keptUserMessageCount: compaction.keptUserMessageCount,
+								keptHeadUserMessageCount: compaction.keptHeadUserMessageCount,
+								droppedCount: compaction.droppedCount
+							},
+							time: time ?? 0
+						});
+						continue;
+					}
+				}
+				replay.push({
+					type: "message",
+					message,
+					time: time ?? 0
+				});
+			}
+			return replay;
+		}
+		/**
 		* Every v2 workspace-id bucket addressing `workDir` (already normalized):
 		* the registered workspace's alias set when the catalog knows the root, or
 		* the freshly minted bucket key for index-only sessions (mirrors how v1's
@@ -386883,6 +386941,10 @@ var init_session_replay = __esmMin((() => {
 				return;
 			}
 			if (message.origin?.kind === "injection") return;
+			if (message.origin?.kind === "compaction_summary") {
+				this.renderCompactionSummary(context, message);
+				return;
+			}
 			if (message.origin?.kind === "task") {
 				this.flushAssistant(context);
 				const info = this.host.sessionEventHandler.backgroundTasks.get(message.origin.taskId);
@@ -387051,6 +387113,21 @@ var init_session_replay = __esmMin((() => {
 				}
 			});
 		}
+		/**
+		* Render a `compaction_summary` user message folded into the model context
+		* (the resume snapshot's context history carries it after compaction). The
+		* message text is the model-facing summary; token counts are unknown here,
+		* so only the summary is surfaced. The snapshot is still rebuilt from the
+		* wire journal on resume (see `resumedAgentState`), so this branch is a
+		* fallback for snapshots that were built from a folded context.
+		*/
+		renderCompactionSummary(context, message) {
+			this.flushAssistant(context);
+			this.host.appendTranscriptEntry({
+				...replayEntry(context, "status", "Compaction complete", "plain"),
+				compactionData: { summary: contentPartsToText(message.content) }
+			});
+		}
 		renderHookResult(context, message) {
 			if (message.origin?.kind !== "hook_result") return;
 			this.flushAssistant(context);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dimi-agent/cli",
-  "version": "0.6.2",
+  "version": "0.6.4",
   "description": "The Starting Point for Next-Gen Agents",
   "keywords": [
     "agent",
@@ -60,11 +60,11 @@
     "tsx": "^4.21.0",
     "yazl": "^3.3.1",
     "zod": "^4.3.6",
+    "@dimi-agent/agent-core-v2": "^0.1.0",
     "@dimi-agent/dimi-oauth": "^0.1.0",
     "@dimi-agent/dimi-sdk": "^0.2.0",
-    "@dimi-agent/dimi-web": "^0.1.0",
-    "@dimi-agent/agent-core-v2": "^0.1.0",
     "@dimi-agent/dimi-telemetry": "^0.1.0",
+    "@dimi-agent/dimi-web": "^0.1.0",
     "@dimi-agent/kap-server": "^0.1.0",
     "@dimi-agent/pi-tui": "^0.1.0",
     "@dimi-agent/remote": "^0.1.0"