什么时候可以建议加一个 复用本地的session啊

[xiaobaifly7]

What feature would you like to see?

什么时候可以建议加一个 复用本地的session啊

Additional information

No response

[github-actions]

目前代码里已经有一部分“复用 session”的能力，但我没有在仓库里看到“通用接管一个未由 HAPI 创建的本地已有 session”的入口，所以现在还不能从代码确认这个需求已经完整支持，也无法确认具体上线时间。

如果你说的是“恢复 HAPI 里已经存在、但当前 inactive 的会话”，这个能力看起来是已经有的：Web 端在会话 inactive 时发送消息会自动走 resume；Hub 侧也有对应的 /sessions/:id/resume 流程。如果你说的是“把独立在本地终端里已经跑起来的 session，后续再挂到 HAPI 里继续用”，我目前没有找到通用 attach/import 实现。

Relevant code:

• web/src/router.tsx:245 - inactive 会话发送消息时自动调用 resumeSession
• hub/src/web/routes/sessions.ts:98 - 提供 POST /sessions/:id/resume
• hub/src/sync/syncEngine.ts:367 - 恢复依赖已保存的 metadata.path
• hub/src/sync/syncEngine.ts:375 - 恢复依赖 agent 对应的 session/resume token
• cli/src/commands/codex.ts:42 - 支持 hapi codex resume <sessionId>
• cli/src/claude/claudeLocal.ts:49 - Claude 本地模式在已有 sessionId 时会传 --resume
• cli/README.md:29 - CLI 文档已写明 Codex resume 命令

Need more info:

• 你说的“复用本地 session”，是指“恢复 HAPI 里已有但 inactive 的会话”，还是“把独立在本地终端里启动的已有会话后续接入 HAPI”？
• 主要想支持哪种 agent：Claude、Codex、Cursor、Gemini，还是 OpenCode？

---

HAPI Bot

[xiaobaifly7]

是“把独立在本地终端里启动的已有会话后续接入 HAPI”？

[hqhq1025]

This is also a pain point for me — I often start a Claude Code session in the terminal, work for a while, then want to continue on my phone or another device through HAPI's web UI.

Here are a few possible approaches from a user experience perspective. Would love to hear which resonates most with everyone.

---

Option A: "Pick up" from the Web UI

When creating a new session on the HAPI web, you'd see a list of locally running or recent Claude/Codex sessions, and click one to adopt it.

• UX: Like "remote desktop" — connect to an existing window
• Pros: Discoverable, no terminal knowledge needed, mobile-friendly
• Cons: Requires the runner to scan local session files; list could get cluttered
• Implementation: Medium — CLI session scanner already exists for Codex, needs equivalent for Claude + a new "adopt" flow in the web UI

Option B: hapi attach from the terminal

You'd run a command like hapi attach or hapi adopt <session-id> from the terminal where a Claude/Codex session is already running (or recently ran).

• UX: Like tmux attach — "I'm already here, just hook it up to HAPI"
• Pros: Feels natural for terminal users; explicit, no accidental adoption
• Cons: Requires terminal access; not useful if you only have your phone
• Implementation: Easier — reuse existing --resume flag, just need session file discovery + metadata registration

Option C: Auto-discovery by the runner

The HAPI runner continuously watches ~/.claude/projects/ and ~/.codex/sessions/ for new session files. Any new session automatically appears in the web UI.

• UX: Zero friction — everything just shows up
• Pros: Seamless, no manual steps
• Cons: Could surface too many throwaway sessions; privacy concern if multiple users share a machine
• Implementation: Harder — needs file watching, filtering heuristics, and a way to ignore irrelevant sessions

---

My take

I'd lean toward Option A + B combined: auto-discovery with an explicit "adopt" action. The runner detects available local sessions, shows them in the web UI as adoptable, but doesn't sync them until the user clicks "connect". This gives you the discoverability of A, the explicitness of B, and avoids the noise of C.

@tiann What do you think? Is this something you'd want to support, and if so, which direction feels right?

[tiann]

I just do 'alias cc="hapi claude"'

All of my claude session are managed by hapi.

[xiaobaifly7]

我就直接用 alias cc="hapi claude" 试试

我所有的 Claude 会话都由 hapi 管理。
如果没有显式的入口，操作起来会很麻烦，根本无法使用