syntaur 0.45.0 → 0.46.0

package/dist/launch/index.d.ts

@@ -226,6 +226,13 @@ interface HotkeyBindingsConfig {
     bindings: Partial<Record<BindableActionKind, string>>;
 }
 
+/**
+ * Automatic session tracking scope:
+ * - `all`: every discovered/hooked session is written to the sessions DB.
+ * - `workspaces-only`: only sessions whose cwd has `.syntaur/context.json`.
+ * - `off`: no automatic DB writes (manual `track-session` still works).
+ */
+type SessionAutoTrack = 'all' | 'workspaces-only' | 'off';
 interface SyntaurConfig {
     version: string;
     defaultProjectDir: string;
@@ -235,6 +242,9 @@ interface SyntaurConfig {
         autoApprove: boolean;
         autoCreateWorktree: AutoCreateWorktree;
     };
+    session: {
+        autoTrack: SessionAutoTrack;
+    };
     integrations: IntegrationConfig;
     backup: BackupConfig | null;
     statuses: StatusConfig | null;
@@ -280,6 +290,15 @@ interface LaunchPlan {
     shellFallbackWarning: string | null;
     /** Non-fatal launch-prompt token warnings (unknown/malformed `@`-tokens). */
     promptWarnings?: string[];
+    /**
+     * Session identity at launch time, for register-at-birth. `sessionId` is only
+     * known for resume-mode session launches; fresh/fork launches mint a NEW id
+     * inside the agent, so they carry `null` and rely on the pending runtime
+     * marker + scanner to close the gap. Absent on assignment launches.
+     */
+    session?: {
+        sessionId: string | null;
+    };
 }
 interface ResolveLaunchPlanInput {
     kind: 'assignment' | 'session';