session-startup

A startup cleanup detector runs once per conversation by using a PowerShell-based wrapper that enforces run-once semantics, preventing repeated startup actions while preserving initial session state across workflows.

A session startup guard detects stale-state artifacts before the first agent reply and prompts a cleanup pass, applying safe fallbacks if prerequisites fail to ensure a clean conversation startup state.

Yes, the PowerShell startup cleanup detector is wired into both Copilot and Claude Code startup paths, sourcing its logic from a scripts directory to orchestrate a single detector run before the first agent reply.

You automate prompted cleanup by deploying a plugin-driven wrapper that triggers the detector at conversation startup, executing a single cleanup pass while respecting fail-open behavior if script prerequisites are missing.

If startup cleanup detector prerequisites fail, the plugin wrapper applies fail-open behavior, allowing the conversation to proceed safely without blocking the first agent reply or forcing a repeated cleanup attempt.

You need a run-once startup guard when automatic session-cleanup actions must execute at most once per conversation, preventing duplicate cleanup passes and maintaining consistent startup state across agent orchestration workflows.