> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/go-agent/go-agent-v1/agent-initialization-and-session-id.md).

# Agent Initialization & Session ID

Before running the build scan and tests, you must initialize the agent with the token to use and create a session ID.

## Initializing the SeaLights CLI <a href="#initializing-the-sealights-cli" id="initializing-the-sealights-cli"></a>

{% code overflow="wrap" lineNumbers="true" %}

```sh
./slcli config init --lang go --token ./sltoken.txt
```

{% endcode %}

## Generating a session ID <a href="#generating-a-session-id" id="generating-a-session-id"></a>

The Build Session uniquely identifies your application's build and associates any coverage (i.e., all test stages and tests) with that specific build. The session ID is provided for each step and command to link them together as one complete cycle.

{% code overflow="wrap" lineNumbers="true" %}

```sh
./slcli config create-bsid --app <your-app-name> --branch <your-branch-name> --build <your-build-number>
```

{% endcode %}

{% hint style="info" %}
Each time the command runs, the `app/branch/build` trio must be unique to create a new entry in your SeaLights instance. Usually, only `buildname` changes—make sure to generate a unique one each time. For that purpose, you can use a timestamp, e.g., `--build $(date +"%y%m%d_%H%M")` (Linux/macOS).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/go-agent/go-agent-v1/agent-initialization-and-session-id.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.