@cline/core 0.0.80 → 0.0.81-nightly.1787893007

package/dist/services/providers/local-provider-service.d.ts

@@ -1,7 +1,7 @@
 import * as LlmsModels from "@cline/llms";
 import type { AddProviderActionRequest, ITelemetryService, ProviderCapability, ProviderListItem, ProviderModel, SaveProviderSettingsActionRequest, VoiceInputSelection } from "@cline/shared";
 import { type ProviderOAuthCredentials } from "../../auth/provider-auth-registry";
-import type { ProviderClient, ProviderConfig, ProviderProtocol, ProviderSettings } from "../../services/llms/provider-settings";
+import { type ProviderClient, type ProviderConfig, type ProviderProtocol, type ProviderSettings } from "../../services/llms/provider-settings";
 import type { ProviderTokenSource } from "../../types/provider-settings";
 import type { ProviderSettingsManager } from "../storage/provider-settings-manager";
 export { ensureCustomProvidersLoaded } from "./local-provider-registry";

package/dist/services/providers/provider-readiness.d.ts

@@ -0,0 +1,10 @@
+import type { ProviderConfig, ProviderSettings } from "../llms/provider-settings";
+/**
+ * Whether persisted provider settings hold enough real credentials or
+ * endpoint configuration for a turn to plausibly succeed. Unlike the mere
+ * existence of a settings entry (which migrations and empty "connect" saves
+ * can create), this requires provider-appropriate evidence: an API key or
+ * OAuth token, cloud credentials (AWS/GCP/Azure/SAP), a local-auth CLI, or a
+ * resolvable endpoint + model for keyless local providers.
+ */
+export declare function isProviderSettingsUsable(providerId: string, settings: ProviderSettings | undefined, config?: Pick<ProviderConfig, "baseUrl" | "modelId">): boolean;

package/dist/services/workspace/agent-schedules-workspace.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Ensure the home workspace for agent-created schedules exists and return its
+ * path. Agent-created schedules are user-level routines: they anchor (and
+ * their unattended sessions run) in `~/.cline/schedules/` instead of
+ * inheriting whichever chat workspace happened to create them, so they
+ * survive chat cleanup and stay in one predictable scope.
+ */
+export declare function ensureAgentSchedulesWorkspace(): Promise<string>;

package/dist/services/workspace/index.d.ts

@@ -1,3 +1,4 @@
+export { ensureAgentSchedulesWorkspace } from "./agent-schedules-workspace";
 export { ensureChatWorkspace } from "./chat-workspace";
 export type { FastFileIndexOptions } from "./file-indexer";
 export { getFileIndex, prewarmFileIndex } from "./file-indexer";

package/dist/session/models/session-manifest.d.ts

@@ -12,8 +12,8 @@ export declare const SessionManifestSchema: z.ZodObject<{
         completed: "completed";
         idle: "idle";
         running: "running";
-        pending: "pending";
         cancelled: "cancelled";
+        pending: "pending";
     }>;
     interactive: z.ZodBoolean;
     provider: z.ZodString;

package/dist/session/search/index.d.ts

@@ -0,0 +1 @@
+export * from "./session-history-search";

package/dist/session/search/session-history-search.d.ts

@@ -0,0 +1,51 @@
+import type { RuntimeHost } from "../../runtime/host/runtime-host";
+export interface SessionSearchInput {
+    query: string;
+    limit?: number;
+    workspaceRoot?: string;
+}
+export interface SessionSearchHit {
+    sessionId: string;
+    documentId: string;
+    ordinal: number;
+    role: string;
+    startedAt: string;
+    workspaceRoot: string;
+    title: string;
+    snippet: string;
+    score: number;
+}
+export interface SessionHistorySearchOptions {
+    dbPath?: string;
+    reconcileIntervalMs?: number;
+}
+export declare class SessionHistorySearchService {
+    private readonly host;
+    private readonly db;
+    private readonly initializationError;
+    private readonly intervalMs;
+    private readonly removedDuringRefresh;
+    private readonly failedEvictionSessionIds;
+    private timer;
+    private refreshPromise;
+    private readyPromise;
+    constructor(host: Pick<RuntimeHost, "listSessions" | "readSessionMessages">, options?: SessionHistorySearchOptions);
+    start(): void;
+    dispose(): Promise<void>;
+    refreshNow(): Promise<void>;
+    /**
+     * Removes one session from the derived index without scanning canonical
+     * history. The temporary tombstone prevents an in-flight reconciliation
+     * that captured the session before deletion from writing it back.
+     */
+    removeSession(sessionId: string): void;
+    waitUntilReady(): Promise<void>;
+    isAvailable(): boolean;
+    getInitializationError(): unknown | undefined;
+    search(input: SessionSearchInput): SessionSearchHit[];
+    private isSessionSuppressed;
+    private reconcile;
+    private sourceRevision;
+    private indexSession;
+    private deleteIndexedSession;
+}

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

@@ -48,8 +48,8 @@ export declare const TodoTaskInputSchema: z.ZodObject<{
     statuses: z.ZodOptional<z.ZodArray<z.ZodEnum<{
         failed: "failed";
         completed: "completed";
-        in_progress: "in_progress";
         cancelled: "cancelled";
+        in_progress: "in_progress";
         approved: "approved";
         pending_approval: "pending_approval";
         expired: "expired";

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

@@ -3,9 +3,9 @@ import { z } from "zod";
 import { type ScheduledTaskResult, type ScheduleTaskOperationOptions } from "../cron/service/schedule-tool";
 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.";
+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- Scheduled sessions run in the user's schedules home workspace, not this conversation's folder. Include absolute paths in the scheduled `prompt` for any project files or repositories the work must touch.\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 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 in the user's schedules home workspace, not this conversation's folder. Include the goal, constraints, expected output, and absolute paths for any project files or repositories the work must touch.\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";
@@ -53,8 +53,8 @@ export declare const TasksToolInputSchema: z.ZodDiscriminatedUnion<[z.ZodObject<
     statuses: z.ZodOptional<z.ZodArray<z.ZodEnum<{
         failed: "failed";
         completed: "completed";
-        in_progress: "in_progress";
         cancelled: "cancelled";
+        in_progress: "in_progress";
         approved: "approved";
         pending_approval: "pending_approval";
         expired: "expired";

package/dist/types/chat-schema.d.ts

@@ -25,8 +25,8 @@ export declare const ChatSessionStatusSchema: z.ZodEnum<{
     completed: "completed";
     idle: "idle";
     running: "running";
-    pending: "pending";
     cancelled: "cancelled";
+    pending: "pending";
     starting: "starting";
     stopping: "stopping";
 }>;
@@ -107,8 +107,8 @@ export declare const ChatViewStateSchema: z.ZodObject<{
         completed: "completed";
         idle: "idle";
         running: "running";
-        pending: "pending";
         cancelled: "cancelled";
+        pending: "pending";
         starting: "starting";
         stopping: "stopping";
     }>;

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@cline/core",
 	"description": "Cline Core SDK for Node Runtime",
-	"version": "0.0.80",
+	"version": "0.0.81-nightly.1787893007",
 	"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.80",
-		"@cline/shared": "0.0.80",
-		"@cline/llms": "0.0.80",
+		"@cline/agents": "0.0.81-nightly.1787893007",
+		"@cline/shared": "0.0.81-nightly.1787893007",
+		"@cline/llms": "0.0.81-nightly.1787893007",
 		"@modelcontextprotocol/sdk": "^1.29.0",
 		"@opentelemetry/api": "^1.9.0",
 		"@opentelemetry/api-logs": "^0.214.0",