Requirements and compatibility
Agentknock needs a supported phone, the CLI on the computer running your commands, and a connection from both devices to the relay. Follow Install the mobile app and Install the CLI for setup.
The Android app requires Android 8.0 or later. Set up a secure Android screen lock for device authentication and protected actions in the app.
The iOS app is not yet available.
Computer
Section titled “Computer”The CLI has prebuilt releases for:
| Platform | Requirements for running commands |
|---|---|
| x86-64 Linux | Linux 5.8 or later |
| ARM64 Linux | Linux 5.8 or later |
| Apple Silicon macOS | macOS 15 or later |
WSL2 uses the Linux release for its architecture. Native Windows and Intel Macs are not supported.
Linux releases are statically linked and do not require a particular system C library. If you run the CLI in a container, its host kernel must meet the Linux requirement.
Installing through npm requires Node.js ^22.15.0 or >=24.0.0. Building from source requires Rust 1.89 or later. Neither runtime is needed to use a prebuilt CLI executable directly.
Agent skill and plugins
Section titled “Agent skill and plugins”The agent skill gives any LLM instructions for setup and CLI use. The repository also provides optional plugin metadata and marketplaces for OpenAI and Anthropic tools.
To run commands, the agent needs the CLI installed in its execution environment and paired with your phone. The computer and network requirements on this page apply there too. In hosted environments, the CLI installation and pairing data need to persist for reuse across sessions; the skill guides the agent through checking the available storage and explaining any limitations.
Network access
Section titled “Network access”Both devices need outbound access to relay.agentknock.dev over TLS on port 443. The CLI uses a secure WebSocket connection; a firewall or proxy must allow that connection.
The current connected workflow depends on this hosted relay, including when you use manual approval, saved approval modes or temporary access. The app and CLI’s open-source licences do not include continued hosting. If relay access ends, pairing, credential requests and signing through the CLI cannot proceed through that relay. Free hosted access is subject to the service terms.
The CLI supports HTTP and HTTPS proxies using HTTP CONNECT. SOCKS proxies are not supported.
The phone must be online to list secrets, deliver values, and handle SSH authentication or Git signing, including uses approved automatically. A request can wait while the phone is offline. Notification permission controls alerts; it does not replace the network connection or determine whether requests can be reviewed in the app.
Tools and credentials
Section titled “Tools and credentials”| Use | Compatibility |
|---|---|
| Environment secrets | Tools that read credentials from environment variables, or a selected value from standard input. |
| SSH authentication | Tools that use an SSH agent. Agentknock offers Ed25519 and RSA keys; RSA requires SHA-256 or SHA-512 signatures. |
| Git commit and tag signing | Git configured for SSH signatures. Selecting an SSH secret does not itself enable signing in Git. |
Agentknock starts the executable you specify directly. For shell features such as pipelines, invoke a shell explicitly. See Run a command for variable delivery, SSH agent selection, and Git signing configuration.