The conversation records cannot be saved

[noResign]

App Version

3.19.5

API Provider

DeepSeek

Model Used

deepseek-v3

🔁 Steps to Reproduce

os：mac
After the conversation ends and you return, there is no previous conversation record in the history record section

💥 Outcome Summary

src/utils/safeWriteJson.ts ==》throw error

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @noResign! I'm Dosu and I’m helping the Roo-Code team.

I couldn't find any documentation or existing discussions about the error in src/utils/safeWriteJson.ts or issues saving conversation records on macOS with DeepSeek. The error code ENOENT suggests that a required file or directory might not exist when Roo Code tries to save the conversation history. This could be related to missing folders or permissions in your local environment, but there are no official troubleshooting steps or known compatibility issues documented for this scenario.

If you can share the full error message or stack trace from the logs, I can help pinpoint the cause more precisely. Are you able to check if the directory where Roo Code saves conversation history exists and is writable on your system?

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[noResign]

Hi @noResign! I'm Dosu and I’m helping the Roo-Code team.

I couldn't find any documentation or existing discussions about the error in src/utils/safeWriteJson.ts or issues saving conversation records on macOS with DeepSeek. The error code ENOENT suggests that a required file or directory might not exist when Roo Code tries to save the conversation history. This could be related to missing folders or permissions in your local environment, but there are no official troubleshooting steps or known compatibility issues documented for this scenario.

If you can share the full error message or stack trace from the logs, I can help pinpoint the cause more precisely. Are you able to check if the directory where Roo Code saves conversation history exists and is writable on your system?

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  

Hi @noResign! I'm Dosu and I’m helping the Roo-Code team.

I couldn't find any documentation or existing discussions about the error in src/utils/safeWriteJson.ts or issues saving conversation records on macOS with DeepSeek. The error code ENOENT suggests that a required file or directory might not exist when Roo Code tries to save the conversation history. This could be related to missing folders or permissions in your local environment, but there are no official troubleshooting steps or known compatibility issues documented for this scenario.

If you can share the full error message or stack trace from the logs, I can help pinpoint the cause more precisely. Are you able to check if the directory where Roo Code saves conversation history exists and is writable on your system?

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  

hi @dosu
The directory exists.

[noResign]

The issue occurs when the safeWriteJson function attempts to acquire a file lock on the api_conversation_history.json file, but the file's parent directory doesn't exist yet. The proper-lockfile library performs an lstat operation on the target file path during lock acquisition, which fails with ENOENT when the directory structure hasn't been created.

The root cause is a race condition in the file creation process. While getTaskDirectoryPath creates the task directory with { recursive: true }, the lock acquisition in safeWriteJson happens before any directory creation logic within the function itself. The proper-lockfile library expects to be able to stat the target file path to determine lock file placement, but when the directory doesn't exist, this fails immediately.

The issue manifests when saveApiMessages is called during conversation history persistence. The function calls getTaskDirectoryPath to ensure the directory exists, then immediately calls safeWriteJson with the file path. However, there's a timing window where the directory creation might not be complete or visible to the lock acquisition process, especially on slower file systems or under high load conditions.

The fix should ensure that the parent directory of the target file exists before attempting lock acquisition, either by adding directory creation logic within safeWriteJson itself or by modifying the lock acquisition strategy to handle missing parent directories gracefully.

very good