Skip to main content

TerminalStatusBar

Surfacesterminal

The ambient chrome row along the bottom of a console surface: branch and working directory on the left, connection/context/turn progress on the right, every fact independently optional.

import { TerminalStatusBar } from "@elabs-ai/components-terminal";
Install
npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-terminal

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui TerminalStatusBar component (from @elabs-ai/components-terminal) to this project.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Look TerminalStatusBar up before writing code: `npx -y @elabs-ai/components-cli docs TerminalStatusBar` prints its real props, variants, what it pairs with and what to avoid.
3. If @elabs-ai/components-terminal is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-terminal` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-terminal`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
4. Use it here: [the screen or file, and what it should show]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

Avoid

  • Reaching for `@elabs-ai/components-ai`'s `Context` component or its tokenlens math — `terminal` and `ai` are layer-2 DAG siblings; `context` takes two ALREADY-FORMATTED display strings the caller computed, never raw token counts to abbreviate.
  • Relying on colour alone for `connections.disconnected` — it renders a distinct glyph (UnplugIcon, not PlugZapIcon) plus its own visible text label, recoverable in greyscale and by a screen reader.
  • Adding a second `role="status"` on an inner segment — the container itself is already the one live region; a nested one duplicates announcements.
  • Rendering the right-cluster divider as a literal `│` character — that is a box-drawing glyph as text; it is a plain `bg-terminal-border` rule instead.

Works with

Pairs with

Examples

6 live examples

Branch And Workspace Only

Only branch and working directory — every other fact is independently optional.

Connecting Integrations

Integrations mid-handshake — a spinner replaces the connection icon.

Disconnected Integration

A lost or never-established connection. Recoverable in greyscale AND by a screen reader: a distinct glyph (not the connected icon, recoloured) plus its own VISIBLE text label, replacing the numeric count rather than merely sitting beside it.

Long Working Directory

A long working directory truncates in place; the full path stays in `title`.

Empty

No segment supplied — the bar renders nothing at all, not an empty shell. There is no bar content here to demonstrate as a region, so this story supplies its own `render`, which replaces (not adds to) the meta-level console wrapper — nesting an app-toned demo box inside the terminal ground would fail contrast for no benefit.

API

TerminalStatusBar

PropTypeDescription
branchstringCurrent git branch.
workspacestringCurrent working directory. A long path truncates in place; the full value is still reachable via its native `title`.
connectionsTerminalStatusBarConnectionsIntegration/MCP connection progress.
contextTerminalStatusBarContextContext-window usage, already formatted by the caller.
turnTerminalStatusBarTurnProgress through the current turn's steps.

Also accepts: HTMLAttributes<HTMLDivElement>

Theming

The tokens each state resolves to. Change the token and every theme follows.

StateToken
disconnectedGlyphtext-terminal-ansi-bright-red
disconnectedTexttext-terminal-foreground