Before submitting
Area
apps/web
Problem or use case
Sometimes t3 code is not in sync with the original session or just need to do something on that thread in the original app. Good to have a button to open the original.
Proposed solution
A button to open the current session in the original parent app/tui.
Why this matters
Debug the session out of sync or use some niche feature only present in the parent app/tui for that session. Like compaction for Opencode sessions etc.
Smallest useful scope
A button that opens current session in original app.
Alternatives considered
Find the session in the original app manually.
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/web
Problem or use case
Sometimes t3 code is not in sync with the original session or just need to do something on that thread in the original app. Good to have a button to open the original.
Proposed solution
A button to open the current session in the original parent app/tui.
Why this matters
Debug the session out of sync or use some niche feature only present in the parent app/tui for that session. Like compaction for Opencode sessions etc.
Smallest useful scope
A button that opens current session in original app.
Alternatives considered
Find the session in the original app manually.
Risks or tradeoffs
No response
Examples or references
No response
Contribution