[Bug] --resume flag doesn't indicate no conversations exist in new repository

Resolved 💬 1 comment Opened Dec 5, 2025 by alok Closed Dec 8, 2025

Bug Description
--resume on new repo should say ~(no convos in this repo! starting a new one) then prompt a new convo instead of erroring

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.0.59
  • Feedback ID: 37e99b04-4ec1-4e66-9ea1-c095287bc38f

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/alokbeniwal/.local/share/claude/versions/2.0.59 (expected in multi-process scenarios)\n    at Zh0 (/$bunfs/root/claude:2637:1622)\n    at mCA (/$bunfs/root/claude:2637:1300)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-05T23:37:12.242Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/alokbeniwal/.local/share/claude/versions/2.0.59 (expected in multi-process scenarios)\n    at Zh0 (/$bunfs/root/claude:2637:1622)\n    at gCA (/$bunfs/root/claude:2635:35603)\n    at async uG7 (/$bunfs/root/claude:2635:37711)\n    at async tx (/$bunfs/root/claude:2637:236)\n    at async <anonymous> (/$bunfs/root/claude:2637:13004)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-05T23:37:20.026Z"}]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