[FEATURE] Expose /ingress remote session features

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I'd like to implement cross device session management features (particularly for resiliency for Claude Code executed by @anthropic-ai/claude-agent-sdk).

Today, I would have to replicate the CONFIG_DIR path (sync and/or use NFS).
Today, I can sort of use /ingress with localhost:3000/ingress endpoints but seems to only work with --print only.
Ideally, I could use remoteIngress features more completely to manage sessions on my own server implementation.

Proposed Solution

I'd like to be able to run claude --remote-session or something similar, for which the claude code instance does not use local file systems for sessions

Alternative Solutions

I inspected the prettified/approximate de-transpiled code and found the /ingress server option. It seems it only works with -p. I couldn't find any config or arg-driven features to use remote session entirely.

Alternative - syncing file systems, using a shared file system.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

1. I use claude agent sdk on a remote, ephemeral compute environment
2. Claude agent SDK does some work using the local claude install
3. For some number of reasons, the agent (and therefore claude code) must come up on a new host
4. This won't work (natively), because: 1. would have to use a shared file system (not all compute environments have clean ways to mount NFS), 2. Would have to sync from some storage back to local file system (which sounds awful)

Additional Context

TL;DR:

Claude Code has a fairly simple JSONL format for sessions. Make it easy to let me put those in my own database over a REST API instead of the local filesystem.