TabstackPro
Agent apps / Tabstack: an agent-first terminal. Vertical tabs, one per shell or agent session, each with the agent's mark, branch and pull request; a terminal of blocks (the command, its output, exit status and time) with the agent's turns between them and Ask agent on a failed block; the command the agent wants to run waits on Run, Edit or Deny; an input that switches between Terminal and Agent with Profile (Default, Auto, Prod) and Model; a pane with Agents (local and cloud runs) and Review.
oxyn add tabstackrunning 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- Run commands and agents side by side in one terminal, approve what the agent wants to run, and review its change.
When not to use
- Mail folders with counts and labels beside a message list: use Inbox sidebar instead.
- The app frame: use App shell instead.
- An assistant docked beside a page: use AI side panel instead.
Installation
Tabstack is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add tabstackUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Sample
Sample data, the main area as an inset card.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Flat
The same view with the main area edge to edge.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Loading
Skeletons in the sidebar, the conversation and the pane.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Empty
A first run: nothing yet, the composer front and centre.
What should the agent do?
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Approval
The agent asks to run a command: the command in full with Run, Edit and Deny, and the tab marked as waiting.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;The agent wants to runDefault profile
cargo test upload -- --test-threads 8 --nocapture
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
X1
Oxyn: the sidebar as a 56 px icon rail; the top bar expands it.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
X2
Oxyn: the sidebar hidden for focus; the top bar brings it back.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Review
The pane on Review: the session's diff with Approve and Request changes.
running 9 teststest upload::resumes_after_drop ... FAILEDthread 'resumes_after_drop' panicked: timed out after 2000 mstest result: FAILED. 8 passed; 1 failed
This test fails about one run in five. Find out why and fix it.
The test waits a fixed 2 s for the retry, but the retry timer starts only after the socket closes, which can take longer on a busy machine. I'll wait on the retry event instead of the clock.
42: sleep(Duration::from_millis(2000)).await;Editing tests/upload.rs
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
TabstackScreen
| Prop | Type | Default | Description |
|---|---|---|---|
layout | String | "inset" | `inset` or `flat`: the main area as a rounded card on the sidebar's grey, or edge to edge. |
state | String | "sample" | A state key (`sample`, `loading`, `empty`, `approval` or `review`). |
height | u32 | 900 | Height px (outside a stage). |
rail | bool | Default::default() | Oxyn: open with the sidebar as a 56 px icon rail. |
sidebar_hidden | bool | Default::default() | Oxyn: open with the sidebar hidden (the top bar brings it back). |
data | Option<TabstackData> | Default::default() | Your data. `None` shows the sample for `state`; start from `TabstackData::default()`. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Enter | Run the command or send to the agent (Shift + Enter for a new line) |
| Tab | Tabs, blocks, the approval card, the input, then the pane |
| Escape | Close the profile, model or account menu |
Accessibility
- The tabs are a nav landmark; the open tab carries aria-current=page and its state in words.
- Blocks are a list; each block names its exit status in text; Ask agent is a real button.
- The approval card is an alertdialog with the command in full and Run, Edit and Deny.
- Terminal / Agent are toggle buttons (aria-pressed); every action reports in a polite live region.
Responsive behaviour
- Authored on the 1440 × 900 canvas: a 272 px sidebar, the conversation and a 440 px pane (380 px under 1180).
- Under 960 px the sidebar becomes a drawer from the top bar and the pane opens over the conversation from its top-bar button.
- Under 620 px the chips shorten and the composer and pane keep their actions; labels ellipsise.
Edge cases (spec)
1440 × 900 stage; /full at the real viewport. Under 960 px the sidebar is a drawer and the pane opens over the conversation from the top bar. Under 620 px chip labels shorten and rows stack. scripts/ovl.py finds no text overlap at 1440, 768 and 390 in light and dark.
Notes for AI
- Import
TabstackScreenfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
TabstackElinoxyn_gpui. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.