Files

T

History

zeekayandClaude Opus 4.8 3893495338 feat(login): adopt unified Hanzo shell on the logged-out page

Logged-out studio.hanzo.ai now renders the canonical HanzoHeader (Sign in -> same-origin /login) above the sign-in card, plus HanzoPreFooterCTA + HanzoFooter (currentProductId=studio) below it. server.py serves the bundle via a guarded /marketing static route (mirrors /docs); assets are public (.js/.css) so they load pre-auth. The sign-in card stays as the progressive-enhancement fallback -- auth path unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-23 21:58:14 -07:00

marketing

build(marketing): add built unified-shell bundle (studio.hanzo.ai surface)

2026-07-23 21:58:07 -07:00

shell

build(marketing): add web/shell esbuild package for the unified Hanzo shell bundle

2026-07-23 21:58:03 -07:00

src

studio-chat: Up next / History / Stacks queue surface with ratings + favorites (#22 )

2026-07-17 15:28:42 -07:00

.gitignore

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

index.html

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

feat(login): adopt unified Hanzo shell on the logged-out page

2026-07-23 21:58:14 -07:00

package-lock.json

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

package.json

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

README.md

studio/web: call api.hanzo.ai/v1/chat directly — no studio proxy layer

2026-07-16 10:57:33 -07:00

tsconfig.json

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

vite.config.ts

studio: web/ — our unique product frontend (chat app on the shared Hanzo stack)

2026-07-16 09:48:39 -07:00

README.md

Studio web — the Hanzo Studio product frontend

Our unique studio frontend: a specialized chat app on the shared Hanzo stack. You say what to create; the cloud /v1/chat orchestrator drives studio's render tools and the outputs land in the library. This is the default surface at studio.hanzo.ai/studio.

Stack: Vite + React + TS. @hanzo/* packages are npm-published, so a clean npm install — no workspace linking.
Chat: POST api.hanzo.ai/v1/chat {capability, messages} → {reply, actions, ops} — the cloud clients/chat orchestrator, called directly (no studio proxy). The hanzo_token cookie is .hanzo.ai-scoped, so credentials:'include' carries it cross-origin and the handler bills the caller org. (Gateway CORS must allow the studio.hanzo.ai origin with credentials.)
Engine: the studio pod serves /v1/session, /v1/library, /v1/render-queue, /v1/gpu-status same-origin (same cookie) — no token handling in the browser.

npm install
npm run build      # -> dist/  (served at /studio; base = /studio/)
npm run dev        # local, set VITE_STUDIO_API=https://studio.hanzo.ai

The ComfyUI-derived node editor ("Advanced mode") is a separate repo — hanzoai/studio-ui (formerly studio-frontend) — not this app.

Status / next

Increment 1 (done): chat wired to /v1/chat create + live library/queue/gpu strip.
Increment 2: swap the transcript/composer for @hanzo/chat <Chat> on @hanzo/gui (GuiProvider + SessionProvider, copying console2's Provider.tsx spine).
Wiring: Dockerfile multi-stage to build dist/ and serve it at /studio in place of middleware/studio_home.html. (No proxy — chat hits api.hanzo.ai direct.)