@cline/core 0.0.78 → 0.0.79-nightly.1787712192

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

@@ -117,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/tasks/agenda-task-manager.d.ts

@@ -24,6 +24,12 @@ export interface AgendaTaskManagerOptions {
     globalSpecsDir?: string;
     watcherDebounceMs?: number;
     watchFiles?: boolean;
+    /**
+     * Set to false to keep the automation pump idle regardless of persisted
+     * automation policies. Policies stay stored untouched and manual approve/run
+     * commands keep working; nothing is auto-approved or auto-started.
+     */
+    automationEnabled?: boolean;
     logger?: BasicLogger;
     publish?: (event: AgendaTaskManagerEventName, payload: Record<string, unknown>, sessionId?: string) => void;
 }
@@ -42,6 +48,7 @@ export declare class AgendaTaskManager implements AgendaTaskManagerApi {
     private readonly backgroundRuns;
     private maintenanceTimer?;
     private readonly queuedAutomationScopes;
+    private readonly automationEnabled;
     private automationPumping;
     private automationPolicyGeneration;
     private started;

package/dist/tasks/task-tool.d.ts

@@ -4,6 +4,8 @@ import { type ScheduledTaskResult, type ScheduleTaskOperationOptions } from "../
 import { type TodoTaskOperationOptions, type TodoTaskResult } from "./agenda-task-tool";
 export declare const TASKS_TOOL_NAME = "tasks";
 export declare const TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool to manage durable Todo items and explicitly requested scheduled agent work.\n\n- Use `kind: \"todo\"` for meaningful follow-ups, handoffs, ideas, reminders, and other work that should remain visible after this session. This includes useful work you identify and suggest proactively. Agent-created Todos require user approval; Todos created directly by the user are approved immediately. Todo `available_at` controls availability in the list; it never schedules execution.\n- Use `kind: \"scheduled\"` only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and may include an IANA `timezone`.\n- \"Remind me\" is ambiguous: ask whether the user wants a reviewed Todo note or an agent to execute work at that time when intent is unclear.\n- Never create both kinds for the same request unless the user explicitly requests both. Check existing items before creating a likely duplicate.\n- Todo instructions and scheduled prompts must be self-contained. Include the goal, constraints, relevant project context, and expected output.\n- Never approve or start a Todo yourself. Only mutate schedules from an interactive user session, and only update, pause, resume, delete, or run one immediately when the user asks.";
+/** Guidance used while the Todo kind is disabled and only schedules remain. */
+export declare const SCHEDULED_TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. Always pass `kind: \"scheduled\"`.\n\n- One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and may include an IANA `timezone`.\n- Never create a schedule proactively. Check existing schedules before creating a likely duplicate.\n- Make the scheduled `prompt` self-contained because it runs in a new unattended session. Include the goal, constraints, relevant project context, and expected output.\n- Only update, pause, resume, delete, or run a schedule immediately when the user asks for that action.";
 export declare const TasksToolInputSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
     operation: z.ZodEnum<{
         update: "update";
@@ -121,7 +123,12 @@ export type TasksToolResult = ({
     };
 };
 export interface CreateTasksToolOptions {
-    todo: TodoTaskOperationOptions;
+    /**
+     * Omit to disable the Todo kind: the tool then advertises and accepts only
+     * `kind: "scheduled"` while the Agenda backend stays intact for hosts that
+     * re-enable it.
+     */
+    todo?: TodoTaskOperationOptions;
     scheduled: ScheduleTaskOperationOptions;
 }
 /**
@@ -131,4 +138,6 @@ export interface CreateTasksToolOptions {
  */
 export declare function createTasksTool(options: CreateTasksToolOptions): AgentTool<TasksToolInput, TasksToolResult>;
 /** Adds selection and safety guidance only when the unified tool is enabled. */
-export declare function createTasksPromptExtension(): AgentExtension;
+export declare function createTasksPromptExtension(options?: {
+    todoEnabled?: boolean;
+}): AgentExtension;

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.78",
+	"version": "0.0.79-nightly.1787712192",
 	"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.78",
-		"@cline/shared": "0.0.78",
-		"@cline/llms": "0.0.78",
+		"@cline/agents": "0.0.79-nightly.1787712192",
+		"@cline/shared": "0.0.79-nightly.1787712192",
+		"@cline/llms": "0.0.79-nightly.1787712192",
 		"@modelcontextprotocol/sdk": "^1.29.0",
 		"@opentelemetry/api": "^1.9.0",
 		"@opentelemetry/api-logs": "^0.214.0",