Docs cloud
Install the Cloud collector
Enroll a RetrySight Cloud laptop collector against cloud-staging.retrysight.com with the dashboard script and native packages that ship a bundled JRE.
On this page
Agents always run on developer machines. You do not install a JDK — native Cloud packages embed a JRE.
Prerequisites
- A Cloud account and the agent API key (
rk_live_*) from signup - Local coding-agent logs (Cursor, Claude Code, Codex, and others)
- Outbound HTTPS to
https://cloud-staging.retrysight.com
Recommended — dashboard enroll
- Sign in at cloud-staging.retrysight.com.
- Open Welcome, Account, or Collectors (empty state).
- Download the enroll script for your OS and run it. It writes
~/.agent-retry/config.yaml(manager URL + API key), then installs the native package. - macOS/Linux may ask for an administrator password. Windows may show SmartScreen.
| OS | Package on get.retrysight.com/saas/agent/0.1.0/ | Auto-start |
|---|---|---|
| macOS | RetrySightAgent.pkg | LaunchAgent com.retrysight.agent |
| Linux | retrysight-agent.deb | systemd user unit retrysight-agent.service |
| Windows | RetrySightAgent.msi | Scheduled Task RetrySightAgent |
Portable agent-app.jar is for from-source or Docker collectors, not the default path.
After the first heartbeat, the manager assigns an agent ID. The collector stores it in ~/.agent-retry/agent-id and sends X-Agent-Id on later ingest. Copy the same ID from Collectors.
Verify
Within about 10 seconds:
- Open Collectors.
- Find this machine’s hostname.
- Status Online with a recent heartbeat.
- Open the row for Agent ID.
Use Cursor/Claude/Codex locally. Tasks show on Tasks and Dashboard after one upload batch (default 10 seconds). Offline events buffer in SQLite at ~/.agent-retry/buffer.db and upload when connectivity returns.
Optional ingest smoke
curl -s -X POST "https://cloud-staging.retrysight.com/api/v1/ingest/heartbeat" \
-H "Content-Type: application/json" \
-H "X-Agent-Api-Key: rk_live_YOUR_ACCOUNT_KEY" \
-d '{
"hostname": "manual-test",
"developerEmail": "you@company.com",
"activeCollectors": ["CURSOR"],
"queueDepth": 0,
"reportedAt": "'"$(date -u +%Y-%m-%dT%H:%M:%SZ)"'"
}'
Expect HTTP 200 or 201. 401 — wrong key. 403 — account suspended or trial expired.
Config-only (from-source)
mkdir -p ~/.agent-retry
agent:
manager:
url: https://cloud-staging.retrysight.com
api-key: rk_live_YOUR_ACCOUNT_KEY
platform:
auto-discovery: true
Environment equivalent: AGENT_MANAGER_URL and AGENT_MANAGER_API_KEY. Full file: Cloud config.
Uninstall this machine
Stop the collector, remove the app, then delete local state (~/.agent-retry).
macOS
launchctl bootout "gui/$(id -u)/com.retrysight.agent" 2>/dev/null || true
rm -f ~/Library/LaunchAgents/com.retrysight.agent.plist
rm -rf ~/.agent-retry ~/.retrysight-agent ~/Library/Logs/RetrySight
sudo rm -rf /Applications/RetrySightAgent.app
sudo pkgutil --forget com.retrysight.agent.cloud
Linux: systemctl --user disable --now retrysight-agent.service, then dpkg -r retrysight-agent.
Windows: stop Scheduled Task RetrySightAgent, uninstall the MSI, remove %USERPROFILE%\.agent-retry.
Uninstalling a laptop does not delete the Cloud account or server-side data.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| HTTP 401 on ingest | Wrong or missing API key | Copy key from Account |
| HTTP 403 on ingest | Account suspended or trial expired | Account admin / contact |
| Agent shows in the wrong account | Key from another org | Use only your account’s rk_live_* key |
| Dashboard empty | Collector not running or no local agent activity | Start collector; use an IDE agent |
Connection refused | Wrong manager URL | Must be https://cloud-staging.retrysight.com (agent.manager.url) |
| Stale collector | Heartbeat older than stale-after-seconds | Restart collector; check firewall/proxy |
Corporate proxy: agent.manager.proxy-host / proxy-port, or HTTP_PROXY / HTTPS_PROXY. See config.
Related
Dashboard · Collector matrix · Enterprise unsigned packages (self-hosted, different CDN)