Claude Code adds web-mobile session handoff with claude --teleport

• Anthropic refreshed Claude Code on the web and mobile with a new sessions sidebar, drag-and-drop layout, and a routines view, according to ClaudeDevs' refresh thread and ClaudeDevs' new look post.
• The most useful ship is claude --teleport, which lets you start on web or mobile and continue in the terminal with session history and branch state intact, per ClaudeDevs' teleport post.
• Anthropic also says it rebuilt key parts of the web app for faster responses and better reliability, as ClaudeDevs' speed update puts it.
• Routines are getting more concrete fast: noahzweben's trigger post shows GitHub issue triggers for auto-triage, while noahzweben's one-time scheduling demo adds /schedule for one-off runs.
• Under the hood, Anthropic is also shipping more durable agent plumbing, with noahzweben's session store announcement adding S3, Redis, and Postgres adapter shapes for resumable sessions across hosts.

You can open Claude Code on the web, skim the one-off scheduling docs, and read the session storage docs. The interesting part is how cleanly these pieces line up: a prettier web shell, a handoff command into the CLI, background routines that keep running while your laptop is closed, and shared session storage for agents that may not stay on one machine.

Anthropic's public thread is light on copy and heavy on product direction. The web and mobile surfaces now mirror the desktop redesign, which makes Claude Code feel less like a sidecar and more like the main front door.

The visible changes it called out are short and concrete:

• sessions sidebar
• drag-and-drop layout
• refreshed routines view
• live availability on web and mobile

Those details come straight from ClaudeDevs' new look post and ClaudeDevs' live now post. For creative teams juggling prompts, branches, and half-finished tasks across devices, the sessions sidebar is probably the part that lands first because it turns the web app into a session manager, not just a chat box.

The handoff feature is the real story. Anthropic says you can begin a session on the web or mobile, then run claude --teleport in a terminal and pick up with full history and the correct branch already loaded.

That is a specific promise, not vague “cross-platform continuity.” The session moves from browser to terminal without dropping the conversational context, and the branch state matters because it turns teleport into a coding workflow feature instead of a UI sync trick.

The product pitch fits the way people actually use agents now: sketch on the phone, inspect on the web, finish in a repo. aakashgupta's routines example is about background work rather than teleport, but his screenshot spells out the same system shape, agent, environment, and session, and the session box explicitly says it persists through disconnections and is checkpointed every step.

Routines are the other half of this refresh. Anthropic already shipped them on April 14, and the new web layout gives them a more prominent home. aakashgupta's morning briefing workflow shows why they are different from foreground copilots: the run happens while the laptop is closed, then drops a summary into Slack before the day starts.

The recent routine mechanics now visible in the evidence are:

• GitHub-triggered runs for issue creation, which noahzweben's trigger post frames as an auto-triage setup
• one-time scheduling from the CLI or routines UI with /schedule, shown in noahzweben's scheduling demo
• normal rate-limit accounting for one-off tasks, clarified by noahzweben's rate-limit reply

One-time task scheduling in the Claude Code UI

This makes the refreshed routines view more than a navigation tweak. It is becoming the control panel for background agent jobs, recurring or one-shot, with triggers coming from calendars, GitHub events, or plain time.

The quieter infrastructure update came two days earlier in the Agent SDK. Anthropic published example session store adapters for S3, Redis, and Postgres, which means session transcripts can live in your own backend and resume on another host.

Noah Zwebner's thread lists three reasons for that shared store:

1. Multi-host deployments, where serverless functions, CI runners, and autoscaled workers do not share a filesystem.
2. Durability, because local containers disappear on restart or redeploy.
3. Compliance and audit, since teams can keep transcripts under their own retention and access rules.

That infrastructure note helps explain why teleport and web-to-CLI continuity are showing up now. Anthropic is not just polishing surfaces. It is building the session layer that lets a coding agent survive device switches, disconnections, and host changes with less duct tape.