MongoDB Source Connector E2E Harness
airbytehq/airbyte
Starts a throwaway MongoDB 7.0 replica set and runs the Airbyte spec, check, discover and read commands against source-mongodb-v2 images for local end-to-end testing.
Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.
Install Remote Executor Integration Tests
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openinterpreter/openinterpreter remote-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/remote-tests .claude/skills/remote-tests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .claude/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-testsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openinterpreter/openinterpreter remote-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/remote-tests .agents/skills/remote-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .agents/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openinterpreter/openinterpreter remote-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/remote-tests .cursor/skills/remote-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .cursor/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openinterpreter/openinterpreter.git --path .codex/skills/remote-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openinterpreter/openinterpreter remote-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/remote-tests .gemini/skills/remote-tests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .gemini/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openinterpreter/openinterpreter remote-testsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/remote-tests .github/skills/remote-tests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .github/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openinterpreter/openinterpreter --skill remote-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openinterpreter/openinterpreter remote-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/remote-tests .opencode/skills/remote-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "remote-tests" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/remote-tests into .opencode/skills/remote-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-tests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
remote-tests- GitHub stars
- 69k
- Used in
- 2 other repos
- Token cost
- ~842 tokens
- SKILL.md length
- 369 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.
- Works in 2 steps: Docker (Linux exec-server) → Wine (Windows exec-server)
- Running core or app-server integration tests against a Docker remote executor
- SKILL.md covers Test Fixtures, Test Skips, Docker and Wine, plus 1 more section
- Calls bash, just and bazel
What it does
Remote executor tests exercise the split between the app-server and the exec-server so that agent features behave the same locally and remotely. They currently need an x86_64 Linux host and come in two flavors: a Docker container running a Linux exec-server, and a Windows exec-server run under Wine, which only works in Bazel because of the cross-platform build.
Individual tests opt in with helpers such as `TestCodexBuilder::build_with_auto_env()` for core integration tests and `TestAppServer::new_with_auto_env()` for app-server tests. A test that cannot pass in one configuration can be skipped there, with a reason, using one of the skip macros such as `skip_if_wine_exec` or `skip_if_remote`, chosen by what makes it fail. The Docker environment is built by `scripts/test-remote-env.sh`, which also provides a cleanup function to call after testing.
When your agent uses it
- Running core or app-server integration tests against a Docker remote executor
- Making a new integration test work in local and remote execution
- Skipping a test that fails only under Wine or on a Windows host
- Cleaning up the remote test environment after a run
Example prompts
- “Run the core integration tests against the Docker remote executor and report failures.”
- “Make this new app-server test opt in to the remote environment.”
- “This test fails only under Wine. Add the right skip with a reason.”
Requirements
- An x86_64 Linux host
- Docker for the Linux executor, or Bazel for the Wine runs
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Docker (Linux exec-server)
- Wine (Windows exec-server)
What it can do on your machine
Read from SKILL.md and the folder at commit cc054cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bashjustbazelssh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Remote Executor Integration Tests loads about 842 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 369 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openinterpreter/openinterpreter at commit cc054cf, republished under its Apache-2.0 licence (© openinterpreter). 369 words, ~842 tokens.
Download SKILL.mdSave it as
.claude/skills/remote-tests/SKILL.md (or your agent's skills folder).- name
- remote-tests
- description
- Testing against remote executors in integration tests.
Remote executor tests exercise the app-server/exec-server split to ensure that agent features work in both local and remote execution environments.
Remote executor tests currently require an x86_64 Linux host machine. There are two flavors:
- Docker (Linux exec-server)
- Wine (Windows exec-server)
Test Fixtures
Individual test cases must opt-in to being run against a remote executor.
codex_core
Use TestCodexBuilder::build_with_auto_env() to opt-in to remote execution in core integration
tests unless the test needs more precise control over its executor.
app-server
Start the server with TestAppServer::new_with_auto_env() unless the test defines its own
$CODEX_HOME/environments.toml or will define custom environments at runtime.
Start threads with TestAppServer::send_thread_start_request_with_auto_env() if you've created the
server with the auto_env approach. Omit ThreadStartParams.environments (leave it as None) when
doing so.
Test Skips
If a test doesn't pass in a particular remote executor configuration you can skip it in just that configuration. Include a string reason for future readers when the selected skip macro supports one.
Choose the skip macro by what causes the test to fail:
skip_if_target_windows!: Windows target behavior.skip_if_wine_exec!: Wine-exec runner constraints.skip_if_host_windows!: Windows host constraints.skip_if_remote!: Local-only test behavior.skip_if_no_remote_env!: Remote-only test behavior.
Prefer defining tests that run in all host/target configurations by default. See the $path-types
skill for the most common changes required to make tests compatible.
Show full SKILL.md (158 more words)Show less
Docker
Docker container is built and initialized via ./scripts/test-remote-env.sh. Sourcing this script
in bash also provides the codex_remote_env_cleanup function to use after testing.
To run core integration tests against a Docker remote executor:
bash -c '
set -euo pipefail
unset CODEX_TEST_REMOTE_EXEC_SERVER_URL
source scripts/test-remote-env.sh
trap codex_remote_env_cleanup EXIT
cd codex-rs
just test -p codex-core --test all
'To run app-server integration tests against a Docker remote executor:
bash -c '
set -euo pipefail
unset CODEX_TEST_REMOTE_EXEC_SERVER_URL
source scripts/test-remote-env.sh
trap codex_remote_env_cleanup EXIT
cd codex-rs
just test -p codex-app-server --test all
'Wine
These tests build an exec-server for Windows and run it under Wine, with the app-server staying on the Linux host. The cross-platform build dependency means they only run in Bazel.
For core integration tests:
bazel test //codex-rs/core:core-all-wine-exec-testFor app-server integration tests:
bazel test //codex-rs/app-server:app-server-all-wine-exec-testDevboxes
You can use a devbox to run these tests if you are running on a macOS machine.
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.
© openinterpreter, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/remote-tests of openinterpreter/openinterpreter.
Open the folder on GitHubat commit cc054cf
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in openinterpreter/openinterpreter, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Remote Executor Integration Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Remote Executor Integration Tests this skillopeninterpreter/openinterpreter | 69k | 2 repos | ~842 | Automated safety check: Pass | Apache-2.0 | |
| MongoDB Source Connector E2E Harnessairbytehq/airbyte | 22k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Integration Tests for pRESTprest/prest | 4.6k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Go Redis Client Test Runnerredis/go-redis | 22k | — | ~786 | Automated safety check: Pass | BSD-2-Clause | |
| Test Weave Router with Codexweave-os/router | 5.6k | — | ~4.7k | Automated safety check: Notes | Apache-2.0 | |
| Airbyte Postgres Source E2E Testsairbytehq/airbyte | 22k | — | ~2.5k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Integration Tests for pREST
prest/prest
Guides writing and reviewing pREST Docker-based integration tests so every HTTP request is explained by step comments or table-driven descriptions.
- Official
Go Redis Client Test Runner
redis/go-redis
Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.
Test Weave Router with Codex
weave-os/router
Local test harness for the Weave router: a docker compose stack plus codex exec runs that confirm how Codex requests are routed, translated and marked.
- Official
Airbyte Postgres Source E2E Tests
airbytehq/airbyte
Starts a local PostgreSQL 16 container, loads SQL fixtures and runs the Airbyte spec, check, discover and read commands against a chosen source-postgres image.
Snapbox Testing
moonbitlang/moon
Write and maintain Rust CLI/integration tests with snapbox 0.6+ using command assertions, inline snapshots, and minimal wildcard/redaction patterns.
More from openinterpreter/openinterpreter
All 10 skills in this repoPR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
Pull Request Code Review Orchestrator
openinterpreter/openinterpreter
Run a final code review on a pull request
Codex TUI Testing
openinterpreter/openinterpreter
Guide for testing Codex TUI interactively
Related
Categories
Questions about Remote Executor Integration Tests
What does Remote Executor Integration Tests do?
Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them. Remote executor tests exercise the split between the app-server and the exec-server so that agent features behave the same locally and remotely. They currently need an x86_64 Linux host and come in two flavors: a Docker container running a Linux exec-server, and a Windows exec-server run under Wine, which only works in Bazel because of the cross-platform build.
When should I use Remote Executor Integration Tests?
Remote Executor Integration Tests fits situations like: running core or app-server integration tests against a Docker remote executor; making a new integration test work in local and remote execution; skipping a test that fails only under Wine or on a Windows host; cleaning up the remote test environment after a run.
How do I install Remote Executor Integration Tests in Claude Code?
Run `npx skills add openinterpreter/openinterpreter --skill remote-tests -a claude-code`. Or copy the skill folder (.codex/skills/remote-tests in openinterpreter/openinterpreter) into .claude/skills/remote-tests in your project. Claude Code loads it when a task matches its description.
How do I install Remote Executor Integration Tests in Codex?
Run `npx skills add openinterpreter/openinterpreter --skill remote-tests -a codex`. Or copy the skill folder (.codex/skills/remote-tests in openinterpreter/openinterpreter) into .agents/skills/remote-tests in your project. Codex loads it when a task matches its description.
Can I use Remote Executor Integration Tests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openinterpreter/openinterpreter --skill remote-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remote-tests, .gemini/skills/remote-tests, .github/skills/remote-tests and .opencode/skills/remote-tests in your project.
What does Remote Executor Integration Tests need to run?
Going by SKILL.md and its folder, Remote Executor Integration Tests needs the command-line tools its instructions call (bash, just, bazel and ssh). Our summary lists: An x86_64 Linux host; Docker for the Linux executor, or Bazel for the Wine runs.
Does Remote Executor Integration Tests access the network?
SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Remote Executor Integration Tests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Remote Executor Integration Tests use?
Remote Executor Integration Tests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Remote Executor Integration Tests use?
About 842 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Remote Executor Integration Tests?
Skills that share tags, products or a category with Remote Executor Integration Tests: MongoDB Source Connector E2E Harness (airbytehq/airbyte, 22k stars), Integration Tests for pREST (prest/prest, 4.6k stars), Go Redis Client Test Runner (redis/go-redis, 22k stars) and Test Weave Router with Codex (weave-os/router, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Remote Executor Integration Tests?
openinterpreter (a GitHub organization) maintains it in openinterpreter/openinterpreter, which has 68,517 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: openinterpreter/openinterpreter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.