Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Leonxlnx/todobar/llms.txt

Use this file to discover all available pages before exploring further.

Todobar targets Windows and macOS as its first supported platforms. Windows has been built and tested both locally and in CI. macOS is packaged by GitHub Actions but has not yet received physical device QA or code signing. This page documents current status, known gaps, and what the CI pipeline actually verifies so you know exactly where things stand.

Platform status

PlatformStatusRelease artifactsNotes
WindowsWorking.exe setup, .msiBuilt locally and in CI
macOS Apple SiliconCI-built.dmg, .app.tar.gzUnsigned
macOS IntelCI-built.dmg, .app.tar.gzUnsigned

Windows

Windows is the most thoroughly verified platform. Builds pass locally and in GitHub Actions, and the release pipeline produces both an NSIS setup executable and an MSI installer. Desktop features on Windows:
  • Frameless always-on-top window
  • Hidden taskbar entry (window is skipped from the taskbar)
  • Right-edge dock with a draggable handle
  • Click-through transparent regions outside the handle and open panel
  • Global shortcut (Alt+T, with Alt+Shift+T as a fallback)
  • Launch at login via the autostart plugin
  • Single-instance process behavior to prevent duplicate sidebars

macOS

macOS builds are produced by GitHub-hosted runners for both Apple Silicon and Intel architectures. This gives confidence that the packaging pipeline works, but real-device user experience testing is still needed before the macOS release is considered fully polished.
macOS builds are currently unsigned. Gatekeeper will warn on first open. To run the app, right-click the .dmg or .app and choose Open. Code signing and notarization are planned before Todobar reaches general availability.
Expected desktop behavior on macOS mirrors Windows: frameless right-edge window, global shortcut, launch at login, single-instance enforcement, and responsive panel sizing based on the monitor work area.

What CI verifies

The ci.yml workflow runs on both Windows and macOS GitHub-hosted runners and gates every release. It checks:
  • TypeScript and Vite production build
  • ESLint
  • Project consistency checks (version numbers, docs links, scripts, workflow files)
  • Playwright sidebar smoke test
  • Responsive layout checks for desktop, narrow, and short viewports
  • Rust cargo check
  • Tauri no-bundle native build smoke test (validates the native shell without creating installers)

What is not yet verified

The following gaps are tracked in the public issue tracker. They do not block running Todobar, but they do affect production readiness for non-technical users.
GapDetail
Physical macOS QAmacOS builds have only been run on GitHub-hosted runners, not real user hardware
Windows code signingNo Windows certificate is configured yet
Apple notarizationNo Apple Developer signing or notarization is in place
Auto-update channelNo signed update channel exists; updates require a manual reinstall
Multi-monitor position memoryThe sidebar position is not remembered per monitor
Keyboard and accessibilityThe keyboard and accessibility flow has not had a full hardening pass

Release confidence summary

Windows has the strongest confidence: local builds, CI builds, and real-device testing have all passed. macOS packaging is verified by CI, which confirms the build toolchain works, but the gap between a CI-built unsigned binary and a signed, notarized, physically-tested release is real. Plan accordingly if you are distributing Todobar to non-technical macOS users.

Build docs developers (and LLMs) love