127.0.0.1 - - [24/Apr/2025 14:56:17] "GET /api/status/story-6e461a36-eb82-4256-ab4f-f30d9f9d0516 HTTP/1.1" 200 -
127.0.0.1 - - [24/Apr/2025 14:56:22] "GET /api/status/story-6e461a36-eb82-4256-ab4f-f30d9f9d0516 HTTP/1.1" 200 -
127.0.0.1 - - [24/Apr/2025 14:56:29] "GET /api/status/story-6e461a36-eb82-4256-ab4f-f30d9f9d0516 HTTP/1.1" 200 -
In the middle of an ultra-long writing task, the PC was restarted due to a Windows system failure. After restarting, I opened WSL and ran WriteHERE. Although the task was still shown as ongoing and the terminal kept displaying code 200, checking the LLM API panel revealed that WriteHERE was not calling the LLM to continue the task.Needs a robust checkpointing mechanism.
In the middle of an ultra-long writing task, the PC was restarted due to a Windows system failure. After restarting, I opened WSL and ran WriteHERE. Although the task was still shown as ongoing and the terminal kept displaying code 200, checking the LLM API panel revealed that WriteHERE was not calling the LLM to continue the task.Needs a robust checkpointing mechanism.