Controllable Remote Coding Sessions: One Level Above the IDE
Sometimes the nicest feature comes out of a moment where, at first, everything looks broken. This story is one of those. It’s about controllable remote coding sessions in boostN.ai — meaning: sending off a coding task, having an agent work on it in the real code, and being able to jump in live at any time if you want. One level above the IDE. And it nearly fell apart over a single vanished line in the terminal.
What we did before
Our Devi Runner in the boostN CLI starts coding agents as remote-controllable sessions. So that you can click into a running session from the web app too, we needed the matching session link. Up to now we read it quite pragmatically straight from the terminal output — a little pattern matching on the session ID, done. We then displayed that link as a clickable button in the web app. It worked reliably, it was simple, and nobody gave any thought to the idea that this one line might one day no longer be there.
Why it suddenly stopped working
But that’s exactly what happened. The current Claude CLI no longer prints that link to the terminal in interactive mode — precisely the mode our runner needs for the automatic start of the task. Neither in plain text nor as a clickable reference. All that remains is a terse “Remote Control active.” The information we needed was simply gone.
We then systematically tried out all four documented modes of the CLI. The result was sobering: no local mode delivers both the link and the automatic start of the task. The only mode that still outputs the link is a server mode — and that one doesn’t accept a locally supplied task. At first glance this looked like a dead end.
What we found out
Then came the moment that turns the story around. The link hadn’t actually disappeared — it had just moved. Instead of sitting in the terminal, it now lives on the provider’s server interface. There’s an endpoint there that lists all running remote sessions of an account, each with ID, title, and status. Authentication runs via the access token already present in the system keychain. And from the session ID the controllable link can be assembled unambiguously. Importantly: this is pure read access, we only fetch a list.
The plan
That gives us a clean path. The runner still starts the session locally with the task, exactly as before — but additionally tags it with a unique process code as its name. After that it queries the list of running sessions, finds its own via exactly that code, builds the controllable link, and sends it to the web app. In terms of scope we’re talking an estimated 120 to 180 lines of code — manageable.
An honest limitation
The endpoint we use is not officially documented; it comes from a research preview and could change at any time. That’s exactly why we deliberately use it read-only — we fetch a list, nothing more. If it disappears, only this convenience falls away, not the whole feature.
Why this is good for users
The actual point isn’t the recovered link, but what it enables. Remote sessions lift you one level above the IDE. Instead of reading along deep in the editor yourself, you send off a task, an agent works in the real code — and only if it stalls or a question comes up do you deliberately jump in. Or not. Anyone working on many projects in parallel quickly notices that the IDE sits one step too deep for this kind of overview.
IDEs are — as nice as they may be — one level too deep in. Especially when you work on many projects, you want to be on a higher level. With the remote link you send off a task, someone works on it, and if you notice it’s not moving forward or a question comes up, you deliberately jump in — or not. That sets it apart from a normal IDE task, where I have all the text in front of me, have to paste the reference in, and then spend a lot of time reading. I hope this web setup stays available for us providers and that others follow suit — because hosting your own language model just to make the chat remote-capable is far too much of a detour.
So the remote link turns a coding task into something you can delegate and take back over when needed. And that’s exactly the difference from the classic reading-along in the editor.
A wish at the end
That leaves a wish for the platform providers: please keep such remote-capable agent interfaces open and stable. Then tool providers like us can build on them, without having to host our own language model just to make a session remote-capable. That would be a disproportionately large effort for something that essentially already exists — you just have to leave it reachable.
Keep reading
- How we hard-wire recurring routines: AI Workflows by Keyword
- Models for automation without a UI: Headless AI Models
Entdecke mehr
Saving Tokens with Claude: 6 Principles That Make Experts Twice as Fast
How I turned my CLAUDE.md from a style guide into a token budget — 6 principles for lower cost, less waiting, and more honest reporting.
GlossarSpeech-to-Text (STT)
Speech-to-Text refers to the automatic conversion of spoken language into text by an AI model. In an AI workflow, STT replaces the keyboard as the input channel — what matters is model size and domain vocabulary.
LexikonAI Coding Tools Compared
Cursor, Windsurf, Claude Code, GitHub Copilot, Continue.dev, Aider compared. With table and decision guide for four typical developer workflows.