Error toasts can render outside of the viewport, without a way to scroll them.

[RokeJulianLockhart]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

When a session fails to share many times, the consequent error toasts can render outside of the viewport, without a way to scroll them.

To reproduce

Reproduce what issues/9735 describes, until the consequent error toasts render outside of the viewport.

Expected behavior

They should be possible to scroll.

Screenshots, videos, and logs

Operating system (OS)

Linux

Operating system and version

fedora-release-identity-kde-desktop-43

Shell Version

$HOME/.dotnet/tools/.store/powershell/7.5.4

Current Warp version

v0.2026.04.27.15.33.preview_02

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

I don't know whether it ever worked.

Additional context

As requested:

1. #!/usr/bin/env pwsh
   loginctl show-session "$Env:XDG_SESSION_ID" -p Type | jc --ini | jq | yq -P .Type

2. wayland

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.

[oz-for-oss]

@RokeJulianLockhart

Here's what I found while triaging this issue:

The screenshot and current behavior point to a toast-stack overflow issue rather than a shell/Wayland-specific terminal problem. Repeated failed share attempts can accumulate persistent error toasts faster than the current stack can keep within the window.

Maintainer details

I concluded that repeated shared-session creation failures can accumulate persistent error toasts in an unbounded workspace toast stack, causing older toasts to render outside the viewport..

Triage summary

This looks actionable as a toast-stack layout bug triggered by repeated shared-session failures. The reporter's screenshot shows a vertical stack of error toasts overflowing the visible window, and the current client code has a path where failed session sharing creates persistent error toasts.

Evidence

• Reported on Linux/Fedora KDE Wayland in v0.2026.04.27.15.33.preview_02 with a screenshot showing the overflow.
• app/src/terminal/local_tty/terminal_manager.rs handles FailedToCreateSharedSession by calling show_persistent_toast(...) for non-quota failures.
• app/src/terminal/view.rs forwards persistent toasts to the workspace ToastStack.
• app/src/view_components/dismissible_toast.rs appends persistent toasts to an internal vector and renders every toast in an unconstrained vertical column.
• app/src/workspace/view.rs positions that stack as an overlay near the top of tab content without an explicit viewport-height constraint or scroll affordance.

Likely fix direction

Constrain the workspace toast stack to the available viewport and make overflow scrollable, or cap/deduplicate repeated persistent errors. For the session-share failure case specifically, adding a stable object ID or replacing older matching failures may also reduce repeated identical toasts, but the general toast container still needs overflow behavior for other persistent-error sources.

Duplicate check

I enumerated open issues and did not find two or more likely duplicates. Nearby issues such as toast timing or unrelated scroll requests do not match this shared-session error-toast overflow symptom.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[henrytran1803]

I'd like to work on this issue. Let me know if anyone is already on this. thanks

[zachlloyd]

@henrytran1803 you're free to work on it. i'd actually like specs for this one because i'm not sure what the right product behavior is here. @oz-agent could you spec this out pls

[oz-for-oss]

@zachlloyd

I'm implementing this issue with no spec context.

You can view the conversation on Warp.

I created a new draft implementation PR for this issue.

Next steps:

• Review the implementation changes in the PR.
• Complete any manual verification needed for this issue before merging.

Powered by Oz