[Error] Failed to start Claude Code: Session **** already exists

[wliubtw]

Hi there, I would appreciate if someone can help me to look into the issue when I start the app and start sending message to Oracle Agent, it always shows the following error:

[Error] Failed to start Claude Code: Session **** already exists.

I have tried to kill the session and restart the app multiple times but I still get the same error.

[DavidsonGomes]

Hi — thanks for the report. This is exactly the bug we just fixed in develop: when the WebSocket reconnects (common behind a proxy), the frontend re-sends start_claude before learning the session is still alive, and the bridge threw "Session already exists" instead of just re-attaching.

Two PRs landed that together resolve it:

• claude-bridge.js: startSession is now idempotent — returns the existing session instead of throwing
• server.js: on duplicate start, replies with claude_started (re-attach) instead of error

Will ship in the next release. After updating with npx @evoapi/evo-nexus@latest ., the "Session already exists" toast should disappear. If you're in a hurry, you can pull develop manually and rebuild.

Please re-test after the next release and let me know if the issue persists.

[wliubtw]

Hi David, Thanks for your reply. I have tried debugging this bug with Google Antigravity for quite a while but still cannot resolve the issue. Another issue I found is the port 8080 confliction. I have tried the installation and setup in a few different machine and I often got having this port confliction issue when I started your evo-nexus app. I have had to manually killed another process (often used by an unknown Python process). Hope you can solve this problem. Regards, WEI LIU Digital Solutions Engineer M: +64 272 507 608 BTW ***@***.*** | www.btw.nz | +64 7 595 0020 From: Davidson Gomes ***@***.***> Sent: Tuesday, 21 April 2026 6:41 am To: EvolutionAPI/evo-nexus ***@***.***> Cc: Wei Liu ***@***.***>; Author ***@***.***> Subject: Re: [EvolutionAPI/evo-nexus] [Error] Failed to start Claude Code: Session **** already exists (Issue #18) EXTERNAL MESSAGE [https://avatars.githubusercontent.com/u/24706726?s=20&v=4]DavidsonGomes left a comment (EvolutionAPI/evo-nexus#18)<#18 (comment)> Hi — thanks for the report. This is exactly the bug we just fixed in develop: when the WebSocket reconnects (common behind a proxy), the frontend re-sends start_claude before learning the session is still alive, and the bridge threw "Session already exists" instead of just re-attaching. Two PRs landed that together resolve it: * claude-bridge.js: startSession is now idempotent — returns the existing session instead of throwing * server.js: on duplicate start, replies with claude_started (re-attach) instead of error Will ship in the next release. After updating with npx @***@***.*** ., the "Session already exists" toast should disappear. If you're in a hurry, you can pull develop manually and rebuild. Please re-test after the next release and let me know if the issue persists. — Reply to this email directly, view it on GitHub<#18?email_source=notifications&email_token=CBLSIHGCYXJWKE5TNUWALZL4WZVKPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGMZTSNBWHA32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4283394687>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CBLSIHBVJRAEW6VJM37AHD34WZVKPAVCNFSM6AAAAACX64A4YSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOBTGM4TINRYG4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>