Support
Need help setting up a Mac mini or Linux fleet, running strict doctor, or configuring optional Cloud Monitoring?
Run local diagnostics first
Most host issues (APFS unallocated container space, macOS sleep timeouts, systemd --user linger, expired Tailscale node keys, or missing Xcode license acceptance) surface immediately via Strict's read-only preflight command:
strict doctor && strict statusReview the Installation & Fleet Architecture Docs for setup steps, Tailnet build cache troubleshooting, and runner enrollment commands.
Contact support
Email support@strict.ai. To help resolve your issue quickly, include:
- Whether you run Standalone mode (
standalone.tsbehindtailscale serve) or Strict Cloud Monitoring (strict.ai). - Your host OS, architecture (e.g., macOS Apple Silicon or Linux x86_64/ARM64), and
strict doctoroutput. - Never email pairing codes, raw
str_v1_...agent tokens, Tailscale OAuth secrets, or webhook URLs.
Report a security issue
Email security@strict.ai with a clear reproduction report and affected component (macOS app, Python agent, Standalone server, or Cloud Worker). Please allow reasonable time to validate and ship a fix before public disclosure.
Privacy & deletion requests
For account export, workspace deletion, or privacy questions regarding optional Cloud Monitoring, email privacy@strict.ai or follow Data deletion instructions.