Can not resume session when using hapi to run it locally

[SweetStanleyL]

What version of HAPI is running?

0.16.6

What platform is your computer?

Linux 6.8.8-060808-generic x86_64 x86_64

What issue are you seeing?

1. start Claude Code by 'hapi' locally.

• the session is visible in on the web hapi list
• but invisible in 'hapi --resume/ claude --resume' list

2. start session through web controling

• session is visible in both web list and hapi --resume/ claude --resume list

Claude code analysed that the remote start use 'cli' entrypoint while the local start use 'sdk-ts' entrypoint with 'hapi/cli/src/claude/sdk/query.ts' :line 324

What steps can reproduce the bug?

start session in the two different ways

What is the expected behavior?

The session can be resumed by claud --resume when use hapi to start it locally.

Additional information

No response

[github-actions]

I checked the Claude launch paths in this repo, and your observation about different entrypoints is correct.

When hapi is started directly from the terminal, HAPI defaults Claude to local mode and spawns the installed claude CLI directly. In that path, HAPI tracks the Claude session_id through a SessionStart hook. When a session is started through the runner/web flow, HAPI forces remote mode, uses the SDK path, and that path explicitly sets CLAUDE_CODE_ENTRYPOINT=sdk-ts before spawning Claude.

So the code does confirm that local terminal starts and web/runner starts are not using the same Claude entrypoint. What I could not verify from this repo alone is whether sdk-ts is the root cause inside Claude Code's own --resume picker. I also did not find code here that makes local launches use the same SDK path as runner/web launches, or code that explicitly registers local launches into Claude's resume picker.

Relevant code:

• cli/src/claude/runClaude.ts:138 - terminal-started Claude defaults to local; runner-started Claude defaults to remote
• cli/src/claude/claudeLocal.ts:91 - local mode spawns the installed claude executable directly
• cli/src/claude/runClaude.ts:95 - local path starts a SessionStart hook server to learn Claude session_id
• cli/src/runner/run.ts:362 - runner/web launches force --hapi-starting-mode remote --started-by runner
• cli/src/claude/sdk/query.ts:322 - SDK path sets CLAUDE_CODE_ENTRYPOINT = 'sdk-ts'
• cli/src/claude/claudeRemote.ts:246 - remote path waits for the Claude transcript file before marking the session found
• cli/src/claude/utils/path.ts:4 - transcript path resolves under ~/.claude/projects/...

Need more info:

• What does claude --version print on the machine where this happens?
• In the failing local HAPI session, did you send at least one prompt and get one Claude response before exiting?

---

HAPI Bot

[SweetStanleyL]

What does claude --version print on the machine where this happens? "2.1.92 (Claude Code)"

In the failing local HAPI session, did you send at least one prompt and get one Claude response before exiting? "YES"

For more information, AI analysed that extractSDKMetadataAsync() will call query() and then query() will set

if (!process.env.CLAUDE_CODE_ENTRYPOINT) {
process.env.CLAUDE_CODE_ENTRYPOINT = 'sdk-ts'
}

This makes the env: CLAUDE_CODE_ENTRYPOINT=sdk-ts, and when spawn claude locally, the env will be reused which leads to the entrypoint change with sdk-ts。