AI-forward session operations

The session manager for Claude, Codex, SSH, terminal, and file work.

Jump OS turns operational work into one continuous session system. Start with conversation, attach shell and files when needed, switch devices without losing context, and keep every surface aligned.

ClaudeCodexSSHTerminalFilesHandoff
Session model
Conversation-first workspace
Continuity
Mac, web, and iPhone handoff
Controls
Vault, approvals, attached tools
Jump OS desktop workspace with session hub, active shell, and attached tools
One operating model

Built for agentic coding and real operator work, not just terminal tabs.

The product direction is simple: make AI sessions the primary object, keep terminal and SSH power close at hand, and let users of any skill level continue work across devices without reconstructing context.

Session Canvas

Conversation-first workspace

Operators start from a session conversation, not a disconnected terminal tab. Claude and Codex sessions are managed like threads with attached runtime tools.

Cross-device Continuity

One session system across every surface

Mac, iPhone, and web all point at the same session graph. Resume on another device, continue the conversation, and keep shell and file context attached.

Attached Tools

Tools stay docked to the session

Shells, SSH attachments, file IDE, previews, transfers, and approvals stay inside the selected session instead of scattering across separate utilities.

Operator Workflow

Operational control without the clutter

Review approvals, switch between live sessions, inspect handoff state, and move from AI conversation to shell execution without losing the thread.

Run Claude and Codex like real working sessions

Open multiple AI sessions, pin them, rename them, resume them, and move between them the same way you manage live operational work.

Attach SSH and shell work without leaving the thread

Jump from conversation into remote execution, local terminal, files, previews, or transfers from the same workspace instead of opening unrelated screens.

Keep session continuity across devices

Detach on one surface, reattach on another, load a conversation handoff, and keep working without reconstructing context from memory or copy-paste fragments.

Operate securely by default

Vault, device authorization, approvals, and session controls stay part of the same product architecture instead of being bolted-on admin screens.

How it works

Start with the session. Everything else hangs off it.

01

Start a session like a conversation

Choose Claude, Codex, SSH, or terminal from one launch flow. The session becomes the object you manage from that point forward.

02

Attach the tools you need

Open shell, files, previews, transfers, or sharing as attached capabilities of that session instead of separate destinations.

03

Resume anywhere with continuity intact

Switch devices, reopen the session, restore the conversation handoff, and continue the same operational thread.

Desktop workspace

A single canvas for session management

Mac app
Jump OS desktop session manager
Mobile continuation

Session handoff that actually works from your phone

Keep an eye on live work, reopen the right session, and continue on mobile without losing the context built on desktop or web.

Jump OS on iPhone
Built for operational excellence
  • See multiple active Claude and Codex sessions without losing track of runtime state.
  • Switch from conversation to SSH, terminal, files, or transfer controls from the same workspace.
  • Resume and hand off work cleanly across macOS, web, and iPhone.
Private beta

Build your entire operator workflow on one session platform.

Jump OS is being shaped around AI-forward session management for real engineering work. Join the beta and help define the next operating surface for Claude, Codex, SSH, and terminal workflows.