Understand the project
Practical overview
When it fits
Use Riffpad when an AI coding CLI is running on a computer and its operator needs phone-based visibility or explicit remote interaction. The documented setup covers starting Codex through Riffpad and attaching a Claude session started independently.
Who it is for
- Developers using Claude Code, Codex or other AI coding CLIs
- Teams or individuals who need to monitor long-running coding sessions away from a desk
- Builders interested in a Go-based, open-source control layer for coding-agent workflows
Documented uses
- Monitor coding-agent output from a phone
- Send instructions to a running terminal session
- Respond to permission prompts remotely
- Connect a computer-hosted coding session with a mobile client
Before you choose
Requirements & limits
The documented quickstart uses GitHub sign-in on the computer and the same GitHub account in the Riffpad web app. The repository is public and identifies Apache-2.0 licensing for the main project; the relay is separately described as Business Source License 1.1.
- The computer daemon, phone client, adapters and relay each have distinct roles in the workflow.
- The phone pairing flow requires a displayed six-character code or QR code and the same GitHub account on both devices.
- The documented security model keeps keys on the daemon and phone and uses encrypted relay traffic.
- The relay has a separate Business Source License 1.1 from the Apache-2.0 licensing stated for the main project components.
- The quickstart documents Codex startup and Claude attachment, while broader CLI support is described through the adapter architecture.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 3 October 2026
- Original website title
- riffpad/riffpad · Official homepage title · retained in its source language