Problem / motivation
AgentsView keeps sessions in its SQLite archive after they disappear from the source agent. It marks them with deleted_at and deletion_cause = source_missing, then excludes them from search, token counts, and cost totals.
I still want that history after I clean up conversations in Codex, Claude, or another agent. Right now, deleting a conversation there also makes it disappear from AgentsView's search and usage history.
I understand that some people want the current behavior. For them, deleting a conversation from the source should also hide it in AgentsView. This should be an opt-in setting, not a new default.
There is one wrinkle. source_missing can also cover old rows that a parser no longer produces. Those rows should stay excluded because they could duplicate sessions or inflate usage totals.
Proposed solution
Add one app setting, off by default:
"Include sessions deleted from source agents in search and usage tracking"
When enabled, AgentsView should include retained source-deleted sessions in:
- Search results
- Token totals
- Cost totals
The setting should apply across the app. Sessions deleted through AgentsView's Trash should remain excluded. Obsolete parser rows should also remain excluded.
Alternatives considered
Include all source_missing rows by default. AgentsView also uses source_missing for rows other than conversations deleted from the source agent, including obsolete parser rows. Including all of them could bring back duplicates, inflate usage totals, and surprise people who expect source deletions to carry over.
Add separate filters to search and each usage screen. That gives more control, but it makes a simple preference harder to manage.
Restore deleted source files or query the SQLite database directly. Both work as manual workarounds, but neither is practical for normal use.
Problem / motivation
AgentsView keeps sessions in its SQLite archive after they disappear from the source agent. It marks them with
deleted_atanddeletion_cause = source_missing, then excludes them from search, token counts, and cost totals.I still want that history after I clean up conversations in Codex, Claude, or another agent. Right now, deleting a conversation there also makes it disappear from AgentsView's search and usage history.
I understand that some people want the current behavior. For them, deleting a conversation from the source should also hide it in AgentsView. This should be an opt-in setting, not a new default.
There is one wrinkle.
source_missingcan also cover old rows that a parser no longer produces. Those rows should stay excluded because they could duplicate sessions or inflate usage totals.Proposed solution
Add one app setting, off by default:
"Include sessions deleted from source agents in search and usage tracking"
When enabled, AgentsView should include retained source-deleted sessions in:
The setting should apply across the app. Sessions deleted through AgentsView's Trash should remain excluded. Obsolete parser rows should also remain excluded.
Alternatives considered
Include all
source_missingrows by default. AgentsView also usessource_missingfor rows other than conversations deleted from the source agent, including obsolete parser rows. Including all of them could bring back duplicates, inflate usage totals, and surprise people who expect source deletions to carry over.Add separate filters to search and each usage screen. That gives more control, but it makes a simple preference harder to manage.
Restore deleted source files or query the SQLite database directly. Both work as manual workarounds, but neither is practical for normal use.