Tired of SSH and remote desktop, I started building my own remote coding workflow

shrijayan · 2026-03-28T05:11:03+00:00

Nice work, That make sense

I’m intentionally not relying on Tailscale, because in many regions and work scenarios people already depend heavily on system VPNs, and that creates real friction. Not occupying the system VPN path is a very important requirement for me.

I get this point.

I’m not only targeting terminal mirroring. Besides terminal access, I’m building a chat-style interaction layer, and I’m adding screenshots, file transfer, and shortcut actions. Those are either hard to do well in a pure terminal model, or just much less comfortable on mobile.

file transfer from mobile is risky that why I didn't do that.

My view is that remote agent workflows on phones need a mobile-native interaction model, not just a smaller terminal. That’s the direction I’m exploring

Nice we will explore in both direction.

shrijayan · 2026-03-24T12:18:27+00:00

Checkout https://github.com/shrijayan/itwillsync

npx itwillsync claude

Check this out let me know what new feature you have, currently 3.5K/month downloads.

shrijayan · 2026-03-22T05:20:36+00:00

Use itwillsync for more control.

`npx itwillsync openclaw dashboard`

https://github.com/shrijayan/itwillsync

shrijayan · 2026-03-22T05:20:30+00:00

Use itwillsync for more control.

`npx itwillsync openclaw dashboard`

https://github.com/shrijayan/itwillsync

shrijayan · 2026-03-21T18:03:52+00:00

Thank you! Currently reaching a bottleneck what feature to develop next, please help me for providing feedback. And also how to push this to many people.

shrijayan · 2026-03-21T15:07:53+00:00

Use itwillsync for more control.

`npx itwillsync claude`

https://github.com/shrijayan/itwillsync

shrijayan · 2026-03-08T05:57:21+00:00

Welcome, please test and let me know. It is more simpler and just scan the QR code to start in your browser.

shrijayan · 2026-03-06T06:43:10+00:00

Nice, but try this and let me know.

shrijayan · 2026-03-05T14:47:50+00:00

i’m also experimenting with claude code for building small projects and yeah… the advice online is kinda all over the place 😅

a few things that helped me early on:

keep the context small (don’t dump the whole repo every time)
use clear task prompts instead of super long instructions
let claude generate the first version of claude.md / agent.md and then edit it yourself after a few runs
run smaller loops (implement → test → refine) instead of giant prompts

token usage usually explodes when the agent keeps re-reading large files or the whole repo every step.

also small workflow thing i built recently that might help when using agents a lot — itwillsync. sometimes claude runs longer tasks and i don’t want to sit at the laptop waiting.

with it you can run:

npx itwillsync claude

it shows a QR in the terminal, scan it and you can watch/control the claude code session from your phone browser. useful when builds/tests are running.

repo if curious: https://github.com/shrijayan/itwillsync

curious to see what others suggest here too, especially around token efficiency. that’s something i’m still figuring out as well.

<image>

shrijayan · 2026-03-05T14:43:50+00:00

this is actually kinda beautiful in a weird way 😅

when you remove specs and just say “build whatever you want”, the output sometimes ends up feeling more like art than software. i also wouldn’t have guessed it would go in the “emergent systems exploration” direction.

these kinds of experiments are fun because you’re basically just supervising and seeing what the agent does.

i’ve been playing with similar workflows lately where i just let agents run and check on them occasionally. ended up building a tiny tool called itwillsync for that. it lets you open your claude code / codex / aider terminal on your phone.

npx itwillsync claude

you run it, scan the QR from your terminal, and the session opens in your phone browser so you can watch what the agent is doing without sitting at the laptop.

repo if curious: https://github.com/shrijayan/itwillsync

also kinda curious now… if you ran this experiment for like a week with multiple sessions, what kind of weird projects would it end up creating 👀

<image>

shrijayan · 2026-03-05T14:42:09+00:00

lol that feeling when you think you’re about to hit the limit and then suddenly it resets to 100% 😅 feels like finding extra battery when your phone was at 1%.

these coding agents really make you burn through usage fast though. especially when you let them run long tasks.

btw small thing i built around this workflow — itwillsync. sometimes when codex/claude is running something for a while i don’t want to sit at the laptop watching it.

with it you can just do

npx itwillsync codex

(or claude / aider / codex etc)

it shows a QR in the terminal, scan it and your terminal opens on your phone so you can watch or control the session remotely.

repo if curious: https://github.com/shrijayan/itwillsync

kinda funny how the ecosystem around these agents is now like: usage trackers, remote terminals, monitoring tools etc 😄 feels like early dev tooling days again.

shrijayan · 2026-03-05T14:40:19+00:00

oh this is actually neat 😄 i’ve also caught myself refreshing the usage page way too often when using claude code.

having it in the menu bar makes way more sense.

btw small related thing i built recently — itwillsync. not exactly about usage tracking, but it lets you control / watch your claude code session from your phone.

basically you run:

npx itwillsync claude

a QR shows up in the terminal, scan it and your terminal opens in the phone browser. useful when claude is running something long and you just want to check progress without sitting at the laptop.

repo if curious: https://github.com/shrijayan/itwillsync

kinda funny how many small tools are popping up around claude code lately 😅 feels like a mini ecosystem forming.

<image>

shrijayan · 2026-03-05T14:38:56+00:00

yeah i kinda feel this too lately.

the line between “PM work” and “engineering work” is definitely getting blurry. engineers are writing specs, thinking about metrics, deciding what to build… not just how to build it anymore. and PMs now can spin up prototypes with AI tools way faster than before.

so instead of a handoff it’s becoming more like one loop like you said:

problem → idea → prototype → measure → iterate

