Skip to content
Back

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 hangar
Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

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.

Get Pro

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.

Terminal
oxyn add hangar

Usage

Dioxus · rust
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Examples

Sample

Sample data, the main area as an inset card.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Flat

The same view with the main area edge to edge.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Loading

Skeletons in the sidebar, the conversation and the pane.

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Empty

A first run: nothing yet, the composer front and centre.

New conversation

What should the agent build?

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Artifact

The Plan artifact open: comment on a line, then Proceed or send the comments back to the agent.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

X1

Oxyn: the sidebar as a 56 px icon rail; the top bar expands it.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

X2

Oxyn: the sidebar hidden for focus; the top bar brings it back.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Browser

The Browser surface: the checkout at 390 px as the agent sees it, and what it did, with times.

Mobile checkout summaryNeeds review

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.

Task list2 of 5
  1. Read the checkout layout and stylesdone
  2. Write the implementation plandone
  3. Move total and Pay into a sticky footerin progress
  4. Check 390 px in the browsernext
  5. 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 code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

API reference

HangarScreen

PropTypeDefaultDescription
layoutString"inset"`inset` or `flat`: the main area as a rounded card on the sidebar's grey, or edge to edge.
stateString"sample"A state key (`sample`, `loading`, `empty`, `artifact` or `browser`).
heightu32900Height px (outside a stage).
railboolDefault::default()Oxyn: open with the sidebar as a 56 px icon rail.
sidebar_hiddenboolDefault::default()Oxyn: open with the sidebar hidden (the top bar brings it back).
dataOption<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

KeyAction
EnterSend (Shift + Enter for a new line)
← →Move between Editor, Browser and Plan
EscapeClose 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 HangarScreen from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: HangarEl in oxyn_gpui.
  • Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.

Guides

Oxyn · 74 free components · 264 Pro components · 96 screens · 20 blocks · Dioxus and GPUI