Back to Signal Feed
CodeTracked since May 19, 2026

agent-deck adds session-aware Copilot CLI resume and config support

Upgrades Copilot integration from one-off pattern-based starts to a session-aware flow by detecting existing Copilot sessions on disk, resuming them automatically, and wiring model/allow-all configuration into Copilot startup.

agent-deckCopilot CLIsession-state/events.jsonlcopilot_hooks.go

What Happened

  • Upgrades Copilot integration from one-off pattern-based starts to a session-aware flow by detecting existing Copilot sessions on disk, resuming them automatically, and wiring model/allow-all configuration into Copilot startup.
  • Upgrades Copilot integration from one-off pattern-based starts to a session-aware flow by detecting existing Copilot sessions on disk, resuming them automatically, and wiring model/allow-all configuration into Copilot startup.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Introduced a new Copilot session hook path that reads `~/.copilot/session-state/<session-id>/events.jsonl` for `session.start` records matching the working directory and starts Copilot with `--resume <session-id>` when prior conversation exists, while propagating session IDs through tmux and adding per-instance/TOML-driven `model` and `allow_all` startup options.

Why Track This

Why It Matters

Developers and operators using Copilot inside agent-deck can continue ongoing AI coding sessions across restarts and pane boundaries without manual reinitialization, so long workflows keep context and reduce wasted prompt cycles; this is important to watch next because the new file-based discovery can still resume the wrong or stale session if session state files are incomplete, duplicated, or mismatched to the active project. The implementation also adds a config-based model/allow-all path (`~/.agent-deck.toml` and instance fields), so verify that non-standard install paths (`COPILOT_CONFIG_DIR`) and tmux environment propagation keep session IDs isolated per instance.

Impact

Developers and operators using Copilot inside agent-deck can continue ongoing AI coding sessions across restarts and pane boundaries without manual reinitialization, so long workflows keep context and reduce wasted prompt cycles; this is important to watch next because the new file-based discovery can still resume the wrong or stale session if session state files are incomplete, duplicated, or mismatched to the active project. The implementation also adds a config-based model/allow-all path (`~/.agent-deck.toml` and instance fields), so verify that non-standard install paths (`COPILOT_CONFIG_DIR`) and tmux environment propagation keep session IDs isolated per instance.

What To Watch Next

  • Watch whether agent-deck becomes a repeated pattern.
  • Track follow-up changes around AI Integration in IDEs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: stale_or_corrupt_session_events_jsonl, wrong_session_match_by_workdir.
Open Topic TimelineOpen Technical EventOpen Original Sourcestale_or_corrupt_session_events_jsonl / wrong_session_match_by_workdir / resume_false_positive_on_short_conversations / tmux_env_session_id_leak_between_panes / custom_config_dir_path_resolution_errors

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

asheshgoplani/agent-deck PR #851: feat(copilot): add first-class session detection, resume, model/allow-all config

Adds first-class Copilot CLI integration so sessions are detected, resumed, and configured through agent-deck settings instead of treated as fresh invocations.