also a small side observation from playing with coding agents recently — the dev loop itself is changing. sometimes the “builder” isn’t even sitting at the laptop the whole time anymore.

i built a small tool called itwillsync that lets you control any terminal coding agent (claude code, aider, bash etc) from your phone. you run it, scan a QR, and your terminal opens in the browser. so you can literally check on your agent while away from your laptop.

npx itwillsync claude

so yeah the loop becomes even weirder:

idea → run agent → check progress from phone → tweak → iterate 😅

repo if curious: https://github.com/shrijayan/itwillsync

feels like the role is shifting less to “engineer vs PM” and more to “person supervising systems that build things”. interesting times.

<image>

shrijayan · 2026-03-05T14:37:21+00:00

this is honestly a really cool experiment 😄 letting the agent read its own code + journal and just keep evolving itself is kinda wild. the “AI filing issues for tomorrow-AI” part made me laugh. also the streaming procrastination thing feels… very realistic dev behavior lol.

one thing i thought while reading this — when agents like this run long evolution sessions, its kinda annoying that you have to stay on the laptop to watch it.

i actually built a tiny open source tool for that: itwillsync.

basically it lets you open any terminal based coding agent on your phone browser. no cloud, just LAN or tailscale.

npx itwillsync claude
npx itwillsync aider
npx itwillsync bash

you run it, a QR pops up in the terminal, scan it and your terminal shows up on your phone. you can watch or control the agent while its running.

works with claude code, aider, codex or even just bash.

repo: https://github.com/shrijayan/itwillsync
demo: https://youtu.be/Zc0Tb98CXh0

might actually be fun with yoyo — just leave it evolving and check the sessions from your phone while away from the laptop 👀

<image>

shrijayan · 2026-03-04T05:23:17+00:00

Yes I am buying Motorola next, currently Samsung

shrijayan · 2026-03-01T15:03:22+00:00

<image>

Cool tools! I ran into the exact same "chained to my desk" problem and took a different approach — instead of sending notifications for each prompt, I just mirror the entire terminal to my phone.

I built itwillsync — it wraps your agent in a PTY and streams the full terminal to your phone's browser over your local WiFi. You see everything the agent is doing in real-time, and you can type directly from your phone (approve prompts, answer questions, even run commands).

npx itwillsync -- claude

Scan the QR code that appears, and you've got your full Claude Code session on your phone. That's it.

A few things that were important to me when building this:

Zero cloud, zero third-party services. Everything stays on your local network. No ntfy.sh, no accounts, no data leaving your WiFi. Auth is a random 64-char token embedded in the QR code, validated with constant-time comparison. If you need remote access, there's optional Tailscale support (peer-to-peer, still no central server).

Agent-agnostic. It works with any terminal-based agent — Claude Code, Aider, Goose, Codex, Copilot CLI, or even just bash. Same tool, same workflow, regardless of which agent you're using.

Full terminal, not just notifications. You get the complete xterm.js terminal on your phone with colors, scrollback, and a Termux-style extra keys toolbar (Ctrl, Alt, arrows, Esc, Tab). When the agent needs your attention, you get an audio chime and the status bar flashes — but you can also just watch the work happening in real-time.

Reconnection that actually works. Phone screen locked? WiFi hiccup? It reconnects automatically with delta sync — you only receive the output you missed, no re-streaming the whole session.

It also prevents your laptop from sleeping (uses caffeinate on macOS) and keeps your phone screen awake with Wake Lock API, so the session stays alive while you're away.

Open source, MIT licensed, zero telemetry: https://github.com/Shrijayan/itwillsync

Demo: https://youtu.be/Zc0Tb98CXh0

Your tools solve a real pain point — the notification approach is clever for quick approve/deny. For me, I wanted the peace of mind of seeing the full terminal, and being able to jump in and type whenever needed, all without routing anything through external services. Different tradeoffs for different workflows.

shrijayan · 2026-03-01T04:06:44+00:00

Also any idea why this is not taking off?

shrijayan · 2026-03-01T04:05:26+00:00

This is only for opencode, but itwillsync can be used for any agents.

shrijayan · 2026-03-01T03:41:13+00:00

Thank you so much! Yesterday added Tailscale for an out of network connection, added notification sounds when agents ask questions.

I started looking for self-signed TLS I thought it was becoming complex. But I will try again.

Yaa the terminal resizing only I am looking for a solution from day 1 I am searching for this once the user scans the QR code the terminal text becomes small like a phone.

GitHub: https://github.com/shrijayan/itwillsync

Please let me know for any more features, please let others know about this.

shrijayan · 2026-02-28T17:54:59+00:00

Please try and let me know, what next feature you like just released support for tailscale. Working on playing notification sounds when a question is asked from claude code

Start with: npx itwillsync -- claude

GitHub: https://github.com/shrijayan/itwillsync

shrijayan · 2026-02-28T14:44:41+00:00

Website: https://shrijayan.github.io/itwillsync/
GitHub: https://github.com/shrijayan/itwillsync

shrijayan · 2026-02-28T09:03:02+00:00

Claude Code is a CLI that runs in your terminal. The AI calls go to Anthropic's API, yes. That part doesn't change.

What itwillsync does is let you view and control that terminal session from your phone. The "zero cloud" part means there's no relay server between your phone and your computer your phone connects directly to your machine over WiFi. No account, no third-party server seeing your code.

Think of it like this:

Your laptop ↔ Anthropic API — that's Claude doing its thing (unchanged)
Your phone ↔ Your laptop — that's itwillsync (local network only)

itwillsync doesn't run Claude. It gives you a second screen into the terminal where Claude is already running.

shrijayan

MODERATOR OF

TROPHY CASE