You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Per-server "collapse by default" for MCP Apps (Atlassian's Jira cards take over Claude threads) #31589
Since #29803, Claude threads render MCP Apps inline. Atlassian's MCP server attaches an app to its Jira tools that renders a full issue view: the whole description, acceptance criteria, and so on. It asks for a height large enough to fit all of it, on every call. In a single "refine this ticket" turn, that meant the main issue plus one card per linked issue, each up to 2,000px tall with its own scroll bar. The assistant's reply ended up spread between them.
T3 Code renders what the app asks for, so this is mainly Atlassian's design. But we can't change third-party apps, and as more MCP servers ship apps, users need a way to rein in the ones that don't behave.
Diagnosis
In McpAppFrame, the host provides no close or collapse control: its only button is "Exit full screen", and a card closes only when the app requests teardown. Nothing in settings or per server turns rendering off either. Cards grow to whatever height the app reports, up to MCP_APP_MAX_HEIGHT (2000). Other timeline rows, such as the changed-files section, can already be collapsed.
Proposal
A per-server "collapse by default" list in settings (a list of shame, if you will):
Apps from listed servers render as a one-line collapsed row (server, tool, expand button) instead of an inline card.
Expanding shows the app as it does today. Ideally there's also a "Collapse apps from this server" action on the card itself, so you don't have to dig through settings.
Everything else stays as it is, so well-behaved apps keep rendering inline.
A host-side collapse button on every card would be useful on its own too, but the per-server default is what keeps a thread usable without clicking six times.
Steps to reproduce
Server on 0.1.8-nightly.20261105.4205 or later, Claude Code 2.1.301 or later.
Connect the Atlassian MCP connector.
In a Claude thread: "help me refine ABC-123 so it is ready to build".
Each Jira tool call renders as a tall inline Jira card.
Version
0.1.8-nightly.20261105.4218 (remote server background service and desktop app).
Environment
Desktop app on macOS (arm64) connected to a remote Linux server running as a background service. Claude Code 2.1.318.
Evidence
Screenshot withheld because it contains private work content. One turn produced six stacked Jira cards, each scrolling on its own.
Activity