The developer CLI for creating and packaging Remote applications.
See ARCHITECTURE.md for package boundaries and CONTRIBUTING.md for local checks and testing expectations.
Install the latest release on Linux or macOS:
curl -fsSL https://raw.githubusercontent.com/futrx-com/remote.futrx-cli/main/install.sh | shThe installer supports AMD64 and ARM64, verifies the release checksum, and
places remote in ~/.local/bin by default. Install a specific release or
choose another directory with environment variables on the sh command:
curl -fsSL https://raw.githubusercontent.com/futrx-com/remote.futrx-cli/main/install.sh \
| REMOTE_VERSION=v0.1.0 REMOTE_INSTALL_DIR="$HOME/bin" shOn Windows, run this in PowerShell:
irm https://raw.githubusercontent.com/futrx-com/remote.futrx-cli/main/install.ps1 | iexThe Windows installer supports AMD64 and ARM64, verifies the release checksum,
installs remote.exe under %LOCALAPPDATA%\Programs\Remote by default, and
adds that directory to the user PATH. REMOTE_VERSION and
REMOTE_INSTALL_DIR provide the same overrides as on Linux and macOS.
Platform detection, download, and checksum verification happen once when the installer runs. The installed CLI does not contact GitHub or repeat installation checks when you run a command.
go install github.com/futrx-com/remote.futrx-cli/cmd/remote@latestDuring local development:
go build -o ./bin/remote ./cmd/remoteremote create app my-app
cd my-app
remote validate
remote buildcreate produces a complete composable application with ui/, backend/,
infra/, skills/, application.json, documentation, and an MIT license.
Delete capabilities the application does not need and update the manifest.
build validates the package and writes <id>-<version>.zip beside the app.
The ZIP is reproducible. Infrastructure support files are turned into
infra/payload.tar.gz in memory, so an app does not need to ship or run a
package.sh script. Legacy infra/package.sh and generated payloads are
excluded from the package automatically.
remote create app <name> [--dir PATH]
remote app create <name> [--dir PATH]
remote validate [PATH]
remote build [PATH] [-o FILE]
remote package [PATH] [-o FILE] # alias for build
remote version