Deployment

Build, start, and verify a Goauld agent

Preparing an agent consists of compiling it with the correct server defaults and, once it is on the target machine, starting and verifying it.

Prerequisites

Before building the agent, confirm that:

  • the server is running and its required control and data listeners are reachable from the target network;
  • the client has the server’s matching age public key;
  • you know which outbound transports the target network permits; and
  • the server and client access tokens are configured.

For a complete first deployment, follow the multi-machine Quick Start.

Build the agent

Generate a build-variable template, edit it for the deployment, and compile the required operating-system and architecture target:

tealc compile --drop-env > env.txt
tealc compile --env env.txt --id agent --goos windows --goarch amd64

The binary is written below output/agent/. See Compile agent for build options and the distinction between the full agent and the agent stager.

Start the agent

Once the compiled agent is on the target machine, start it in the foreground so that configuration or transport errors are visible:

.\goauld_windows-amd64.exe

After validating the connection, store runtime options in the agent configuration file rather than in a world-readable command line.

Verify the deployment

From the operator workstation, run:

tealc list
tealc tui

Expected output from tealc list:

TODO_PLACEHOLDER_HERE

Then open a test session:

tealc ssh AGENT_NAME

If the agent is missing, use The agent does not appear. If it appears but SSH fails, use Control works, but SSH fails.

Operational constraints

  • An agent process restart ends active channels and in-memory persistent shell sessions.
  • Build-time values are defaults; supported runtime CLI, environment, and YAML values can override them.
  • Use working days and the killswitch when an engagement needs explicit operating windows or an automatic stop date.