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]>
2.5 KiB
2.5 KiB
Testing Notifications on macOS
Quick Test Commands
1. Test Notification Immediately
To test if notifications are working, call this command from your frontend:
// This will initialize the notification system and show a test notification
await invoke('test_notification_with_auto_consent');
2. Initialize Notification System First
If you want to initialize the notification system manually:
// Initialize the notification system
await invoke('initialize_notification_manager_manual');
// Then show a test notification
await invoke('show_test_notification');
3. Recording Notifications
When you start recording, the app should automatically show a notification. The system will:
- Check if notification manager is initialized
- Automatically grant consent and permissions for testing
- Show "Recording has started" notification
Expected Behavior on macOS
When working correctly, you should see:
- A native macOS notification appear in the top-right corner
- Title: "Minutes"
- Body: "Recording has started" (or test message)
- The notification should appear like system notifications (microphone detected, etc.)
Troubleshooting
If notifications don't appear:
-
Check macOS Notification Settings:
- Go to System Preferences → Notifications & Focus
- Find your app in the list
- Ensure notifications are enabled
-
Check Do Not Disturb:
- Make sure Do Not Disturb is off
- Or use:
await invoke('get_system_dnd_status')to check
-
Check Logs:
- Look for log messages about notification initialization
- Check for permission/consent messages
-
Manual Permission Request:
await invoke('request_notification_permission');
Available Commands for Testing
// System status
await invoke('is_notification_system_ready');
await invoke('get_system_dnd_status');
await invoke('get_notification_stats');
// Permissions and consent
await invoke('request_notification_permission');
await invoke('set_notification_consent', { consent: true });
// Testing
await invoke('test_notification_with_auto_consent');
await invoke('show_test_notification');
// Settings
await invoke('get_notification_settings');
Development Notes
- The notification system is designed to work like native macOS notifications
- For development/testing, consent and permissions are automatically granted
- The system respects Do Not Disturb settings
- All notification preferences are saved locally