Allow collapsing or hiding inline MCP app cards while keeping the connector enabled

[CsengerBari]

Problem

Inline Jira MCP app cards can take over the conversation with full ticket descriptions, even when the user only needs a short confirmation or summary. There is no visible way to collapse the card or keep the integration enabled while hiding its inline UI.

This makes routine Jira work hard to scan. The user ends up considering disconnecting the Atlassian integration just to avoid the large cards, despite still wanting the agent to read and update tickets.

Reproduction

1. Use Codex in T3 Code with the Atlassian integration connected.
2. Ask the agent to retrieve or update a Jira ticket with a substantial description.
3. The result appears as an inline Jira MCP app card containing the ticket title, metadata, and full description with headings and lists.
4. Collapse the normal tool/activity trace. The large Jira card remains in the conversation, with no visible collapse control.

Requested behavior

Allow users to keep the connector and its tools enabled while controlling how its app cards appear:

• A collapse/expand control on each card, showing a compact summary when collapsed.
• An optional preference to start MCP app cards collapsed, or show a normal tool result with an explicit action to open the app.

The aim is to keep normal ticket reads and updates compact while leaving the full app accessible when needed.

Environment and investigation

• T3 Code desktop on macOS, Apple Silicon.
• Installed version: 0.1.7-nightly.20261102.4066.
• Provider: Codex.
• Observed on 4 November 2026.
• Persisted Atlassian tool results include t3McpApp pointing to ui://widget/jira-widget.html.
• The installed renderer displays these as separate mcp-app timeline rows. I could not find a hide/collapse preference in the saved client settings or the installed settings definitions.
• The current MCP apps documentation describes apps appearing in place of tool calls, but does not document a collapse or opt-out control.

Related reports include #16992 (blank Jira cards) and #17032 (excess blank space in short cards on mobile). This request concerns successfully rendered, content-heavy cards and user control over their presentation.

[JulienZD]

I'm having the same problem with Claude in T3 Code. The Jira MCP cards are huge and take up so much space before I can even see the response.

See both examples below. In neither case did I even ask for the contents, I just wanted to know if some tickets had something, and I get a massive wall of unrelated cards.

I'm on 0.1.8-nightly.20261105.4205. I'm going to downgrade to a version from before, as this is making it harder to get my work done.

Examples:

Asking Claude whether there's an existing ticket for {something}

After downgrading to an earlier version, this message is a lot more readable

---

Here I'm asking Claude to put some tickets on my name in Code Review. The result is what's shown in the image, with even a second auto-expanded ticket below it, taking up even more vertical space.

Claude's response at the very bottom was just one short sentence:

I moved {ticket_one} and {ticket_two} from In Progress to Code review.