Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
Python agentagent-osaiai-agentsai-partnerchatopsclaudeclaude-codecodexdevtoolsdiscord-botlark-botllmlocal-firstlong-term-memoryopencodeslack-botvibe-codingvibeywechat
import { createContext, useContext } from 'react';
/**
* Whether THIS document was opened as a single-app tab (`?standalone=1`, see
* `apps/appLaunch.ts`). The shell freezes the flag at mount and publishes it here so
* the app pages under the route Outlet can render FULL-BLEED — no page header, no
* rounded card, no shell chrome — instead of the padded workbench page layout.
*
* The published value is the FROZEN document flag, not "is the tab currently on an app
* route". The window controls read it to withhold minimize (a chromeless tab renders no
* sidebar, so nothing can restore a minimized window), and that answer must hold for the
* tab's whole life: a standalone tab that steps out to `/chat/...` gets the Dock back
* only until Back returns it to the app route, which would strand anything minimized in
* between. The shell's own layout uses the route-scoped combination instead — it must
* put the chrome back on the pages a standalone tab navigates to.
*
* Deliberately separate from the `windowed` prop an app body receives inside an
* AppWindow: `windowed` also carries window semantics (ephemeral terminal sessions,
* close guards, persisted window state), while a standalone tab is still the ROUTE
* mount and keeps that route's behavior — it only drops the chrome.
*
* Defaults to false, so a page mounted outside the shell (tests, storybook-ish
* harnesses) keeps the normal padded layout.
*/
export const StandaloneAppTabContext = createContext(false);
export function useStandaloneAppTab(): boolean {
return useContext(StandaloneAppTabContext);
}