harness.yaml, which the CLI builds and deploys as a runtime. The whole loop revolves around that one file — initialize, configure, deploy, invoke, then return to configuration to iterate.
Configure credentials first.
harness deploy is a control-plane operation and requires AK/SK; SSO login currently only covers invoking (invoke) a deployed runtime. See the Authentication section of the Quickstart.1
Initialize the harness
Create a harness directory containing
harness.yaml and .env.example.2
Configure the agent
Write fields with
harness set. Only the flags you pass are modified, so you can build up the configuration across several calls.3
Build and deploy
Build the image in the cloud from
harness.yaml and create or update the runtime.4
Invoke the runtime
Call the runtime you just deployed by name; the CLI resolves the endpoint and auth automatically. Invocation is a data-plane operation, so either credential type works: AK/SK, or the STS credentials from an
agentkit login SSO session.5
Iterate
Change the configuration and redeploy to publish a new version; when the runtime misbehaves, read the instance logs to diagnose it.