mirror of
https://github.com/hanzo-inc/tabs.git
synced 2026-11-10 03:09:32 +00:00
`Tabs` is the fleet read with the host's bearer, nothing drawn before the registry answers, then the workspace with the plan's stream count. tabs.hanzo.ai draws it, and so do the app at hanzo.ai/tabs and platform.hanzo.ai/tabs; the app's copy rendered the workspace before the first read, so a reader with no saved layout got no pane, and it never passed the stream count. - `useFleet` takes the bearer or a reader of it, asked on every poll and mint, so a session renewed in storage is used without a re-render. - `Workspace` takes `at`, a machine named by the host's address: a pane on it is focused, or a shell on it opens beside the rest. - `createSandbox` read the running sandboxes from api.hanzo.ai whatever origin it was given. - CI runs on GitHub, where hanzo-inc has runners: the checks, the site, and an npm publish when package.json is ahead of the registry.