Connect a computer, choose supported tools, and send monitoring metadata to your workspace. A background connector keeps working when you close its tray menu.
This preview is for technical evaluation. Its programs and installer scripts are not code-signed, and the macOS app is not notarized.
Updates are manual. When this page offers a newer version, toolcaise-connect status and the tray menu say so; nothing is downloaded or installed automatically. toolcaise-connect update-check disable turns that check off.
Your operating system will warn you. First check that the SHA-256 of the file you downloaded matches this page: a match shows it is the file that was published, though not, as a signature would, who published it.
Windows: SmartScreen may say “Windows protected your PC”. Choose More info, then Run anyway. Smart App Control, and computers whose administrators allow only signed software, block unsigned programs with no way past: wait for a signed release rather than turning those protections off. If PowerShell only runs signed scripts on your computer (the AllSigned execution policy), the installer script will not run.
macOS: Gatekeeper refuses to open the installer and then the app the first time (“Apple could not verify…”). Open System Settings › Privacy & Security and choose Open Anyway for the blocked item. This needs an administrator password and may not be allowed on a managed Mac. Do not turn Gatekeeper off or remove the quarantine attribute.
Linux: nothing is signed, so the SHA-256 is the check.
Windows
Intel / AMD 64-bit
Extract the whole ZIP: right-click it and choose Extract All.
Right-click install-windows.ps1 and choose Run with PowerShell. It installs for your Windows user only, without administrator rights, and adds Toolcaise Connect to the Start menu.
Open Toolcaise Connect from Start. From its tray menu, sign in, choose the agents to monitor, then install the background collector.
Check it with Get-FileHash .\Toolcaise-Connect-0.4.0-preview.2-windows-amd64.zip -Algorithm SHA256 (letter case does not matter).
macOS
Apple silicon
Open the ZIP, then open install-macos.command. It copies Toolcaise Connect to the Applications folder in your home folder and keeps the previous version when you upgrade.
Toolcaise Connect runs in the menu bar. Sign in, choose the agents to monitor, then install the background collector.
Check it with shasum -a 256 Toolcaise-Connect-0.4.0-preview.2-macos-arm64.zip.
macOS
Intel
Open the ZIP, then open install-macos.command. It copies Toolcaise Connect to the Applications folder in your home folder and keeps the previous version when you upgrade.
Toolcaise Connect runs in the menu bar. Sign in, choose the agents to monitor, then install the background collector.
Check it with sha256sum toolcaise-connect-0.4.0-preview.2-linux-arm64.tar.gz.
From install to a verified connection
01
Sign in
Use the tray app or pairing command. Your browser shows the device name and asks which workspace should receive its reports.
02
Select tools
Choose recognized integrations. Detection alone does not enable collection or prove that a tool is monitored.
03
Check coverage
Run a small task in the connected tool, then check its activity in Toolcaise. Missing usage stays unknown.
Choose the connection that fits
Your environment
Connection
Coverage
Desktop agent tools
Tray app + supported adapter
Telemetry the selected tool exposes; capabilities vary by version.
Server or Raspberry Pi
Headless connector
Background delivery, connection health and selected integrations.
Agents already on the computer
Found by the connector on its own
Python, Node, PowerShell and shell scripts that use a model, running or scheduled. Monitoring one records each run's start, end and duration, and on Windows its exit code.
Custom script
Command wrapper or Python / Node SDK
Wrapper: exit and runtime. SDK: instrumented usage, checks and controls.
Cloud-hosted workflow
Direct HTTPS integration
Events explicitly sent by your workflow; a desktop installation cannot discover remote agents.
A connection test confirms delivery. Semantic correctness, token cost and safe pause support require evidence from the relevant integration. This connector does not grant a remote shell.