launch-openshell-gator

Launch and supervise OpenShell gator sandbox agents for PR and issue review.

8.5k|1.3k|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/NVIDIA/OpenShell --skill launch-openshell-gator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-openshell-gator
Source: https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/launch-openshell-gator
Command: npx skills add https://github.com/NVIDIA/OpenShell --skill launch-openshell-gator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operating the repository's headless gator review agent requires careful preflight checks, gateway validation, scoped launch commands, and log-based supervision; this Skill encodes that entire operator workflow so gator launches are safe, validated, and correctly scoped.

Core Features & Use Cases

  • Preflight Validation: Verifies repository root, host tools (openshell, gh, jq, ruby), GitHub and Codex authentication, gateway health, and existing gator sandboxes before launching.
  • Scoped Supervised Launches: Starts gator watchers for PRs, issues, or linked pairs using scripts/agents/run.sh with --watch --background, strict input normalization, and DNS-1123 sandbox naming.
  • Monitoring and Restarting: Interprets log sentinels (waiting, blocked, transient_failure, terminal_failure, complete), inspects active sandboxes, and restarts stale or wedged gators after payload version bumps.
  • Use Case: A maintainer asks to run gator on PR #1234; the Skill validates the gateway and credentials, launches a supervised sandbox named gator-pr-1234-supervised, reads the background log, and reports the sandbox status and latest sentinel.

Quick Start

Launch a supervised gator agent to review and monitor pull request number 1234 on my registered OpenShell gateway.

Frequently Asked Questions about launch-openshell-gator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch a gator agent on a GitHub pull request?

Run scripts/agents/run.sh with --agent gator, a validated gateway name, a DNS-1123 sandbox name like gator-pr-<number>-supervised, and the --watch --background flags. The prompt must scope the invocation to the specific PR number.

What preflight checks are required before starting a gator sandbox?

Confirm the repository root, verify openshell, gh, jq, and ruby are installed, check GitHub auth with gh api user, validate Codex tokens in ~/.codex/auth.json, and confirm the target gateway responds to status and sandbox list commands.

How do I test a different Codex model with gator?

Set the CODEX_MODEL environment variable on the launch command instead of editing agent.yaml. For Codex CLI version changes, copy the gator directory to a temporary context and pass it with --from, leaving the repo Dockerfile unchanged.

Why does my gator sandbox show status terminal_failure?

A terminal_failure sentinel indicates an unrecoverable error or a stale immutable payload after a payload_version bump. Inspect the log reason, then delete the sandbox and relaunch with the updated payload.

What should I do when the OpenShell gateway is unreachable?

Stop retrying gator launches against the dead gateway. Load the debug-openshell-cluster skill to diagnose the gateway and runtime driver, fix the underlying problem, and only then relaunch gator.

When is it allowed to restart a running gator sandbox?

Restart when the payload changed, the sandbox is wedged without a sentinel, the model or tooling version changed, or transient failures repeat past the useful retry point. Leave actively producing review cycles running.