Launch
ChatView
Visit
Example Image

ChatView

Vibe code from your phone

Visit

Chat with your Cursor or VS Code from anywhere.

ChatView is a mobile + web companion for Cursor and VS Code. You install the VS Code extension on your laptop, scan a QR code from the ChatView mobile app, and now your phone is a remote for the coding agent running on your machine.

Prompt from your phone. Watch diffs render in real time. Approve or reject each edit. The agent uses whatever model you've already configured in Cursor — bring-your-own-key, no extra inference cost from us.

What it's good for:

  • Triaging bugs from your phone before you sit down
  • Kicking off a long refactor and walking away from the keyboard
  • Reviewing AI-generated edits on the couch
  • Pair-prompting with a teammate (Pro)

Free tier includes daily prompt quota and one paired device. Pro unlocks unlimited prompts, multi-device pairing, and team plans.

Built in public from Cape Town. Open issues, open roadmap, weekly releases.

Example Image
Example Image
Example Image
Example Image

Features

  1. QR pairing between phone/web and your laptop's IDE
  2. Streaming agent responses on mobile
  3. Live diff view with approve / reject per file
  4. Works with Cursor and VS Code
  5. Brings your own model config (Claude, GPT-4/5, Gemini, local)
  6. Multi-device pairing — phone, tablet, second laptop
  7. Team plan with shared sessions
  8. End-to-end encrypted relay (your code never sits on our servers)
  9. Dark mode + light mode, both designed by hand

Use Cases

1. Fix-a-bug-in-the-coffee-queue

  • Who: Indie devs, founders
  • When: You're 10 min from home and Sentry pings a prod error
  • What: Open ChatView mobile → prompt "look at error in app.tsx line 42, propose fix" → review diff on phone → approve → laptop pushes the commit
  • Saves: 30–60 min of "wait til I get home"

2. Triage-from-bed

  • Who: On-call engineers
  • When: Pager at 2 AM, you don't want to boot the laptop
  • What: ChatView prompts the agent to read recent logs, identify the failing service, and either patch or escalate
  • Saves: Time to acknowledge + decision quality (no half-asleep typing)

3. Commute-refactor

  • Who: Anyone with a 30+ min commute
  • When: On the train/bus, laptop closed at home
  • What: Kick off a long refactor ("convert all class components in /src/legacy to hooks"), watch streamed diffs, approve in batches
  • Saves: A whole productive working-block per day

Comments

Social Links
custom-img
Founder at Doculeearn
Makers
custom-img
Founder at Doculeearn

Comments