When a session has both agent files and session files, the Files drawer sometimes shows the merged tree without the All/Agent/Session segmented control, so there is no way to filter by origin.
The control's visibility is derived from at most five recent-file summaries rather than from the tree itself, so whenever the recents sample happens to contain only one origin, the control does not render even though both origins are present in the tree.
Steps to reproduce:
- Open an agent session where the agent wrote at least one file (session origin) and the agent template carries files (agent origin).
- Open the Files drawer.
- Depending on which five recents the summary returns, the segmented control is present or absent; the tree itself always shows both origins.
Seen on staging v0.107.0 during release QA (2026-08-02); the derivation predates the release. Files are reachable either way, so this is a filter affordance gap, not data loss.
When a session has both agent files and session files, the Files drawer sometimes shows the merged tree without the All/Agent/Session segmented control, so there is no way to filter by origin.
The control's visibility is derived from at most five recent-file summaries rather than from the tree itself, so whenever the recents sample happens to contain only one origin, the control does not render even though both origins are present in the tree.
Steps to reproduce:
Seen on staging v0.107.0 during release QA (2026-08-02); the derivation predates the release. Files are reachable either way, so this is a filter affordance gap, not data loss.