@cline/core 0.0.77 → 0.0.79

package/dist/runtime/host/local-runtime-host.d.ts

@@ -42,6 +42,7 @@ export declare class LocalRuntimeHost implements RuntimeHost {
     private readonly providerSettingsManager;
     private readonly oauthTokenManager;
     private readonly defaultTelemetry?;
+    private readonly distinctId;
     private readonly defaultLogger?;
     private readonly defaultFetch?;
     private readonly events;
@@ -116,13 +117,40 @@ export declare class LocalRuntimeHost implements RuntimeHost {
      * `attempt_completion`-driven emission and works for both interactive
      * and non-interactive sessions.
      *
-     * `shutdownSession(...)` retains a fallback emission for completed
-     * sessions that finish without an explicit completion-tool observation
-     * (e.g., non-interactive runs not using the yolo preset). This helper
-     * sets `submitAndExitObserved` so the shutdown fallback can suppress a
+     * `emitTaskCompletedOnTeardown(...)` retains a fallback emission for
+     * completed sessions that finish without an explicit completion-tool
+     * observation (e.g., non-interactive runs not using the yolo preset,
+     * or hosts that disable `submit_and_exit` entirely). This helper sets
+     * `taskCompletedEmitted` so the teardown fallback can suppress a
      * duplicate emission for the same logical completion.
      */
     private observeTaskCompletionTool;
+    /**
+     * Single choke point for the fallback `task.completed` emission on
+     * session teardown. Every path a session can end through funnels into
+     * `shutdownSession(...)` or `releaseSessionRuntime(...)`, and BOTH must
+     * call this helper — the emission must never depend on which teardown
+     * branch a stop happens to route through. (The 4.1.11 regression:
+     * truthful session-status reporting re-routed many interactive stops
+     * onto the release branch, and the fallback that lived only inside
+     * `shutdownSession` silently stopped firing for them.)
+     *
+     * Emits at most once per session (`taskCompletedEmitted`), and never
+     * after the `submit_and_exit` observer already reported the completion.
+     * The completion criterion deliberately does not read `session.status`
+     * (whose lifecycle is what changed in 4.1.11):
+     *
+     * - Interactive sessions use the recorded final-turn outcome,
+     *   `lastInteractiveTurnFinishReason === "completed"`. The extra guards
+     *   suppress emission when teardown arrives mid-run (the in-flight turn
+     *   being aborted is the real final turn, and it did not complete).
+     * - Non-interactive sessions use the terminal status their run result
+     *   resolved to (`finalStatus`, from `finalizeSingleRun`), preserving
+     *   the pre-existing `input.status === "completed"` semantics.
+     *
+     * Sessions whose final turn errored or aborted emit nothing.
+     */
+    private emitTaskCompletedOnTeardown;
     private prepareTurnInput;
     private ensureSessionPersisted;
     private markTurnRunning;

package/dist/runtime/orchestration/session-runtime.d.ts

@@ -32,6 +32,11 @@ export interface BuiltRuntime {
 }
 export interface RuntimeBuilderInput {
     config: CoreSessionConfig;
+    /**
+     * Host-resolved stable end-user identity, forwarded so delegated agents
+     * (sub-agents / teammates) emit the same telemetry `userId` as the lead.
+     */
+    distinctId?: string;
     hooks?: AgentHooks;
     extensions?: AgentConfig["extensions"];
     onTeamEvent?: (event: TeamEvent) => void;

package/dist/types/session.d.ts

@@ -47,14 +47,21 @@ export type ActiveSession = {
      *    declares completion (parity with original Cline's
      *    `attempt_completion`).
      * 2. Suppress the fallback `task.completed` emission from
-     *    `shutdownSession(...)` so the same logical completion is not
-     *    reported twice.
+     *    `emitTaskCompletedOnTeardown(...)` so the same logical completion
+     *    is not reported twice.
      *
      * Non-interactive sessions that finish without ever calling the
-     * completion tool still receive a `task.completed` from the shutdown
+     * completion tool still receive a `task.completed` from the teardown
      * fallback.
      */
     submitAndExitObserved: boolean;
+    /**
+     * Set to `true` the moment `task.completed` is emitted for this session,
+     * whether by the `submit_and_exit` observer or by the teardown fallback
+     * (`emitTaskCompletedOnTeardown`). Enforces the invariant of exactly one
+     * `task.completed` per session regardless of which teardown path runs.
+     */
+    taskCompletedEmitted: boolean;
 };
 export type PendingPrompt = {
     id: string;

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@cline/core",
 	"description": "Cline Core SDK for Node Runtime",
-	"version": "0.0.77",
+	"version": "0.0.79",
 	"repository": {
 		"type": "git",
 		"url": "https://github.com/cline/cline",
@@ -49,9 +49,9 @@
 		"test:watch": "vitest --config vitest.config.ts"
 	},
 	"dependencies": {
-		"@cline/agents": "0.0.77",
-		"@cline/shared": "0.0.77",
-		"@cline/llms": "0.0.77",
+		"@cline/agents": "0.0.79",
+		"@cline/shared": "0.0.79",
+		"@cline/llms": "0.0.79",
 		"@modelcontextprotocol/sdk": "^1.29.0",
 		"@opentelemetry/api": "^1.9.0",
 		"@opentelemetry/api-logs": "^0.214.0",