Sajay Antony sajayantony

KMX agent creator: Copilot and Claude driver POC

TL;DR

Use Copilot CLI or Claude Code as the conversational agent creator, while KMX remains the deterministic authority for:

validating a typed agent intent;
asking for missing human-owned configuration;
choosing the agent runtime and execution sandbox;

KMX sandbox picker: choosing the smallest compatible sandbox for an agent

TL;DR: Let the local coding agent describe requirements, not choose infrastructure directly. KMX should compile the agent and tool requirements into an explainable, portable sandbox plan:

Hyperlight JS for JavaScript-only tool execution with no shell, native packages, container image, or device access.
Hyperlight + Unikraft for ordinary Linux programs, Python/Node.js, shells, subprocesses, or native/dynamic packages.
Full pod sandbox when the workload needs an OCI image, devices/GPU, sidecars, volumes, or Kubernetes-native composition.

The selected backend and the requirements that caused the decision belong in the portable agent revision. Runtime adapters then translate that plan into platform-specific resources. KMX must refuse underspecified or incompatible choices and must not claim isolation until the runtime reports observed evidence.

KMX agent OpenTelemetry POC

Proven locally on Podman on September 28, 2026. Experimental evidence only.

Experience first

Run one command from the Kaimahi worktree:

cd poc/kmx-agent-otel

Researched and drafted with GitHub Copilot on September 25, 2026.

KMX Direction: Stable Workload Interfaces for Kubernetes

Date: September 25, 2026
Scope: Repositories under /Users/sajay/code/src/kaimahi-agents, organization-level .github material, kaimahi-agents/kaimahi#194, kaimahi-agents/kaimahi#223, and every revision of the gist linked by #223.

Executive Summary

Recommendation: KMX should be the stable, CLI-first workload-lifecycle layer through which agent and tool authors define, render, deploy, observe, evaluate, diff, and roll back workloads on Kubernetes. Authors should not need to depend on Orka, kagent, Azure, Kubernetes object schemas, or vendor SDKs. Orka and kagent should be internal built-in lifecycle implementations behind shared KMX contracts and selected by deployment/operator policy; Kubernetes mechanics should sit behind a separate target port; inference and cloud infrastructure should remain sibling domains.[^1][^2]

`kmx`: an agent developer entry point

Status: Proposal

kmx gives developers one command-line entry point for creating and running Kubernetes agents. It packages the working Kaimahi developer journey without replacing Kubernetes, kagent, or the agent YAML.

Quick start

ACR Image Purge — Keep Last N Images

Automated cleanup for Azure Container Registry repositories. Deploys a scheduled ACR task that retains only the last N images per repository and deletes the rest.

How It Works

The ACR task uses the built-in acr purge command with:

Flag	Value	Purpose

How to ssh to a remote server without typing your password

Save yourself a few keystrokes. Follow the steps below:

Run this Bash script on your laptop:
```
#!/usr/bin/env bash
```

The hostname of your remote server.

Configure ACR cache with Docker Hub token

Create a DockerHub Reaonly Access Token.

Create readonly token in the security tab - https://hub.docker.com/settings/security

Create a Keyvault to hold this access token

This is optional and you can use an existing keyvault

	#!/bin/bash

	echo 'linux/amd64' > README-linux-amd64.md
	echo 'linux/arm64' > README-linux-arm64.md

	# Push the artifact for amd64 and get the digest
	DIGEST_LINUX_AMD64=$(oras push --oci-layout layout-dir README-linux-amd64.md --format go-template='{{.digest}}')

	# Push the artifact for arm64 and get the digest
	DIGEST_LINUX_ARM64=$(oras push --oci-layout layout-dir README-linux-arm64.md --format go-template='{{.digest}}')

	#!/bin/bash

	# Variables
	acrName=
	resourceGroup=
	vmName=

	# Create ACR task with encoded YAML
	az acr task create \
	--name startvm \