Centralized Simulator Management & Client-Side Access

[krrskl]

The problem

T3 Code already supports running isolated simulators for different development sessions, but the current workflow has two limitations:

1. Host-dependent launching: Simulators need to be launched from the host rather than directly from connected clients.
2. Chat-bound access: Simulators are associated with individual chat sessions, making it difficult to access or manage an existing simulator independently.

This creates unnecessary friction when working across devices, especially when accessing T3 Code remotely.

Proposed solution

Introduce a centralized Simulator Management Panel that treats simulators as independently accessible workspace resources rather than chat-specific UI elements.

The proposed experience includes:

• Centralized management: Access running simulators from a dedicated panel.
• Client-side launching: Launch simulators directly from connected clients without returning to the host.
• Chat-independent access: Open and interact with an existing simulator regardless of which chat originally launched it.
• Multi-device workflows: Make simulator management more convenient when switching between desktop and remote clients.

The goal is not to replace the existing chat-based simulator workflow, but to extend it with an additional way to launch, access, and manage simulators.

Implementation status

A working implementation is already developed.

I've been building this functionality to address these limitations in my own workflow.

I can share the implementation for review and adapt its scope or architecture based on maintainer feedback.

Screenshots / Demo

Why this matters

T3 Code already provides a great experience for working with multiple coding agents and accessing them remotely.

Simulator management should offer similar flexibility.

The goal is to make simulators accessible across the workspace and connected clients, without requiring developers to navigate back to a specific chat or interact directly with the host.

Feedback requested

Before submitting a PR, I'd love to get feedback from the maintainers on:

1. Does this approach align with T3 Code's intended direction?
2. Should simulators be managed as workspace-level resources independently of chats?
3. Would the team be open to reviewing a focused PR implementing this functionality?

Happy to share the code, technical details, and a working demo.

Thanks for building T3 Code!