Run any Skill in Manus with one click

Get Started

examples-auto-run

Stars3,371

Forks843

UpdatedJune 23, 2026 at 22:24

Run examples:start-all in auto mode with parallel execution, per-script logs, and start/stop helpers.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

openai

openai/openai-agents-js

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	examples-auto-run
description	Run examples:start-all in auto mode with parallel execution, per-script logs, and start/stop helpers.

examples-auto-run

What it does

Runs pnpm build && pnpm -r build-check first
Runs pnpm examples:start-all in auto-input mode (interactive prompts are auto-answered, HITL/MCP/apply-patch are auto-approved).
Executes starts in parallel (default concurrency 4) and pipes each start’s stdout/stderr into its own log file under .tmp/examples-start-logs/.
Provides start/stop/status/logs/tail helpers via run.sh.
If the Codex session ends (no disown/nohup), the child processes receive SIGHUP and exit; stop is also available to clean up manually.

Usage

# Start (auto mode, concurrency=4 by default)
.agents/skills/examples-auto-run/scripts/run.sh start [extra args to examples:start-all]
# If you invoke the skill name alone ($examples-auto-run):
#   - when `.tmp/examples-rerun.txt` exists and is non-empty, it will run `rerun` automatically
#   - otherwise it runs the default `start` command.

# Examples:
.agents/skills/examples-auto-run/scripts/run.sh start --filter basic
.agents/skills/examples-auto-run/scripts/run.sh start --include-server --include-audio

# Check status
.agents/skills/examples-auto-run/scripts/run.sh status

# Stop running job (kills pid from .tmp/examples-auto-run.pid)
.agents/skills/examples-auto-run/scripts/run.sh stop

# List logs (per start script)
.agents/skills/examples-auto-run/scripts/run.sh logs

# Tail latest log
.agents/skills/examples-auto-run/scripts/run.sh tail
.agents/skills/examples-auto-run/scripts/run.sh tail basic__start_hello-world.log

# After a run, build a rerun list from the latest main log (auto-skip list is imported from `scripts/run-example-starts.mjs` and server/audio/external skips are honored)
.agents/skills/examples-auto-run/scripts/run.sh collect
# Rerun only the entries in .tmp/examples-rerun.txt
.agents/skills/examples-auto-run/scripts/run.sh rerun
# Show the current auto-skip list (env or defaults)
.agents/skills/examples-auto-run/scripts/run.sh start --print-auto-skip --dry-run

Defaults (overridable via env)

EXAMPLES_INTERACTIVE_MODE=auto
AUTO_APPROVE_MCP=1, APPLY_PATCH_AUTO_APPROVE=1, AUTO_APPROVE_HITL=1 (set in runner)
EXAMPLES_CONCURRENCY=4
- sandbox:start:memory-generation is still serialized by the runner because its pre-stop memory generation can contend with shared local resources. Other hosted, Unix-local, and Docker sandbox examples remain parallelized.
EXAMPLES_EXECA_TIMEOUT_MS=300000 (5m)
financial-research-agent and computer-use use 10m inside the script.
Includes interactive; excludes server/audio/external by default:
- EXAMPLES_INCLUDE_INTERACTIVE=1
- EXAMPLES_INCLUDE_SERVER=0
- EXAMPLES_INCLUDE_AUDIO=0
EXAMPLES_INCLUDE_EXTERNAL=0
- This means realtime-* / nextjs (tagged as server/audio) are skipped unless you opt in with --include-server / --include-audio or the corresponding env flags.
Auto-skip list: EXAMPLES_AUTO_SKIP (comma/space separated) overrides the built-in defaults used by both run.sh and run-example-starts.mjs. Defaults include agent-patterns:start:llm-as-a-judge, connectors:start, mcp:start:hosted-mcp-on-approval, mcp:start:hosted-mcp-human-in-the-loop, sandbox:start:vercel, tools:start:codex, tools:start:codex-same-thread.

Codex execution environment

When Codex invokes start or rerun, run the command outside the Codex sandbox by default (sandbox_permissions=require_escalated). Several examples start nested sandboxes, browsers, npm helpers, or local service processes; running from inside the Codex sandbox can produce environment-only failures such as Playwright browser launch permission errors, npm cache permission errors, or nested sandbox setup errors.
Use sandboxed execution only when the user explicitly asks for it or when running a narrow dry-run / log inspection command that does not execute examples.

Cancellation / cleanup

Jobs are backgrounded but not disowned; if Codex suspends/ends the shell, the process group gets SIGHUP and stops.
Manual cleanup: run.sh stop (removes stale pid if already exited).

