Fullscreen Workspace

The expanded mode for multi-step exploration or editing once the task no longer fits a thread-native surface.

Fullscreen Workspace

Fullscreen is a host-managed expanded mode. The system composer still exists, so this is for deeper exploration or multistep editing rather than replacing the chat shell.

What it is for

Show when the app should ask the host for more room without confusing fullscreen with a standalone shell the app owns.

Use when

The task needs more room than an inline card, inspector rail, or PiP can safely provide.

Do not use when

The content is still a preview, a supporting detail rail, or a live monitor.

Related patterns

Widgets & Registry · Fullscreen · App Surfaces · Side Panel · MCP Client Interface

Escalation path

Side panel or inspector rail → request host fullscreen for deep work → use the composer for follow-up prompts.

Developer details

Start from these files when you need to trace the live implementation.

src/shared/ui/chat/FullscreenWorkspaceShell.tsx · src/shared/ui/chat/ContextDetailPanel.tsx

Host view

The host grants more room, but the composer still drives the conversation.

requestDisplayMode: fullscreen

Fullscreen is not app takeover. It is the host expanding the canvas while preserving follow-up prompting below the response area.

Interior workspace payload

Estimate workspace

Use fullscreen when the user needs a broader task canvas. The shared shell here is only the interior payload designed for that host mode.

composer remains visible

Why fullscreen exists

Give the task more room for editing, review, or structured exploration while keeping follow-up prompting in the host.

Workspace actions

Fullscreen should still read like a host-owned workflow. The expanded workspace grows the task canvas, not the app’s claim over the whole screen.