HangarPro
Agent apps / Hangar: an agent manager as a desktop app. Conversations grouped by workspace, with an Inbox of those that wait on your review; the open conversation's task list and the artifacts the agent made (an implementation plan, a walkthrough recording, a screenshot); Planning or Fast and a model in the composer; a Surfaces pane with the Editor and the agent's edits, the Browser it drives (its actions with times) and the Plan, where any line takes a comment before Proceed.
oxyn add hangarOn phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
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
- Hand a task to an agent, follow its task list, review the artifacts it makes (comment on the plan line by line before it goes on), and look at its work in the editor and the browser it drives.
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
Hangar 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 hangarUsage
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.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
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.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
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 build?
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Artifact
The Plan artifact open: comment on a line, then Proceed or send the comments back to the agent.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
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.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
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.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Browser
The Browser surface: the checkout at 390 px as the agent sees it, and what it did, with times.
On phones the checkout summary hides the total under the fold. Make it a sticky footer with the total and the Pay button, and check it in the browser at 390 px.
- Read the checkout layout and stylesdone
- Write the implementation plandone
- Move total and Pay into a sticky footerin progress
- Check 390 px in the browsernext
- Record a walkthroughnext
Artifacts
I wrote a plan for the sticky footer. Read it, comment on any line, then Proceed and I'll check it in the browser.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
HangarScreen
| 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`, `artifact` or `browser`). |
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<HangarData> | Default::default() | Your data. `None` shows the sample for `state`; start from `HangarData::default()`. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Enter | Send (Shift + Enter for a new line) |
| ← → | Move between Editor, Browser and Plan |
| Escape | Close the mode, model or account menu |
Accessibility
- The sidebar is a nav landmark; conversations sit under their workspace and name their state in text.
- Inbox is a toggle button (aria-pressed) with the count of conversations waiting on review.
- Editor, Browser and Plan are a tablist (roving tabindex, arrow keys); each plan line is a button that opens a labelled comment box.
- The task list names each task's state in text, not colour alone; 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 dates hide in rows. scripts/ovl.py finds no text overlap at 1440, 768 and 390 in light and dark.
Notes for AI
- Import
HangarScreenfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
HangarElinoxyn_gpui. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.