Remote coding

Webbee Code works a task to completion on its own, which means you don't have to sit and watch it. Remote coding lets you walk away from the terminal and stay in the loop from somewhere else — send a new instruction, approve or decline a change, or just check in — from Telegram or the panel, while the terminal keeps right on working.

It's the same one session, the same Webbee. You're not starting a second conversation somewhere else — you're reaching into the run that's already going.

How it works

• The terminal keeps executing. Turning remote on doesn't hand the task off or pause it. Your terminal stays in charge and keeps working; the other surface is just another way in.
• Updates come to you. With remote on, Webbee sends you the moments that matter — the finished reply, its to-do progress, when it pauses or finishes, and any point where it needs your approval — without flooding you with every keystroke.
• You can steer — or stop. Reply with a new instruction and it folds into the running task. Reply to an approval prompt to let a change through or hold it back. Tell it to stop and the run cancels, just like Esc in the terminal. Or just chat.
• It's all one conversation. An instruction you send from Telegram or the panel shows up right in the terminal too, tagged with where it came from — and the terminal replays the whole conversation when you come back to it.

Remote coding is off until you turn it on, and it only ever touches your own session.

Turn it on in the terminal

In your Webbee Code dock, use /notify to choose where a running session reaches you:

To steer from Telegram, you'll also need Telegram linked to your account — see Connect Telegram. It takes about a minute.

Control it from Telegram

Once a session is mirrored to Telegram, you drive it right from the chat:

• Send an instruction. Tell Webbee what you want in your own words — "make the tests pass first", "use the staging config" — and it folds it into the task the terminal is already running. No need to restate everything, just steer.
• It's still the same Webbee. Ask about your mail, your notes, anything else mid-run and it simply answers — a question doesn't derail the coding task, and steering doesn't take over your chat. Webbee tells the difference from what you say, not from a mode you have to switch.
• Approve or decline. When Webbee needs your OK for a change, it asks in the chat. Reply to approve it or hold it back. Your reply is read exactly the way it would be in the panel — nothing is auto-approved on your behalf.
• Stop the run. /stop cancels what the terminal is working on right now — the same as pressing Esc in the terminal itself. The session stays open and nothing else is touched, so you can send a new instruction right after. You can also just say it — "stop the terminal task" works too. If nothing is running, Webbee says so instead of pretending.
• /code on · /code off · /code status — arm remote for the session, turn it off again, or check where things stand. /code off always works, and /stop, /code, and turning remote on or off never cost anything.

Control it from the panel

Prefer to stay in the browser? The same session updates can mirror into the panel, so you can follow along and steer from there too. Pick it with /notify panel (or /notify both) in the terminal.

The panel's session card also has a Stop button — one click cancels the run in progress, exactly like Esc in the terminal. It lights up only while something is actually running, and the session itself stays open.

One conversation, everywhere

Steering doesn't fork the conversation — everything flows back into the terminal:

• Remote turns show up live, tagged. Send an instruction from Telegram and the terminal prints that turn as it happens, marked [telegram]. Steer from the panel and it's marked [web-panel]. Turns you type in the terminal itself stay untagged. You always see who said what from where, in order, right in the scrollback.
• Coming back replays the whole story. Close the terminal and open it again later: Webbee Code replays your recent conversation — including the turns you sent from your phone, each with its tag — then draws a — live — line. Everything above the line already happened; everything below is happening now.
• Work still runs in one place. No matter where an instruction comes from, your terminal is where it runs. A turn steered from Telegram doesn't run twice or somewhere else — it folds into the session your terminal is already executing.
• Answering an approval from Telegram frees up the terminal too. If Webbee is waiting on your OK and you approve (or decline) it from Telegram, the terminal's own prompt clears itself and keeps going — you don't need to also answer it in the terminal.

If the session isn't running

You can only steer a session that's live. Send an instruction and it first tries to reach your session directly — if your terminal is open and idle, it picks the instruction up within a few seconds and folds it right in, tagged just like any other remote turn.

If no terminal is open at all, the instruction waits for one — up to an hour — and Webbee tells you:

queued — your open terminal will pick it up within seconds; if no terminal is open, start one

Open (or reopen) your terminal and start or resume Webbee Code there within that window, and your instruction folds in automatically — no need to resend it.

Safety

Remote coding is built so control never leaks:

• Opt-in, off by default. Nothing is mirrored or steerable until you turn it on for a session.
• Scoped to your own session. Every instruction and every update is tied to your live session — there's no way to reach anyone else's, and no one else can reach yours.
• Consent still means consent. Approvals are never granted automatically; your reply is interpreted the same way the panel would, and money stays a browser-only decision.
• You can stop anytime. /stop in Telegram or the panel's Stop button cancels the run in progress; /code off disarms remote; /notify off in the terminal stops mirroring — or just stop the turn in the terminal itself.