# Launch Openshell Gator

Launch and supervise OpenShell gator agents.

- Repository: https://github.com/NVIDIA/OpenShell (20903 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add NVIDIA/OpenShell --skill launch-openshell-gator -g -a claude-code -y`
Codex: `npx skills add NVIDIA/OpenShell --skill launch-openshell-gator -g -a codex -y`
Cursor: `npx skills add NVIDIA/OpenShell --skill launch-openshell-gator -g -a cursor -y`
Gemini CLI: `npx skills add NVIDIA/OpenShell --skill launch-openshell-gator -g -a gemini-cli -y`

## Description

Launch and supervise OpenShell gator agents. Use when starting gator on issues or PRs, checking gator sandboxes, building the gator sandbox image, restarting stuck gators, inspecting gator logs, or experimenting with gator harness/model overrides. Trigger keywords - launch gator, start gator, run gator, gator sandbox, supervised gator, gator logs, restart gator.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Launch OpenShell Gator

Launch and supervise the repository's headless gator sandbox agent through OpenShell. This skill covers the operator workflow around `scripts/agents/run.sh`; the in-sandbox review and state-machine policy remains the `gator-gate` skill baked into the gator payload.

For gator's PR/issue validation policy, load `gator-gate` inside the launched sandbox. For generic sandbox CLI usage, use `openshell-cli`. For unhealthy gateways or sandbox startup failures, use `debug-openshell-cluster` after the launch preflight identifies a gateway/runtime problem.

## Non-Negotiable Rules

- Keep normal gator launches supervised: use `--watch` and let the in-sandbox supervisor own sleeping and relaunching bounded cycles.
- Do not add passive `sleep` loops in the operator session to watch gator. Check logs or status once, then report the current state or launch a proper watcher outside the model session only when explicitly asked.
- Do not change the default gator model in `scripts/agents/gator/agent.yaml` for experiments. Use `CODEX_MODEL=...` and, if needed, a temporary `--from` Docker context or `--codex-bin` override.
- Do not push to contributor branches, approve, merge, post `/ok to test`, or broaden gator scope unless the operator explicitly authorized that action.
- Scope each launch prompt to the requested issue/PR set. Avoid repo-wide gator scans unless the operator asked for repo-wide processing.
- Leave unrelated local files alone, including `.opencode/` artifacts and old gator logs unless the user asks for cleanup.

## Key Paths

The rest: https://github.com/NVIDIA/OpenShell/blob/HEAD/.agents/skills/launch-openshell-gator/SKILL.md