Yaver
Yaver is a local-first developer toolkit for driving coding agents, previews, feedback, and deploy loops from your phone.
Your code stays on your machine. The mobile app is the remote control; the yaver agent runs on your Mac, Linux box, WSL machine, Pi, or VPS; the SDK captures feedback from your own dev builds.
What Works Today
- Run Claude Code, Codex, OpenCode, Aider, Goose, or another terminal agent from the Yaver agent.
- Push React Native / Expo bundles to a paired phone through the native Hermes path.
- Capture dev-build feedback with screenshots, logs, and replay context.
- Stream task, build, and reload progress back to mobile or the web dashboard.
- Keep peer discovery, relay, and vault flows local-first and self-hostable.
- Use SDKs and examples for React Native, Flutter, web, Unity, Go, Python, and JS/TS.
Quick Start
npm install -g yaver-cli
yaver auth
yaver serve
For headless machines:
yaver auth --headless
yaver serve
If an AI coding agent is setting Yaver up for you, read the canonical machine guide first:
curl -s https://yaver.io/llms.txt
Use from Claude Code, Codex, or opencode (MCP)
Yaver ships an MCP server, so a coding agent can drive your machine directly. You do not need a global install first — npx pulls the server on first run. Register it once, then ask the agent to call yaver_lazy_setup; it surfaces the sign-in link for you to tap and pairs your phone from inside the chat.
# Claude Code
claude mcp add --scope user yaver -- npx -y yaver-cli yaver-mcp
# Codex
codex mcp add yaver -- npx -y yaver-cli yaver-mcp
# opencode
npm install -g yaver-cli && yaver mcp setup opencode
Already installed Yaver globally? yaver mcp setup claude-code (or codex / opencode) writes the same entry, and yaver auth auto-registers every installed runner on first sign-in. Yaver is published to the official MCP registry as io.github.kivanccakmak/yaver. Full tool list and HTTP/remote setup: MCP guide.
Core Loop
- Start
yaver serveon your own machine. - Pair the mobile app or web dashboard with that agent.
- Send a task to your coding agent from the phone.
- Watch terminal/build/reload progress live.
- Push the fix to a real device or deploy from your own machine when ready.
Repository Map
| Path | Purpose |
|---|---|
desktop/agent/ | Go agent, CLI surfaces, local API, relay/P2P/runtime integrations |
mobile/ | React Native mobile app and native preview container |
web/ | Next.js marketing site and dashboard |
backend/convex/ | Hosted identity, session, and device-discovery metadata |
relay/ | QUIC relay service |
sdk/ | Public SDKs and feedback clients |
demo/ | Small fixture apps used to test SDK and push flows |
demo-videos/ | Source notes for the landing/demo clips |
docs/ | Architecture notes, setup guides, audits, handoffs, and planning material |
Documentation
Markdown in this repo is context, not source of truth. If a doc and the code disagree, trust the code and fix the doc in the same change.
Development
# Web dashboard / landing
cd web
npm install
npm run dev
# Go agent tests
cd desktop/agent
go test ./...
Run the narrower package tests for the area you change; the full repo spans Go, Node, React Native, Swift, Kotlin, Flutter, Unity, and embedded C work.
License
Core Yaver code is under FSL-1.1-Apache-2.0. SDK packages are Apache-2.0 where marked. See docs/planning/LICENSING.md.