skills.rest
adminlove520
adminlove520COMMUNITY
Explore all skills by this author →
GitHub

remote-tests

Run Codex integration tests against a remote docker executor via scripts/test-remote-env.sh.

Updated Aug 27, 2026
Search Tags:#codex#docker#integration-testing#remote#tests#devbox#remote-executor
One-click install
npx skills add https://github.com/adminlove520/Claude-Code-Universe --skill remote-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-tests
Source: https://github.com/adminlove520/Claude-Code-Universe/tree/main/codex/.codex/skills/remote-tests
Command: npx skills add https://github.com/adminlove520/Claude-Code-Universe --skill remote-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Some codex integration tests support running against a remote executor. This means that when CODEX_TEST_REMOTE_ENV environment variable is set they will attempt to start an executor process in a docker container CODEX_TEST_REMOTE_ENV points to and use it in tests.

Docker container is built and initialized via ./scripts/test-remote-env.sh

Currently running remote tests is only supported on Linux, so you need to use a devbox to run them

You can list devboxes via applied_devbox ls, pick the one with codex in the name. Connect to devbox via ssh <devbox_name>. Reuse the same checkout of codex in ~/code/codex. Reset files if needed. Multiple checkouts take longer to build and take up more space. Check whether the SHA and modified files are in sync between remote and local.

Frequently Asked Questions about remote-tests

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

FAQPage Schema
How do I run Codex integration tests against a remote executor?▼

To run Codex integration tests against a remote executor, set the CODEX_TEST_REMOTE_ENV environment variable to point to a Docker container, which the tests will automatically detect and use to spawn the executor process.

What is the CODEX_TEST_REMOTE_ENV environment variable used for?▼

The CODEX_TEST_REMOTE_ENV environment variable specifies the target Docker container for remote test execution. When set, it triggers integration tests to start an executor process inside that container rather than running locally.

How do I build and initialize the Docker container for remote test execution?▼

You build and initialize the Docker container for remote test execution by running the provided scripts/test-remote-env.sh script on your Linux devbox before starting the integration tests.

Can I run remote integration tests on macOS or Windows?▼

Running remote integration tests is currently only supported on Linux. You must connect to a Linux devbox via SSH, select a devbox with 'codex' in the name using applied_devbox ls, and execute the tests from there.

Why do my local and remote Codex test environments fail to synchronize?▼

Local and remote test environments fail to synchronize if the Git SHA and modified files between your local checkout and the remote devbox are not aligned. You must manually verify and reset the shared checkout to keep them in sync.

Related Skills

Explore More Software Engineering Skills→
xrehpicxxrehpicx
4

remote-tests

Launch a Docker executor for remote test execution in Linux environments.

Community
Intermediate
golemcloudgolemcloud
1.5k

investigating-executor-performance

Run worker-executor tests with OTLP tracing and analyze trace data in Jaeger.

Official
Advanced
NagyViktNagyVikt
2

sandbox-sdk

Execute untrusted code in isolated containers within Cloudflare Workers.

Community
Advanced
AarononthewebAaronontheweb
1.1k

testcontainers-integration-tests

Run .NET integration tests against Docker containers using TestContainers.

Community
Advanced