Skip to content

@hanzo/team 0.1.14: Bots is hanzo.bot's app, the same bots and conversations - #15

Merged
zeekay merged 1 commit into
mainfrom
bots
Nov 12, 2026
Merged

zeekay merged 1 commit into
mainfrom
bots

Conversation

@zeekay

@zeekay zeekay commented Nov 12, 2026

Copy link
Copy Markdown
Member
  • /bots is a surface on the rail: @hanzo/app 0.3.68's Bots (the component hanzo.bot draws) in team's chrome, lazy-loaded (Bots chunk 187 KB; the main bundle stays 1.56 MB).
  • One API and one data source: /v1/agents and its runs with the reader's token; the session through a provider built from the same config() as team's IAM client; the org of the open space; ?bot= held by react-router.
  • Chat navigator and search open bots in the Bots app; deleted agents are no longer offered; earlier bot DMs stay in Direct.
  • Dev proxy honours HANZO_API_ORIGIN (as hanzo.ai's dev server does).

Tests: node --test 69 passed, tsc --noEmit clean, vite build ok. Live: hanzo-inc/app e2e/bots.spec.ts 10/10 against a local cloud with a real model, including "hanzo.team draws the same bot and the same conversation" signed in with a token minted by team's own client (hanzo-team-native).

After merge, hanzo.team ships by bumping @hanzo/team in hanzo-inc/team site/package.json to 0.1.14.

🤖 Generated with Claude Code

…sations

A Bots surface at /bots draws @hanzo/app's Bots (0.3.68), the component
hanzo.bot draws, in this app's chrome: one roster, one thread and one panel,
read from /v1/agents with the reader's own token, so a bot made on hanzo.bot
is here with its conversation. The app is lazy (its own chunk); it reads the
session through a provider built from the same IAM settings as this app's
client (data/iam.ts config()), works in the open space's org, and its ?bot= is
held by this app's router. The roster's foot is off: the rail and bar already
hold the account and the other apps.

The chat navigator's and the search's bots open the Bots app (botPath); a
deleted agent (Employee.active false) is no longer offered as a bot; a direct
message with a bot from before stays in Direct. The dev proxy takes
HANZO_API_ORIGIN, as hanzo.ai's does, so a local cloud can stand behind it.
blockExoticSubdeps is off for @hanzo/personas' release tarball, as on hanzo.ai.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
@zeekay
zeekay merged commit 88a3cc0 into main Nov 12, 2026
6 checks passed
@zeekay
zeekay deleted the bots branch November 12, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant