fragpipe

Bare-metal multiplayer and Android device test orchestration.

Fragpipe owns local, bare-metal, SSH, and Android-device smoke testing for projects that can expose deterministic command-line launch modes. It does not replace cluster harnesses such as steampipe; those remain better suited for VM, Steam, and tournament orchestration.

WebRTC 1v1

From a Chessbender checkout with fragpipe.toml:

fragpipe webrtc-1v1 --max-runs 1

The flow starts a local listening peer, waits for WEBRTC_JOIN_ADDR=..., rewrites wildcard or loopback listen addresses to a reachable local IP, then starts the remote joining peer over SSH.

Android 1v1

android-1v1 starts a desktop listening peer and launches an Android joining peer from a configured APK:

fragpipe android-1v1 --config examples/chessbender.toml --max-runs 1

The Android config controls whether fragpipe boots an emulator or uses a physical device selected by adb_serial. The APK build command is project specific; fragpipe only runs it, installs the APK, pushes the rendezvous file, captures logcat, and records per-run artifacts.

Android UI

android-ui launches the configured full app, waits briefly for startup, asserts that the Android display is landscape, captures a screenshot, and stores logcat plus a JSON report:

fragpipe android-ui --config examples/chessbender.toml --max-runs 1

Use android-doctor to validate SDK, adb, APK, target, package, and activity configuration before running a loop:

fragpipe android-doctor --config examples/chessbender.toml

MCP and Codex Plugin

Fragpipe also ships a fragpipe-mcp binary plus Codex plugin metadata. The MCP server exposes the same fix-loop surface for native WebRTC, Android WebRTC, Android UI, Android doctor, and cross-platform matrix runs.

Run the packaged MCP server with:

nix run git+ssh://git@codeberg.org/caniko/fragpipe.git#fragpipe-mcp

The plugin manifest lives at .codex-plugin/plugin.json, the MCP server config lives at .mcp.json, and fix-loop skills live under skills/.