From request to pull request. Without losing the thread.

Go 1.26+ is required only to develop Pajé, which happens to be implemented in Go; Go-native positioning is inconsequential. The target repository can use any language: include its toolchain in the worker image. For the beta, prepare Docker, Helm 3, Hatchet, and Codex authentication.

Build the image with an auditable revision and apply the chart after configuring separate Secrets.

git clone https://github.com/araihu/paje.git
cd paje

PAJE_COMMIT="$(git rev-parse --verify 'HEAD^{commit}')"
docker build \
  --build-arg CODEX_VERSION=0.144.5 \
  --build-arg PAJE_COMMIT="$PAJE_COMMIT" \
  -t ghcr.io/your-org/paje:beta .

helm upgrade --install paje ./charts/paje \
  --namespace paje --create-namespace \
  --values values.production.yaml

Today, start paje-code-change-v1 in Hatchet. The intended integration will move this trigger into harness hooks and skills. Use profile: generic with explicit checks and the toolchain present in the image. The go profile is only a convenience for module discovery and test defaults.

{
  "run_id": "73f659b2-eaee-4c37-8784-48fab274b3e8",
  "input": {
    "idempotency_key": "client-timeout-20260725",
    "task_description": "Increase the client timeout and update the tests.",
    "repository_uri": "https://github.com/example/service.git",
    "base_ref": "main",
    "memory_query": "HTTP client conventions",
    "memory_limit": 5,
    "tags": {
      "user_id": "operator@example.com",
      "app_id": "service"
    },
    "profile": "generic",
    "checks": [
      {
        "name": "test",
        "executable": "npm",
        "args": [
          "test"
        ],
        "timeout": "10m",
        "required": true
      }
    ],
    "publication": {
      "mode": "artifact"
    }
  }
}

To create a draft PR, use publication.mode: pull_request. The approval phase waits for the event paje:approval:<run-id> with the same run and digest. If anything changes, the decision is not reused.