Skip to content

docs(sessions): record the sessions switch as a feature-flag chapter #996

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JSdotNet merged 1 commit into from
Oct 5, 2026
Merged

docs(sessions): record the sessions switch as a feature-flag chapter #996

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .devbook/domain/sessions/context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,15 @@ machines ran. Two agents run on them now, and "which agent, in which repository,
how long" is a different question in a different language from "how is this PC
configured" — so the subject moved out to here and Dev PC Management stopped
modelling it.

## Sessions area

```meta
status: draft
type: feature-flag
key: sessions
default: on
related: [".devbook/domain/sessions/features.md#turn-the-area-off"]
```

Turning it on shows the Sessions segment and its list in the Home shell. Switching it off withdraws the area everywhere else too: the `list_sessions` tool and the eight delivery-surface operations leave the MCP endpoint, and the dashboard's hours worked and the roadmap's actual hours stop reading agent activity. On by default and marked `DEV`. The key is `SessionFeatures.Sessions` in the Sessions module; the string is unchanged from when it lived on `DevPcFeatures`, so nobody's switched-off area came back. The settings screen lists it from the feature catalog in `AppFeatures.cs`, and a person's choice is kept in `features.json` beside the app's other per-device choices. It is retired when the Sessions area leaves `DEV`.
7 changes: 6 additions & 1 deletion .devbook/domain/sessions/features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -592,10 +592,15 @@ from the session's own `Session State`.

```meta
type: feature
feature-flag: .devbook/domain/sessions/context.md#sessions-area
tests: [unit:dotnet:Backlog.Desktop.UI.UnitTests.HomeWorkspaceSurfaceTests.With_the_sessions_feature_off_there_is_no_segment_and_no_list, unit:dotnet:Backlog.Desktop.UI.UnitTests.HomeWorkspaceSurfaceTests.A_remembered_sessions_surface_falls_back_to_the_workspace_when_its_feature_is_off, unit:dotnet:Backlog.Desktop.UI.UnitTests.HomeWorkspaceSurfaceTests.Opening_a_session_from_a_task_with_sessions_switched_off_says_so_and_stays, unit:dotnet:Backlog.HostComposition.UnitTests.McpEndpointGateTests.The_delivery_surface_is_absent_while_its_feature_is_off, unit:dotnet:Backlog.Infrastructure.FileSystem.UnitTests.AgentActivityHoursWorkedSourceTests.With_the_sessions_area_switched_off_the_hours_are_not_read, unit:dotnet:Backlog.Infrastructure.FileSystem.UnitTests.RoadmapActualHoursTests.With_the_sessions_area_switched_off_the_hours_are_not_read]
```

The whole area can be switched off, and when it is there is no way in and nothing to
find — not a disabled control and not an empty surface.
find — not a disabled control and not an empty surface. Nothing else reads the
sessions either: the `list_sessions` tool and the eight delivery-surface operations
leave the MCP endpoint, and the dashboard's hours worked and the roadmap's actual
hours stop reading agent activity.

One switch for the area rather than one per column or per grouping, because "should
this product show me sessions at all" is a single question.
Loading