Manage Codex plugins and service connections directly in T3 Code

[Assem130]

Problem and use case

I use T3 Code with Codex on Linux and want to manage Codex plugins without switching to another application or the terminal.

Plugins such as Impeccable and Firecrawl can provide useful skills and tools to a Codex session, but I want a clear place in T3 Code to see which plugins are installed, which are enabled for the selected Codex provider, and whether their service connections are ready.

For example, I should be able to find Firecrawl, install it, complete its connection setup, and then use it from a T3 Code conversation. For a skill-based plugin such as Impeccable, I should be able to install it and see the skills it provides.

Proposed solution

Add a Plugins section associated with the selected Codex provider/account:

• Browse and search the Codex plugin catalog, with descriptions of the skills, tools, and connections each plugin provides.
• List installed plugins and support installation, updates, enable/disable, and removal where Codex exposes those operations.
• Show connection status and provide Connect, Reconnect, and Disconnect actions where supported, using the service's normal authorization flow.
• Surface installation confirmations and connection requests from conversations as usable controls.
• Show useful states such as ready, disabled, setup required, unavailable, or failed, with an explanation and next step.
• Refresh plugin and skill availability after a change, or clearly explain when a new chat or session restart is required.
• Identify which provider/account and environment a change applies to, especially when multiple Codex instances or remote environments are configured.

Reuse Codex's existing plugin state and app-server capabilities so T3 Code and the native Codex clients remain consistent. Where an operation is unavailable in the installed Codex version, show that limitation clearly.

What success looks like

A user can discover and install Firecrawl, complete its required connection setup, verify it is ready, and use it in a conversation without leaving T3 Code. The same interface supports a skill-based plugin such as Impeccable and lets the user disable or remove it later.

Installed, enabled, and connected are presented as distinct states. Changes remain visible after reopening T3 Code.

Related reports

• #6065: Plugin installation confirmation card does not render
• #2168: Plugins/Skills not brought over from the Codex app

These describe related parts of the experience; this proposal asks for an integrated plugin management and connection flow.