<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Backseat</title>
    <description>The latest articles on DEV Community by Backseat (@backseat).</description>
    <link>https://dev.to/backseat</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4152943%2F8d0cf96f-a70d-45c0-9862-8c07a0106152.png</url>
      <title>DEV Community: Backseat</title>
      <link>https://dev.to/backseat</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/backseat"/>
    <language>en</language>
    <item>
      <title>I code from my phone now — Cline does the typing</title>
      <dc:creator>Backseat</dc:creator>
      <pubDate>Wed, 30 Sep 2026 18:55:06 +0000</pubDate>
      <link>https://dev.to/backseat/i-code-from-my-phone-now-cline-does-the-typing-3kf6</link>
      <guid>https://dev.to/backseat/i-code-from-my-phone-now-cline-does-the-typing-3kf6</guid>
      <description>&lt;p&gt;My coding setup used to have a hard requirement: me, at my desk. Cline is a great driver, but somebody had to sit in the car. Last week I got tired of that and built the thing I actually wanted: a way to backseat-drive my coding agent from my phone.&lt;/p&gt;

&lt;p&gt;Here's the setup. There's a VS Code extension — Backseat — and a private GitHub repo that acts as the task queue. I text my personal AI what I want ("add an AI opponent to the Blokus game, with scoring"), and it writes that up as a task file: tasks/pending/something.json. The extension on my PC polls the repo, picks it up, and runs it in Cline's sidebar. I watch it work in the chat, from wherever I am. When Cline finishes, it writes a done file, the extension files the result, and I get my summary.&lt;/p&gt;

&lt;p&gt;The mental model that makes it click: I'm the backseat driver. I do architecture in plain language — "no, the AI should prefer big pieces, and pass automatically when it has no moves" — and Cline does the typing. A real build becomes a text conversation spread across the day: a message on the train, a message in line for coffee.&lt;/p&gt;

&lt;p&gt;Under the hood it's deliberately boring: the queue is JSON files moving through pending → active → done, Cline is driven through its extension API so everything stays visible in the sidebar, and completion is a file handshake. The interesting work was all in failure handling — retrying provider errors instead of stalling, re-adopting the Cline session after a VS Code restart, cancelling a runaway task from my phone. I know, because every one of those broke live while I was dogfooding it, and each one is now a feature.&lt;/p&gt;

&lt;p&gt;The proof: yesterday I architected a complete Blokus game — board, placement rules, an AI opponent, scoring — without touching a keyboard. Just texts.&lt;/p&gt;

&lt;p&gt;It's open source (MIT) and very much still being tested in production, which is exactly why it works: &lt;a href="https://github.com/darek225/backseat" rel="noopener noreferrer"&gt;https://github.com/darek225/backseat&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;VS Code Marketplace: &lt;a href="https://marketplace.visualstudio.com/items?itemName=darek.backseat" rel="noopener noreferrer"&gt;https://marketplace.visualstudio.com/items?itemName=darek.backseat&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're setting up Muse for the first time to try Backseat, my referral code is 4T6Z5L.&lt;/p&gt;

&lt;p&gt;If you try it, I'd genuinely love to know what breaks. That's been the whole development process so far.&lt;/p&gt;

</description>
      <category>vscode</category>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