Log locations

.tmp/examples-start-logs/<package>__<script>.log (per start)
Main runner log path is printed when start is invoked.
Rerun list (generated by collect): .tmp/examples-rerun.txt (one package:script per line).

Notes

Auto-skip is centralized (same defaults as above) and can be overridden via EXAMPLES_AUTO_SKIP. Auto-skip entries are excluded from rerun collection and will be removed from rerun execution automatically.
Auto-input map covers common interactive prompts; HITL/MCP/apply-patch auto-approve via env is enabled by the runner.
Shell tool approvals are auto-approved in auto mode (SHELL_AUTO_APPROVE=1).
rerun runs entries sequentially, continues after failures, and rewrites .tmp/examples-rerun.txt with only the remaining failures. Auto-skip entries are not re-added.
Behavioral validation is not done in the runner, so Codex must immediately perform it after every start or rerun invocation without waiting for the user to ask. Required steps:
1. Read the example source to infer intended flow from code/comments (tools invoked, expected outputs, guards, approvals).
2. Read the matching log under .tmp/examples-start-logs/.
3. Compare intent vs. log: confirm key actions/results happened; flag omissions or divergences.
4. Do this for all exit-0 entries, not just samples.
5. Summarize findings right after the run completes; when “OK”, note what was checked (e.g., “tools called + final message emitted”).
6. When reporting, do not omit or ellipsize outputs that justify the validation; include the full relevant lines (keep it concise but untruncated).
The runner prints a full table after the summary: one row per start script with status, package:script, info (reason/exit/skipped), and the log path. If the run stops before the table appears, point the analyzer at the latest main_*.log to reconstruct a table and validations.

More from this repository

same repository

code-change-verification

openai/openai-agents-js

Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents JS monorepo.

2026-07-113.4k

runtime-behavior-probe

openai/openai-agents-js

Plan and execute runtime-behavior investigations with temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports. Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks, especially to uncover edge cases, undocumented behavior, or common failure modes in local or live integrations. A baseline smoke check is fine as an entry point, but do not stop at happy-path confirmation.

2026-07-043.4k

maintainer-review

openai/openai-agents-js

Review a GitHub issue or pull request URL as an openai-agents-js maintainer, with a staged assessment of whether the claim is real, practically important, already solvable with supported functionality, correctly scoped, better served by another design, and worth maintainer and contributor effort. Use when assessing issue validity or severity, deciding whether an issue should be prioritized or closed, determining whether a requested feature represents an unmet need rather than a discoverability or usage gap, judging whether a PR is worth bringing to mergeable quality, comparing open PRs or alternative designs, separating code quality from repository readiness, or drafting a concise maintainer assessment. When closure, additional evidence, or code changes should be requested, also produce a polite, concise, complete, copy-paste-ready maintainer comment.

2026-07-043.4k

pr-draft-summary

openai/openai-agents-js

Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-js. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.

2026-06-183.4k

implementation-strategy

openai/openai-agents-js

Decide how to implement runtime and API changes in openai-agents-js before editing code. Use when a task changes exported APIs, runtime behavior, schemas, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewritten directly.

2026-05-123.4k

integration-tests

openai/openai-agents-js

Run the integration-tests pipeline that depends on a local npm registry (Verdaccio). Use when asked to execute integration tests or local publish workflows in this repo.

2026-05-103.4k

examples-auto-run

What it does

Runs pnpm build && pnpm -r build-check first

Runs pnpm examples:start-all in auto-input mode (interactive prompts are auto-answered, HITL/MCP/apply-patch are auto-approved).

Executes starts in parallel (default concurrency 4) and pipes each start’s stdout/stderr into its own log file under .tmp/examples-start-logs/.

Provides start/stop/status/logs/tail helpers via run.sh.

If the Codex session ends (no disown/nohup), the child processes receive SIGHUP and exit; stop is also available to clean up manually.

Usage

