# Application shell

Source: /tuil/docs/reference/components/application-shell
Locale: en

Compose full-screen terminal applications from a main content region, top application bar, and bottom status surface.





## Overview [#overview]

Compose full-screen terminal applications from a main content region, top application bar, and bottom status surface.

## Installation [#installation]

<CodeBlockTabs defaultValue="npm">
  <CodeBlockTabsList>
    <CodeBlockTabsTrigger value="npm">
      npm
    </CodeBlockTabsTrigger>

    <CodeBlockTabsTrigger value="pnpm">
      pnpm
    </CodeBlockTabsTrigger>

    <CodeBlockTabsTrigger value="yarn">
      yarn
    </CodeBlockTabsTrigger>

    <CodeBlockTabsTrigger value="bun">
      bun
    </CodeBlockTabsTrigger>
  </CodeBlockTabsList>

  <CodeBlockTab value="npm">
    ```bash
    npx @mwillbanks/tuil add app-shell app-bar status-bar
    ```
  </CodeBlockTab>

  <CodeBlockTab value="pnpm">
    ```bash
    pnpm dlx @mwillbanks/tuil add app-shell app-bar status-bar
    ```
  </CodeBlockTab>

  <CodeBlockTab value="yarn">
    ```bash
    yarn dlx @mwillbanks/tuil add app-shell app-bar status-bar
    ```
  </CodeBlockTab>

  <CodeBlockTab value="bun">
    ```bash
    bun x @mwillbanks/tuil add app-shell app-bar status-bar
    ```
  </CodeBlockTab>
</CodeBlockTabs>

The CLI writes source-owned components beneath the destination configured in
`tuil.config.ts`; the default import below assumes `src/components/tuil`.

<PublishedStory storyId="component-acceptance" variant="AppShell" />

## Components and subcomponents [#components-and-subcomponents]

| API                                                                    | Signature            | Description                |
| ---------------------------------------------------------------------- | -------------------- | -------------------------- |
| [`AppShell`](/tuil/docs/reference/components/application-shell/app-shell)   | `function AppShell`  | Public function AppShell.  |
| [`AppBar`](/tuil/docs/reference/components/application-shell/app-bar)       | `function AppBar`    | Public function AppBar.    |
| [`StatusBar`](/tuil/docs/reference/components/application-shell/status-bar) | `function StatusBar` | Public function StatusBar. |

## Interaction [#interaction]

These are structural components. Child navigation, commands, and controls own interaction.

## API and events [#api-and-events]

Shell components forward child behavior and do not emit their own events.

Every interactive component publishes semantic roles, labels, state, and focus
identity through the renderer's `SemanticRegistry`. Callback failures flow to
the owning application's error boundary.

<Mermaid
  chart="flowchart LR
  S0[&#x22;props and runtime state&#x22;]
  S1[&#x22;semantic registration&#x22;]
  S2[&#x22;focus and input routing&#x22;]
  S3[&#x22;callback or state update&#x22;]
  S4[&#x22;rerender&#x22;]
  S0 --> S1
  S1 --> S2
  S2 --> S3
  S3 --> S4"
/>

## Example [#example]

```tsx
import type { ComponentProps } from "react";
import { AppShell } from "@/components/tuil/components/app-shell";

export function Example(props: ComponentProps<typeof AppShell>) {
  return <AppShell {...props} />;
}
```

Registry-installed components are source-owned: customize the generated file in
your application, and use the package reference for the shared runtime contracts.