Back to Signal Feed
CodeTracked since May 18, 2026

Make launch concurrency safe with explicit session IDs

In v1.9.15, the launch path was fixed so session persistence is safe when multiple launches happen in parallel and the launch command now returns a session ID, preventing ambiguous or lost session tracking in automation.

agent-decklaunchsession persistencesession ID

What Happened

  • In v1.9.15, the launch path was fixed so session persistence is safe when multiple launches happen in parallel and the launch command now returns a session ID, preventing ambiguous or lost session tracking in automation.
  • In v1.9.15, the launch path was fixed so session persistence is safe when multiple launches happen in parallel and the launch command now returns a session ID, preventing ambiguous or lost session tracking in automation.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added a concurrency-safe launch flow that serializes/guards session-state writes and returns the created session identifier from launch, turning session start into a reliable, script-friendly operation.

Why Track This

Why It Matters

Operators and automation scripts that start multiple Agent Deck sessions can now avoid session mix-ups and state loss by reading a returned session ID immediately, which lowers retry churn and makes parallel orchestration more dependable; watch whether high-concurrency workflows still show session state gaps or stale identifiers.

Impact

Operators and automation scripts that start multiple Agent Deck sessions can now avoid session mix-ups and state loss by reading a returned session ID immediately, which lowers retry churn and makes parallel orchestration more dependable; watch whether high-concurrency workflows still show session state gaps or stale identifiers.

What To Watch Next

  • Watch whether agent-deck becomes a repeated pattern.
  • Track follow-up changes around Agent Planning and Control.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: parallel_launch_state_contention, session_id_capture_in_custom_scripts.
Open Topic TimelineOpen Technical EventOpen Original Sourceparallel_launch_state_contention / session_id_capture_in_custom_scripts / state_file_cleanup_after_failures

Supporting Evidence

GITHUB RELEASEHigh Trust

v1.9.15

fix(launch): parallel-safe persistence + return session ID (closes #1031) (#1032)