> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veadk.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# High-code agents

The high-code path suits cases that need custom logic, tools, or multi-agent orchestration: you scaffold a project from a template, write the agent code directly, and let the CLI build the image in the cloud and deploy it as a runtime. The loop starts at scaffolding and runs through editing, deploying, invoking, and reading logs, then returns to editing to iterate.

> [!NOTE]
>
> Configure AK/SK credentials first, or obtain short-lived STS credentials through [SSO login](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/commands/auth.md). `launch`, `deploy`, and `invoke` use the same credential precedence to resolve valid credentials. See the Authentication section of the [Quickstart](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/quickstart.md). For the full guide to writing agent code, see the [VeADK 1.0.9 docs](https://docs.veadk.xyz/productions/veadk/archives/1.0.9/en/index.md).

**1. Scaffold a project**

Create a project from a built-in template. Run `agentkit init --list-templates` to list every template first.

```bash lines theme={null}
agentkit init my-agent --template basic
cd my-agent
```

**2. Edit the agent**

Modify the scaffolded code to adjust the agent's instruction, tools, and orchestration logic.

> [!NOTE]
>
> The runtime container must listen on `0.0.0.0:8000` to pass its readiness probe. Templates satisfy this by default, so you rarely need to change it.

**3. Build and deploy**

Run the full lifecycle flow, building the image in the cloud and creating or updating the runtime.

```bash lines theme={null}
agentkit launch
```

> [!TIP]
>
> To inspect or hand-edit `agentkit.yaml` or the `Dockerfile` between scaffolding and building, run `agentkit config --show`, then split the flow into `agentkit build` and `agentkit deploy`. See [Config](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/commands/config.md), [Build](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/commands/build.md), and [Deploy](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/commands/deploy.md).

**4. Invoke the runtime**

Call the runtime by name to verify the deployment.

```bash lines theme={null}
agentkit invoke my-agent -m "Hello, introduce yourself"
```

**5. Inspect and iterate**

Read the logs when the runtime misbehaves; edit the code and redeploy to publish a new version.

```bash lines theme={null}
agentkit runtime logs my-agent --limit 200
agentkit launch
```

To roll back or adjust resources, use the version and update commands: list history with `agentkit runtime versions my-agent`, publish a specific version with `agentkit runtime release my-agent --rev <n>`, and change CPU and memory with `agentkit runtime update my-agent --cpu-milli 1000 --memory-mb 2048 --auto-release`.

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

```bash lines theme={null}
agentkit runtime delete my-agent -y
```

When you only need configuration and no code, use [Using Harness](https://docs.veadk.xyz/productions/agentkit-cli/archives/0.51.1/en/workflows/harness) instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.