Roadmap

Shipped (through v0.3.15)

✅ patchwire CLI with setup, init, init-remote, sync, ask, apply, chat, doctor, whoami
✅ patchwire-agent HTTP server with /health, /ask, /chat
✅ Bearer-token auth (constant-time); published to npm as @rebink/patchwire
✅ Selective per-file apply
✅ patchwire-agent install/uninstall (macOS launchd; Linux systemd)
✅ Tailscale peer auto-discovery in setup
✅ Multi-developer isolation: per-user bearer tokens, isolated project directories, fair request queue
✅ patchwire-agent user: add / list / disable / enable / rm / rotate
✅ Per-user policy enforcement: project allowlist + rate limit on /ask and /chat
✅ JSONL audit log (every /ask and /chat; stores prompt_sha256, never plaintext)
✅ patchwire-agent log: filtered audit log viewer
✅ patchwire-agent usage: per-user requests / accepted / ask / chat / lines added-removed / duration / tokens + dollar cost (TOK / $EQV)
✅ Streamed /ask (NDJSON live queue visibility while Claude runs)
✅ VS Code extension: opens a Claude Code session on your remote and keeps your laptop in two-way sync (Mutagen); published to the Marketplace + Open VSX
✅ Secret-safe sync (rsync respects .gitignore and sync.exclude)
✅ Reliable 3-way apply: detects local drift since sync and merges instead of failing
✅ Test-before-return: optional PW_VERIFY_CMD runs on the checkout so you review a validated diff
✅ Pre-sync secret scan (sync.secretScan): gitleaks blocks/warns before a tracked-file secret can cross
✅ Cost & token visibility: usage shows TOK and $EQV; provider-reported cost where available, operator price-table fallback (~estimated). See Configuration → Cost tracking.
✅ Local file attachments: patchwire push and a VS Code 📎 Attach button get local files (incl. screenshots/images for vision) to the remote claude, via a gitignored .patchwire-inbox/. The panel lists staged attachments: open one, delete it (clears the remote copy too), or re-insert its path into the active session. See Configuration → Attachments.
✅ Sync profiles by project type: setup auto-detects Flutter / Node frontend / Node backend / Python / Common and seeds sync.exclude; the extension’s two-way sync now honors it, so build caches and dependencies stay off the wire. See Configuration.
✅ Terminal-based key install (no sshpass): the setup wizard installs your SSH key via an interactive ssh-copy-id plus a Verify step. No GPL binary, no brew tap; macOS and Linux out of the box.
✅ Reliable onboarding: installable from npm (@rebink/patchwire), the extension activates on fresh machines (even with no folder open at launch), and the activity bar shows the Patchwire mark.
✅ Automatic agent provisioning: after key install + push, the wizard installs and starts the remote patchwire-agent over SSH and sets the token on both ends, so the CLI ask flow and doctor work with no manual remote steps. Non-blocking if it can’t finish.
🧪 Default-deny egress (macOS, experimental, off by default): the seatbelt deny works, but the Anthropic allowlist is brittle against the API’s CDN IPs, so it’s not production-usable yet and not recommended for trusted-network setups. See Security → Default-deny egress.
✅ GitHub repo: rebink/remote_claude

Near-term

🔜 Per-request model selection + an “allowed models” policy
🔜 Dollar-cost on the chat path (chat already records real tokens; cost attribution is next)
🔜 Egress: timer-based IP re-resolution + a Linux (netns) backend

Exploring / not committed

💭 Build-cache sharing across developers on the same agent (Dart/Flutter pub cache, node_modules snapshots)
💭 Hosted agent option: run the agent on a cloud VM without needing a dedicated machine

Decided against

❌ Android device bridge. Edits apply to the local working tree, so developers run flutter run locally. A remote device bridge is off-model and adds complexity with no benefit.
❌ iOS remote debugging. Same reasoning as Android.
❌ Bidirectional file sync. The product premise is one-way. We’re not adding the other direction.
❌ Real-time co-editing. Patchwire is request/response. For inline completions, run Claude Code locally.
❌ Becoming a full remote-IDE. Editor stays local. Always.

Want to influence the roadmap?

Open an issue at the GitHub repo and describe the workflow pain you’re trying to solve. We weight requests by how concretely they’re tied to a real workflow, not by upvote count.