You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c8afb73
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/launch-openshell-gator/SKILL.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,20 @@ The launcher passes the non-secret host account ID as literal `CODEX_ACCOUNT_ID`
84
84
85
85
The image contains task-independent tooling and a prompt template, not the run's PR assignment or test authorization. The launcher supplies those instructions at runtime through `OPENSHELL_AGENT_TASK` in the canonical process command. The supervisor captures the assembled prompt in memory and supplies it on stdin for every cycle. Task text is non-secret and may appear in runtime command metadata; never put credentials in the task. Task-only changes reuse the same tooling build inputs, although the launcher still builds/tags an image per invocation.
86
86
87
+
For Kubernetes gateways, select image delivery explicitly: `--k3d-cluster NAME`
88
+
builds with Docker and imports into a running local cluster with the matching
89
+
current kube context; `--publish-image REGISTRY/REPOSITORY:TAG` builds and pushes,
90
+
then launches by resolved digest; `--image REGISTRY/REPOSITORY@sha256:DIGEST`
91
+
reuses trusted compatible tooling without local image tools. Do not infer
92
+
locality from a loopback endpoint. The k3d selection asserts which cluster
93
+
serves the gateway; imported images require `if_not_present` or `never` pull
94
+
policy. Registry builds use the builder's platform and existing registry auth;
95
+
nodes need their own pull access. `--build-only` builds/delivers without
96
+
gateway mutations, provider credential reads, or a sandbox launch. Reused
97
+
images must match the local manifest's agent ID and payload version and support
98
+
the runtime task contract; legacy baked-task images fail startup. See
99
+
`scripts/agents/gator/README.md` for examples and option compatibility.
100
+
87
101
### Step 5: Verify Gateway Is Registered And Alive
88
102
89
103
Use the target gateway from the operator request or current session context. Do not assume a gateway name. If the operator did not specify one, list registered gateways and ask before launching when the correct target is ambiguous.
"Review and monitor PR #${pr_number} through the gator-gate workflow. Scope this invocation only to PR #${pr_number}."
166
180
```
167
181
168
-
The launcher queries the gateway's selected compute driver, builds the gator image in the matching Docker or Podman image store, stages the immutable payload, imports provider profiles, configures provider credentials and refresh, and starts the agent supervisor as the sandbox's canonical main process. The detached main process survives loss of the host CLI connection and reconnects to a restarted gateway. Unless `--keep` is set, the sandbox is marked ephemeral so the gateway deletes it after the canonical main process exits and its terminal result is finalized. `CONTAINER_ENGINE`, when set, must match the gateway driver.
182
+
The launcher queries the gateway's selected compute driver and prepares the image through the selected build/import/publish or prebuilt path before importing provider profiles, configuring provider credentials and refresh, and starting the agent supervisor as the sandbox's canonical main process. The detached main process survives loss of the host CLI connection and reconnects to a restarted gateway. Unless `--keep` is set, the sandbox is marked ephemeral so the gateway deletes it after the canonical main process exits and its terminal result is finalized. `CONTAINER_ENGINE`, when set, must match Docker/Podman gateways or Docker for k3d imports; registry builds for Kubernetes may use either local engine.
169
183
170
184
The launcher streams image-build and provisioning output until the detached workload is ready, then exits. Use `openshell logs <sandbox-name>` or the TUI for runtime output.
Copy file name to clipboardExpand all lines: scripts/agents/gator/README.md
+72-6Lines changed: 72 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ Launch a headless sandbox agent that runs the `gator-gate` skill against OpenShe
7
7
-`gh` is authenticated on the host and has access to `NVIDIA/OpenShell`.
8
8
- For `--harness codex`, `codex login` has created `$HOME/.codex/auth.json`.
9
9
- For `--harness codex`, local Codex auth must include an access token, refresh token, and account ID.
10
-
- A local gateway and either Dockeror Podman are available to build the
11
-
default sandbox image.
10
+
- A Docker, Podman, or Kubernetes gateway is available. Local builds require
11
+
Docker or Podman; a prebuilt image does not require a local container engine.
12
12
13
13
## Usage
14
14
@@ -24,11 +24,75 @@ By default the launcher uses `scripts/agents/gator/Dockerfile` as the sandbox im
24
24
25
25
The PR assignment, operator test authorization, harness selection, watch mode, and polling interval are runtime inputs, not rendered image contents. The launcher supplies the non-secret assignment as `OPENSHELL_AGENT_TASK` in the canonical process command. The supervisor assembles the prompt once in memory and sends it to each harness cycle on stdin; cycles do not read task instructions from an agent-writable file. Assignment text is literal data, so shell syntax and template tokens inside it are not evaluated. Do not put credentials in assignments; use providers. Runtime command metadata can contain the assignment. This separates reusable tooling from per-run instructions; it does not make prompt instructions a security boundary.
26
26
27
-
The launcher still builds and tags an image for each invocation, but task-only or supervision-setting changes reuse identical tooling build inputs. Publishing and selecting reusable images is a separate launcher capability.
27
+
Without `--image`, the launcher builds and tags an image for each invocation,
28
+
but task-only or supervision-setting changes reuse identical tooling build
29
+
inputs. Docker and Podman builds use the gateway's engine; an explicit
30
+
`CONTAINER_ENGINE` must match it.
28
31
29
-
The launcher queries the selected gateway and builds with its Docker or Podman
30
-
compute driver. If `CONTAINER_ENGINE` is set, it must match that driver. Other
31
-
gateway drivers cannot run this local-image launcher.
32
+
## Kubernetes image delivery
33
+
34
+
The launcher discovers the compute driver from the selected gateway. It does
35
+
not infer a local cluster from a loopback gateway endpoint: that endpoint could
36
+
be a port-forward to a remote deployment. Select one of these image paths for
37
+
a Kubernetes gateway.
38
+
39
+
For local k3d, explicitly identify the cluster serving the gateway. The launcher
40
+
requires the matching current kube context and a running local cluster, builds
41
+
with Docker, and imports the image into that cluster before creating a sandbox:
42
+
43
+
```shell
44
+
OPENSHELL_WORKSPACE=gator mise exec[email protected] -- ./scripts/agents/run.sh \
"Review and monitor PR #1234 through the gator-gate workflow."
78
+
```
79
+
80
+
Set `GATOR_IMAGE` to the printed digest-pinned reference, not a mutable tag.
81
+
`--image` skips local builds and cluster imports and works with Docker/Podman
82
+
gateways too. It cannot be combined with `--from`, `--codex-bin`,
83
+
`--k3d-cluster`, `--publish-image`, or `--build-only`. The image must contain
84
+
tooling built by this launcher with the same agent ID and payload version as
85
+
the local manifest. Startup validates that contract before running the agent;
86
+
legacy images with baked assignments are incompatible. Only reuse trusted
87
+
tooling images: the contract check does not authenticate their contents.
88
+
89
+
Omit `--build-only` from `--publish-image` to build, push, and launch in one
90
+
invocation. A failed push, missing repository digest, or failed k3d import
91
+
stops the launcher before gateway settings, provider configuration, or sandbox
92
+
creation. Kubernetes launches without an explicit image-delivery choice fail
93
+
with guidance rather than guessing a cluster or registry.
94
+
95
+
## Runtime and providers
32
96
33
97
Use `--harness codex` to select Codex explicitly. Other harness names are rejected until their support is added to `agent.yaml` and `scripts/agents/runtime/harnesses/<name>/`. Agent directories do not carry their own harness implementations; they provide prompt templates and optional skills or subagents for the shared runtime to inject.
0 commit comments