Getting Started

Prerequisites

  • SeaLights Account: Active SeaLights account with access credentials

  • Authentication Token: Valid SeaLights Agent token (stored as sltoken.txt or injected via environment variable)

  • Supported Go Version: The SeaLights Go Agent maintains support in line with what Golang itself supports, which is generally "from 2 versions ago" (At the time of this writing, Go 1.24+)

  • Go Agent Binary: Downloaded slgoagent binary placed in your project directory

  • Network Access: Ability to connect to SeaLights servers (check firewall/proxy settings if needed)

Downloading the Go Agent

The SeaLights Go Agent is distributed as a binary archive. Download and extract it to your project directory before proceeding.

Using an internal artifact repository? If your organization mirrors SeaLights agents in an internal repository (such as JFrog Artifactory, Nexus, or alike), replace the download URL with your internal repository endpoint. The download path structure remains the same.

Choosing a Download Strategy

Strategy
When to use

Latest

Quick start, dev/sandbox environments, POC

Specific version

Production pipelines — set via API (recommended) or hardcoded

For convenience, the table below contains direct links to the latest version of the SeaLights Go Agent:

OS
Architecture
V2 Download Link

Linux

x86-64

https://agents.sealights.co/slgoagent/latest/slgoagent-linux-amd64.tar.gz

Linux

ARM64

https://agents.sealights.co/slgoagent/latest/slgoagent-linux-arm64.tar.gz

macOS

x86-64

https://agents.sealights.co/slgoagent/latest/slgoagent-darwin-amd64.tar.gz

macOS

ARM64

https://agents.sealights.co/slgoagent/latest/slgoagent-darwin-arm64.tar.gz

Strategy 1: Always Download the Latest Version

Suitable for development environments where you always want the newest capabilities and can tolerate potential breaking changes between runs.

Tip: For production pipelines, leave SL_AGENT_VERSION empty in the snippet below to automatically resolve (via API call) the version your administrator has approved in the Dashboard settings dedicated page.

  • When the approved version changes, every pipeline picks it up automatically on the next run — no edits required.

  • When troubleshooting, set it to latest or pin it to a specific version (e.g. v2.0.225).

API Endpoint:

  • Authentication: Authorization: Bearer <your-agent-token>

  • Response: JSON object with a version field, e.g. {"version": "v2.0.225"}

Last updated

Was this helpful?