claude code from your phone: three ways in

which computer is doing the work?

anthropic options below are documented as of 12 november 2026. dusk phone access depends on the computer you pair it with.

remote control keeps your existing machine involved

as of 12 november 2026, anthropic's remote control connects a claude code session on your own machine to claude.ai/code or the claude mobile app. the local process still does the work. the computer must stay on, and the claude process must remain running. if sleep or a lost network interrupts it, claude code reconnects when the machine comes back.¹

that fits a session tied to the computer at your desk. it does not turn the phone into a replacement host. before leaving, think about power, connectivity and whether the machine will stay available long enough to finish.

anthropic lists remote control on pro, max, ultra, team and enterprise. api-key authentication is not supported for it; team and enterprise need an owner to enable the feature.¹

cloud sessions are anthropic's separate option

as of 12 november 2026, anthropic documents cloud sessions that keep running when you close the laptop. you can start from the Code tab in its mobile app, claude.ai/code, the desktop app or claude --cloud. usage counts toward plan limits.²

the page lists pro, max, ultra and team, plus eligible enterprise seats. if the goal is a coding session you can check while travelling, read this option before setting up another computer. for repeating work rather than one session, the claude scheduled tasks guide explains its cloud scheduler. do not assume a session and a schedule are the same thing.

dusk gives you a bot to text

in dusk, a bot is a named teammate with a job, its own chats and memory, and an ai you pick. choosing claude code as the engine means dusk runs that official command-line app on the machine where the bot lives, with you completing sign-in yourself. texting the bot lets you give work and follow up through that chat.⁴⁶

this fits ongoing work with a named bot, rather than a window into a particular terminal session. if you want one bot for planning and another for reviewing documents, they can have different jobs and different ais. each keeps its own memory. switching an ai does not discard the bot's chats or files.⁴

using a phone doesn't change anthropic's terms. its legal page (checked 12 november 2026) says nothing in it prevents 'an end user from signing in to the unmodified Claude Code binary with their own Claude subscription', and it sets conditions for platforms that host it. check the current page yourself.⁷

pair once, then test away from your desk

open dusk's phone pairing and scan the code. alternatives are a six-digit code, a nearby list on wi-fi or tailscale. pairing needs no account. iphone and android are supported, but the store apps are still on their way. for now, pairing opens dusk in your phone's browser and you add it to the home screen. that browser version sends no notifications.³

send a simple question while the host is awake. then check which host you paired to. if it is your laptop, Settings, Remote access, Keep this computer awake helps keep it reachable. if you need it after shutting the laptop, pair with dusk cloud instead.³

keeping claude code available overnight covers the hosting tradeoffs. for people looking specifically for other chat channels, the telegram, discord and slack guide is a separate question from phone pairing.

use the small screen for decisions

give a narrow instruction you can review on the phone: 'read the proposal i attached and tell me which two assumptions need checking. leave the file alone.' that gives you a useful checkpoint without asking you to inspect a whole document while walking.

dusk approval cards can reach the phone. connected apps can be limited per bot, including read-only access. for changes inside an app, write 'ask me before you change anything' if you want supervision. sending has a separate approval setting. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so set Sending on your behalf to Ask every time for full-access bots.⁸ do not treat phone access as a reason to grant broader permissions.⁸