mirror of
https://github.com/hanzoai/minutes.git
synced 2026-10-30 18:27:58 +00:00
zeekayandHanzo Dev
ecd717c6fb
A fork of meetily (MIT, Zackriya Solutions) rebranded to Hanzo. The Python/FastAPI tier, its Docker files, its whisper-server scripts and the whisper.cpp submodule are deleted rather than rebranded. Upstream's own CLAUDE.md says that tier is archived and unsupported and tells you not to add endpoints to it; the shipping product is one Tauri binary that transcribes in-process with whisper-rs and Parakeet. Rebranding a corpse would have doubled the surface and taught the next reader that a dead service is a live one. Going with it: the vestigial localhost:5167 gate the sidebar checked before reading its own database. .github/workflows goes too. This repo lives on git.hanzo.ai, which reads .hanzo/workflows, and we do not use GitHub-hosted runners — six workflow files that cannot run read like CI that passes. Nothing replaces them yet, because a pipeline that has never run is worse than an honest absence. Summaries are written by api.hanzo.ai, our own stack, and it is the default. The other providers still compile and should go in a follow-up. The upstream MIT notice stays and the Hanzo copyright joins it. About and the README say plainly what this is a fork of. Left alone deliberately, and each is a decision someone must still make: the minisign updater key is upstream's and we cannot re-sign, so the updater points at a release path that does not exist yet; the ffmpeg binaries still come from upstream's GitHub; the Parakeet models still come from upstream's host. Co-authored-by: Hanzo Dev <[email protected]>
1.5 KiB
1.5 KiB
System Architecture
Minutes is a self-contained desktop application built with Tauri. It combines a Rust-based backend with a Next.js frontend into a single, efficient, and cross-platform application.
High-Level Architecture Diagram
graph TD
subgraph User Interface
A[Next.js Frontend]
end
subgraph "Core Logic (Rust)"
B[Tauri Core]
C[Audio Engine]
D[Transcription Engine]
E[Database]
F[Summary Engine]
end
A -- Tauri Commands --> B
B -- Manages --> C
B -- Manages --> D
B -- Manages --> E
B -- Manages --> F
Component Details
Frontend (Next.js)
- Provides the user interface for managing meetings, displaying transcriptions, and configuring the application.
- Communicates with the Rust core through Tauri's command system.
Backend (Rust Core)
- Tauri Core: The heart of the application, responsible for managing the window, handling events, and exposing the Rust core to the frontend.
- Audio Engine: Captures audio from the microphone and system, processes it, and prepares it for transcription.
- Transcription Engine: Uses local speech-to-text models (Whisper or Parakeet) to transcribe the captured audio. It can be accelerated with a GPU.
- Database: A local SQLite database that stores meeting metadata, transcripts, and summaries.
- Summary Engine: Generates meeting summaries using various Large Language Models (LLMs), including local models via Ollama.