# Start (auto mode, concurrency=4 by default) .agents/skills/examples-auto-run/scripts/run.sh start [extra args to examples:start-all] # If you invoke the skill name alone ($examples-auto-run): # - when `.tmp/examples-rerun.txt` exists and is non-empty, it will run `rerun` automatically # - otherwise it runs the default `start` command. # Examples: .agents/skills/examples-auto-run/scripts/run.sh start --filter basic .agents/skills/examples-auto-run/scripts/run.sh start --include-server --include-audio # Check status .agents/skills/examples-auto-run/scripts/run.sh status # Stop running job (kills pid from .tmp/examples-auto-run.pid) .agents/skills/examples-auto-run/scripts/run.sh stop # List logs (per start script) .agents/skills/examples-auto-run/scripts/run.sh logs # Tail latest log .agents/skills/examples-auto-run/scripts/run.sh tail .agents/skills/examples-auto-run/scripts/run.sh tail basic__start_hello-world.log # After a run, build a rerun list from the latest main log (auto-skip list is imported from `scripts/run-example-starts.mjs` and server/audio/external skips are honored) .agents/skills/examples-auto-run/scripts/run.sh collect # Rerun only the entries in .tmp/examples-rerun.txt .agents/skills/examples-auto-run/scripts/run.sh rerun # Show the current auto-skip list (env or defaults) .agents/skills/examples-auto-run/scripts/run.sh start --print-auto-skip --dry-run

Defaults (overridable via env)

EXAMPLES_INTERACTIVE_MODE=auto

AUTO_APPROVE_MCP=1, APPLY_PATCH_AUTO_APPROVE=1, AUTO_APPROVE_HITL=1 (set in runner)

EXAMPLES_CONCURRENCY=4

sandbox:start:memory-generation is still serialized by the runner because its pre-stop memory generation can contend with shared local resources. Other hosted, Unix-local, and Docker sandbox examples remain parallelized.

EXAMPLES_EXECA_TIMEOUT_MS=300000 (5m)
financial-research-agent and computer-use use 10m inside the script.

Includes interactive; excludes server/audio/external by default:

EXAMPLES_INCLUDE_INTERACTIVE=1
EXAMPLES_INCLUDE_SERVER=0
EXAMPLES_INCLUDE_AUDIO=0

EXAMPLES_INCLUDE_EXTERNAL=0

This means realtime-* / nextjs (tagged as server/audio) are skipped unless you opt in with --include-server / --include-audio or the corresponding env flags.

Auto-skip list: EXAMPLES_AUTO_SKIP (comma/space separated) overrides the built-in defaults used by both run.sh and run-example-starts.mjs. Defaults include agent-patterns:start:llm-as-a-judge, connectors:start, mcp:start:hosted-mcp-on-approval, mcp:start:hosted-mcp-human-in-the-loop, sandbox:start:vercel, tools:start:codex, tools:start:codex-same-thread.

Codex execution environment

When Codex invokes start or rerun, run the command outside the Codex sandbox by default (sandbox_permissions=require_escalated). Several examples start nested sandboxes, browsers, npm helpers, or local service processes; running from inside the Codex sandbox can produce environment-only failures such as Playwright browser launch permission errors, npm cache permission errors, or nested sandbox setup errors.

Use sandboxed execution only when the user explicitly asks for it or when running a narrow dry-run / log inspection command that does not execute examples.

Cancellation / cleanup

Jobs are backgrounded but not disowned; if Codex suspends/ends the shell, the process group gets SIGHUP and stops.

Manual cleanup: run.sh stop (removes stale pid if already exited).

Log locations

.tmp/examples-start-logs/<package>__<script>.log (per start)

Main runner log path is printed when start is invoked.

Rerun list (generated by collect): .tmp/examples-rerun.txt (one package:script per line).

Notes

Auto-skip is centralized (same defaults as above) and can be overridden via EXAMPLES_AUTO_SKIP. Auto-skip entries are excluded from rerun collection and will be removed from rerun execution automatically.

Auto-input map covers common interactive prompts; HITL/MCP/apply-patch auto-approve via env is enabled by the runner.

Shell tool approvals are auto-approved in auto mode (SHELL_AUTO_APPROVE=1).

rerun runs entries sequentially, continues after failures, and rewrites .tmp/examples-rerun.txt with only the remaining failures. Auto-skip entries are not re-added.

Behavioral validation is not done in the runner, so Codex must immediately perform it after every start or rerun invocation without waiting for the user to ask. Required steps:

Read the example source to infer intended flow from code/comments (tools invoked, expected outputs, guards, approvals).
Read the matching log under .tmp/examples-start-logs/.
Compare intent vs. log: confirm key actions/results happened; flag omissions or divergences.
Do this for all exit-0 entries, not just samples.
Summarize findings right after the run completes; when “OK”, note what was checked (e.g., “tools called + final message emitted”).
When reporting, do not omit or ellipsize outputs that justify the validation; include the full relevant lines (keep it concise but untruncated).

The runner prints a full table after the summary: one row per start script with status, package:script, info (reason/exit/skipped), and the log path. If the run stops before the table appears, point the analyzer at the latest main_*.log to reconstruct a table and validations.