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
Session tasks currently occupy a full-width band above the conversation, generated files live in a dedicated 320px right pane, and the embedded browser mounts as a separate 520px auxiliary pane. These are all per-session work surfaces, but their split ownership reduces conversation space and allows multiple auxiliary panels to compete with the main workspace.
Desired outcome
Replace the separate task ledger, artifact pane, and browser pane wrappers with one shell-owned, collapsible session workbar on the right.
Control the workbar from a top-right shell action, symmetric with the left session sidebar. Remove the artifact pane's internal collapse rail.
Keep the workbar collapsed by default, persist its open state independently, and never force it open or switch tabs when new content appears.
Make the desktop workbar resizable and persist its width. Start at 400px and clamp it to 320–600px; preserve the existing narrow-window bottom-workspace behavior.
Provide three stable, peer tabs: Tasks, Browser, and Files, with counts or availability state.
Move the existing task ledger into the Tasks tab without duplicating its task model, tree semantics, loading/error/retry states, or recent-terminal behavior.
Move the existing live BrowserPanel into the Browser tab. Keep the tab visible but disabled when the active session has no live browser view; this issue does not add a manual browser launch flow.
Move the existing generated-file list, selected preview, and toolbar into the Files tab. Selecting a file keeps its preview inside the workbar and never replaces the conversation.
Only expose browser native-view bounds while the workbar is open, the browser tab is active, and no modal is hiding the workspace.
Acceptance criteria
No task-ledger band remains above the conversation.
The browser and generated-file surfaces no longer mount as separate adjacent auxiliary panes.
A top-right action opens and closes the right workbar, exposes correct accessible state, persists the user's choice, and does not auto-open for new tasks, files, or browser activity.
The desktop resize separator supports pointer drag plus keyboard Arrow/Home/End controls, persists width, and clamps to 320–600px with a 400px default.
Tasks, Browser, and Files remain in stable tab positions. New content updates counts or availability without stealing the active tab.
The Browser tab is disabled without a live view and preserves the existing browser controls and native WebContentsView viewport synchronization when enabled.
The Files tab preserves list selection, inline preview, toolbar actions, deleted state, loading/error state, keyboard navigation, and artifact preview security boundaries.
Empty, loading, error, long-content, collapsed, resized, tab-switch, modal, session-switch, and narrow-window states remain usable and accessible.
Deterministic component/layout contracts cover state and geometry invariants, and one representative fake-backend visual or E2E journey covers the integrated workbar.
Out of scope
Opening generated-file previews in the main conversation area.
Adding a user-initiated browser launch flow.
Changing task storage, task tree semantics, browser automation behavior, artifact persistence, or preview security boundaries.
Adding Codex-specific Sources or Output concepts that Maka does not already own.
Automatically opening the workbar or switching tabs in response to runtime activity.
Alternatives or workarounds
Stacking all three details vertically makes the native browser and file preview too short when both are present. Keeping tasks fixed above browser/file tabs introduces two competing navigation levels. Three peer tabs give each work surface the full available height while stable labels and counts retain cross-surface awareness.
Problem
Session tasks currently occupy a full-width band above the conversation, generated files live in a dedicated 320px right pane, and the embedded browser mounts as a separate 520px auxiliary pane. These are all per-session work surfaces, but their split ownership reduces conversation space and allows multiple auxiliary panels to compete with the main workspace.
Desired outcome
Tasks,Browser, andFiles, with counts or availability state.Taskstab without duplicating its task model, tree semantics, loading/error/retry states, or recent-terminal behavior.BrowserPanelinto theBrowsertab. Keep the tab visible but disabled when the active session has no live browser view; this issue does not add a manual browser launch flow.Filestab. Selecting a file keeps its preview inside the workbar and never replaces the conversation.Acceptance criteria
Tasks,Browser, andFilesremain in stable tab positions. New content updates counts or availability without stealing the active tab.Browsertab is disabled without a live view and preserves the existing browser controls and nativeWebContentsViewviewport synchronization when enabled.Filestab preserves list selection, inline preview, toolbar actions, deleted state, loading/error state, keyboard navigation, and artifact preview security boundaries.Out of scope
SourcesorOutputconcepts that Maka does not already own.Alternatives or workarounds
Stacking all three details vertically makes the native browser and file preview too short when both are present. Keeping tasks fixed above browser/file tabs introduces two competing navigation levels. Three peer tabs give each work surface the full available height while stable labels and counts retain cross-surface awareness.
Related: #1032