CIMon (think "Simon", for CI Monitoring) is a small, cross-platform desktop app that lives in your system tray on Windows or your menu bar on macOS and tells you what your CI pipelines are doing. It watches your CI and surfaces pipeline progress as native notifications, so you can stop babysitting browser tabs.
Status: early development. CIMon monitors GitLab and GitHub pipelines, including self-managed GitLab and GitHub Enterprise instances, on macOS, Windows, and Linux. The macOS build is code-signed and notarized; the Windows build is not yet signed (see Download and install).
 The menu bar popover shows live status for every project you monitor. |
 Projects are grouped by account once you connect more than one. |
 Connect accounts and pick which projects to watch. |
 Token health is surfaced in Settings: a revoked token and one expiring soon. |
The screenshots use built-in demo data, not real repositories. See Demo data for screenshots.
- It lives where you can glance at it. A true menu bar item on macOS and a real tray icon on Windows, with the icon reflecting the worst current status across the projects you monitor.
- It is quiet by default and configurable. Choose which pipeline events and which job events you care about (started, succeeded, failed for each), and get a native notification only for those.
- It is fast and light. Built on Tauri v2 (a Rust core with a small web UI), so it uses very little memory while running all day.
CIMon is fully standalone. It runs entirely on your machine and talks directly to the CI provider you configure. There is no CIMon cloud service, no CIMon account, no telemetry, and no anonymous usage data or analytics of any kind. Your access token is stored in the operating system credential store (macOS Keychain, Windows Credential Manager, and on Linux the Secret Service API provided by GNOME Keyring or KDE Wallet), never in a plain file, and it is never sent anywhere except the GitLab or GitHub instance you point it at.
- Connect one or more GitLab and GitHub accounts, each with a scoped, read-only access token. An account can point at gitlab.com, a self-managed GitLab instance, github.com, or a GitHub Enterprise instance.
- Auto-discover the projects your token can access (GitLab projects or GitHub repositories) and pick which ones to monitor.
- Background polling with native notifications when a monitored pipeline (a GitLab pipeline or a GitHub Actions workflow run), or an individual job within it, starts, succeeds, or fails. Pipeline events and job events each have their own independent started, succeeded, and failed toggles. Click a notification to open the relevant page in your browser (the specific job for a job notification, the pipeline otherwise).
- Tray / menu bar icon showing the aggregate status across the projects you monitor, with quick links to open a pipeline in your browser.
- Token health monitoring. If a token becomes invalid, revoked, or expired, the affected account is flagged distinctly in the popover and in Settings (not as a generic connection error), with a one-time notification, and you can replace the token in place from Settings without removing the account. CIMon also warns before a token expires (on launch, then at 72 hours and 24 hours remaining) and shows an "expires in N days" indicator next to each account.
- In-app update checks. CIMon notifies you when a newer release is available, shows the update in the popover and Settings, installs and restarts in app on macOS and Windows, and opens the GitHub release page on Linux.
- Light, dark, or system appearance, with the interface available in English and French.
- Launch at login.
CIMon is read-only. It monitors and notifies. It does not trigger, re-run, or cancel pipelines.
Pre-built installers for macOS, Windows, and Linux are published on the Releases page. Download the file for your platform and install it the usual way.
The macOS build is code-signed and notarized by Apple, so it opens normally with no Gatekeeper warning. The Windows build is not yet signed, so Windows shows a one-time warning. Here is what to expect on each platform.
CIMon checks for new published releases automatically. On macOS and Windows, the update banner can install the new version and restart the app after you click Install and restart. On Linux, CIMon shows the same available version but opens the GitHub release page so you can install the package for your distribution.
Install with Homebrew:
brew install --cask fuitad/tap/cimonOr download CIMon_<version>_universal.dmg from the Releases page. CIMon is signed with a Developer ID certificate and notarized by Apple, including the disk image, so it opens with a normal double click. Open the .dmg, drag CIMon into your Applications folder, and launch it. No right-click step or quarantine workaround is needed.
Download CIMon_<version>_x64-setup.exe from the Releases page and run it. It is a per-user install, so it needs no administrator rights and installs CIMon under your %LOCALAPPDATA% folder.
Windows SmartScreen may show a "Windows protected your PC" dialog for the unsigned installer. Click More info, then Run anyway to continue.
The .deb, .rpm, and .AppImage builds need no signing. Install the package for your distribution, or make the AppImage executable and run it:
chmod +x CIMon_*.AppImage
./CIMon_*.AppImageCIMon stores your access tokens through the Secret Service API, so a provider such as GNOME Keyring or KWallet must be installed and running. Most desktop environments (GNOME, KDE) include one by default. On a minimal or headless setup without one, CIMon warns at startup and cannot save or read tokens until a provider is available.
- Node.js 20.19 or newer (Vite 8 requires 20.19+, or 22.12+) and npm
- Rust (stable) and Cargo
- Platform build tools for Tauri (see the Tauri prerequisites)
- Optional native WebDriver E2E tooling on Linux and Windows:
cargo install tauri-driver --locked
npm install
npm run tauri devBuild a release bundle:
npm run tauri buildOn macOS, npm run build:mac instead builds the bundle, installs it into /Applications, and code-signs it with a local identity so notification banners appear (an ad-hoc signed build shows notifications only in Notification Center). See Contributing for the one-time certificate setup.
Run the frontend tests (Vitest):
npm test # watch mode
npm run test:run # one-shot, the way CI runs themRun the Rust unit tests:
cd src-tauri && cargo testRun native Tauri WebDriver checks on supported platforms:
cargo install tauri-driver --locked
tauri-driver --port 4444 --native-port 4445tauri-driver 2.x currently supports Linux through WebKitWebDriver and Windows through
msedgedriver.exe. On macOS the binary installs, but exits with tauri-driver is not supported on this platform; use browser preview E2E plus manual native Tauri dev checks there until upstream
macOS support exists.
The screenshots in this README come from a built-in fixtures mode that fills the app with fabricated projects, so no real repository is ever shown. It runs only in a development build (it is compiled out of release builds) and is driven by environment variables:
# Menu bar popover with a spread of statuses, dark theme
CIMON_FIXTURES=panel CIMON_FIXTURES_THEME=dark npm run tauri dev
# Settings window with two accounts, light theme
CIMON_FIXTURES=multi CIMON_FIXTURES_SURFACE=settings CIMON_FIXTURES_THEME=light npm run tauri devCIMON_FIXTURES selects the dataset (panel, multi, or tokenhealth). CIMON_FIXTURES_SURFACE selects what to show (panel for the menu bar popover, settings for the settings window). CIMON_FIXTURES_THEME forces the appearance (light, dark, or system). In this mode CIMon skips the live poller and reads no accounts or tokens, so it never touches your real configuration.
Run the full quality gate (lint, format, static analysis, dead-code, types, tests) the way CI does:
npm run check
cd src-tauri && cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo machete && cargo testnpm install installs a pre-commit hook that runs this gate automatically before each commit. See CONTRIBUTING for the coding standards and the test-driven development workflow.
CIMon only reads project and pipeline data, so a read-only token is enough. The same scopes apply whether the account is the hosted service or a self-managed / Enterprise instance.
- GitLab: a personal access token (or project access token) with the
read_apiscope. - GitHub: a classic personal access token with the
reposcope, or a fine-grained token with read-only access to Actions, Contents, and Metadata.
MIT. See LICENSE.