fix(core): hide scheduler background sessions - #1650
Open
AaronZ345 wants to merge 1 commit into
Open
Conversation
AaronZ345
force-pushed
the
fix/background-session-list-20260806
branch
from
August 7, 2026 14:41
2c403e2 to
929bcc5
Compare
AaronZ345
force-pushed
the
fix/background-session-list-20260806
branch
from
August 13, 2026 14:44
929bcc5 to
596b07d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
new_per_runsessions as background sessions./list,/switch, and/deletefiltering by default, including current and past agent session IDs.core.hide_scheduler_sessions = false, plus config docs, changelog, and tests.Fixes #1077.
Tests
go test ./corego test -tags no_web ./cmd/cc-connectSupersedes #1417. This is the same rebased patch on a fresh PR branch, including the requested compatibility opt-out.
Supersedes #1497. This fresh replacement carries the same patch rebased onto the latest
mainafter the original PR exceeded 30 days.