Before submitting
Area
Desktop app / window management
Problem or use case
I want to use multiple t3code windows at the same time so I can keep separate projects, threads, or tasks open side by side. Today, the app appears to behave like a single-window experience, which makes it harder to compare work, monitor a long-running agent task, or switch between independent coding sessions without losing focus.
Proposed solution
Add support for opening multiple app windows or instances. Each window should be able to show a different project or thread, while preserving the normal session state for that window.
Useful behavior would include:
- A menu item or command to open a new window.
- The ability to open different projects or threads in separate windows.
- Correct session isolation so actions in one window do not unexpectedly affect another.
- Window restoration where practical after app restart.
Why this matters
Multiple window support would make t3code better for real coding workflows where several tasks need to stay visible at once. It would reduce context switching and make it easier to run one agent task while reviewing or continuing another.
Smallest useful scope
A first pass only needs to support opening a second independent window for the app and allowing that window to navigate to a different project or thread.
Alternatives considered
The current workaround is to run one session at a time and manually switch between threads or projects. That works for simple cases, but it slows down workflows that need parallel visibility.
Risks or tradeoffs
Multiple windows may require careful handling of shared provider sessions, file watchers, app-level shortcuts, and persisted UI state. The app should avoid duplicate provider actions or cross-window state leaks.
Examples or references
Comparable desktop coding tools support multiple windows so users can keep separate projects or workstreams open independently.
Contribution
I would be open to helping implement this.
Before submitting
Area
Desktop app / window management
Problem or use case
I want to use multiple t3code windows at the same time so I can keep separate projects, threads, or tasks open side by side. Today, the app appears to behave like a single-window experience, which makes it harder to compare work, monitor a long-running agent task, or switch between independent coding sessions without losing focus.
Proposed solution
Add support for opening multiple app windows or instances. Each window should be able to show a different project or thread, while preserving the normal session state for that window.
Useful behavior would include:
Why this matters
Multiple window support would make t3code better for real coding workflows where several tasks need to stay visible at once. It would reduce context switching and make it easier to run one agent task while reviewing or continuing another.
Smallest useful scope
A first pass only needs to support opening a second independent window for the app and allowing that window to navigate to a different project or thread.
Alternatives considered
The current workaround is to run one session at a time and manually switch between threads or projects. That works for simple cases, but it slows down workflows that need parallel visibility.
Risks or tradeoffs
Multiple windows may require careful handling of shared provider sessions, file watchers, app-level shortcuts, and persisted UI state. The app should avoid duplicate provider actions or cross-window state leaks.
Examples or references
Comparable desktop coding tools support multiple windows so users can keep separate projects or workstreams open independently.
Contribution
I would be open to helping implement this.