Files
hanzo.ai/app/(app)/home/page.tsx
zooqueen b53a5ceb21 Reach the gateway through the proxy that exists for it, and open /home again
THE READS WERE ALL FAILING LOCALLY. api.hanzo.ai admits an origin by an
allowlist and by an https, portless DNS proof, and localhost satisfies
neither — so every read carrying an Authorization header failed its
preflight and the app drew as if the org owned nothing: no agents, no
people, no projects, no integrations, no conversations.

next.config.mjs has proxied /v1 for exactly this since it was written,
but a client with an absolute default never reaches a rewrite, so the
proxy sat unused. base() now answers this page's own origin on the dev
server. The static export keeps the absolute default: it has no server
to rewrite anything and is served from an origin the gateway admits.

/home renders the workspace home again. It was turned into a bare
redirect to /chat, which left Home.tsx — the six cards, the four asks —
imported by nothing. It mounts the way every other room does.

The rail's Home wears the chat bubble. It carried a house to tell it
apart from Chat, and the two never sit in the rail together, so there
was nothing to tell apart.
2026-08-30 13:55:33 -07:00

23 lines
496 B
TypeScript

import type { Metadata } from 'next'
import Room from './_workspace'
const TITLE = 'Home — your workspace on Hanzo'
const DESCRIPTION =
'What you are building, who is in the org, and what it has running.'
export const metadata: Metadata = {
title: TITLE,
description: DESCRIPTION,
openGraph: {
title: TITLE,
description: DESCRIPTION,
url: 'https://hanzo.ai/home',
siteName: 'Hanzo AI',
type: 'website',
},
}
export default function Page() {
return <Room />
}