mirror of
https://github.com/hanzo-apps/desktop-chat.git
synced 2026-11-09 15:50:22 +00:00
DEFECT: hanzo-templates shipped 71 templates and not one of them built a native application. Every "make me a desktop app" request dead-ended in the browser, and the one repo that looked like it might help (`mobile`) was completely empty — no commits, no files. There was no answer to "how do I ship a .dmg / .msi / .deb from this platform". REASON for the shape: - Tauri v2 by default. A Rust core against the OS webview produces single-digit MB installers; Electron is reserved for the cases where Chromium itself is the requirement (see desktop-recorder's desktopCapturer). - ONE seam, `src/native.ts`. A native window cannot be iframed, so the gallery preview has to be a real build of the same UI, not a screenshot and not a dead link. `bridge()` resolves a command through the Rust core (or the Electron main process) when it is running natively and through the fallbacks in `src/web.ts` when it is a browser tab. No call site branches; the two shells implement the same contract, which is why app.tsx and shell.tsx are identical across both. - Frameless everywhere. `decorations: false` / `frame: false` means the titlebar in shell.tsx IS the chrome, so the traffic lights do real work through the same bridge rather than importing a shell-specific API. - @hanzo/base for the backend and the a.hanzo.ai analytics/chat runtime in index.html, so a fork starts with persistence and telemetry already wired. - Release fans out to per-OS runners. Desktop bundles must be produced on the target OS (codesign, .dmg/.msi/.deb tooling); this one workflow is the documented exception to the shared build fleet. Upstream and license are recorded in every README. MIT/Apache-2.0/BSD only: these are meant to be forked and commercialised. Co-authored-by: Hanzo Dev <[email protected]>
39 lines
1.3 KiB
TypeScript
39 lines
1.3 KiB
TypeScript
import { bridge } from "./native";
|
|
|
|
/** Browser fallback: localStorage instead of the OS config directory. The key
|
|
* lives in the page here — which is exactly why the native build keeps it in
|
|
* Rust and this file is the only place that difference exists. */
|
|
const T = "hanzo.chat.threads";
|
|
const K = "hanzo.chat.key";
|
|
|
|
const seed = [
|
|
{
|
|
id: "intro",
|
|
title: "What is this app",
|
|
model: "zen-omni",
|
|
msgs: [
|
|
{ role: "user", content: "What is this app?" },
|
|
{
|
|
role: "assistant",
|
|
content:
|
|
"A desktop AI client: Tauri v2 shell, React UI, streaming SSE to the Hanzo gateway at api.hanzo.ai/v1/chat/completions.\n\nThreads and your API key are written by the Rust core into the OS config directory, so they never sit in web storage. Swap the endpoint with VITE_HANZO_API to point at any OpenAI-compatible gateway — including a local one.",
|
|
},
|
|
],
|
|
},
|
|
];
|
|
|
|
export const call = bridge({
|
|
load_threads: () => {
|
|
const raw = localStorage.getItem(T);
|
|
if (!raw) return seed;
|
|
try {
|
|
return JSON.parse(raw);
|
|
} catch {
|
|
return seed;
|
|
}
|
|
},
|
|
save_threads: ({ threads }: { threads: unknown }) => localStorage.setItem(T, JSON.stringify(threads)),
|
|
load_key: () => localStorage.getItem(K) ?? "",
|
|
save_key: ({ key }: { key: string }) => localStorage.setItem(K, key),
|
|
});
|