Using Harness

The harness path suits cases that need no custom code: the agent’s model, tools, knowledge base, memory, and prompt all live in a single 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 AK/SK credentials first, or obtain short-lived STS credentials through SSO login. harness deploy requires control-plane credentials; harness invoke uses control-plane credentials to resolve the Runtime and can pass an additional user token for custom_jwt Runtimes. See the Authentication section of the Quickstart.

harness deploy builds an image and creates or updates a cloud Runtime, which may incur charges. Updating an existing Runtime also changes its production behavior. Confirm the project, region, configuration, and credential references before deployment, and release changes during an appropriate operational window.

Initialize the harness

Create a harness directory containing harness.yaml and .env.example.

agentkit harness init my-harness
cd my-harness

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.

agentkit harness set \
  --name my-harness \
  --model-name ep-xxxxxxxx \
  --system-prompt "You are a concise, helpful agent." \
  --tools web_search

To configure a component such as a knowledge base or memory, set its --<component>-type first, then add the connection parameters; pass an empty string "" to disable one. Running agentkit harness set with no flags lists the current fields. See Harness for the full field list.

Build and deploy

Build the image in the cloud from harness.yaml and create or update the runtime.

agentkit harness deploy --project default --region cn-beijing

Invoke the runtime

Call the runtime you just deployed by name. The CLI resolves the endpoint and authentication automatically, using configured AK/SK credentials or valid STS credentials from the active SSO login profile.

agentkit harness invoke my-harness "Hello, introduce yourself"

Iterate

Change the configuration and redeploy to publish a new version; when the runtime misbehaves, read the instance logs to diagnose it.

agentkit harness set --name my-harness --system-prompt "The replacement instruction."
agentkit harness deploy
agentkit runtime logs my-harness --limit 200

When you no longer need the runtime, delete it to free resources:

Runtime deletion cannot be undone and stops production calls. Confirm the name, project, and region, and retain required configuration, logs, and business data before proceeding.

agentkit runtime delete my-harness -y

When you need custom logic, tools, or multi-agent orchestration, use High-code agents instead.

开始使用

AI-Friendly

命令参考