🤖 Fix ENOENT error in todo_write for SSH runtimes #449
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ensure temp directory exists before writing todos.json. Previously, writeTodos() assumed the directory already existed, but SSH runtime initialization could fail to create it, resulting in ENOENT errors. Added fs.mkdir() with recursive: true to create the directory if needed.
Replace direct fs operations with runtime abstraction to support SSH
runtimes. Key changes:
- readTodos/writeTodos now use readFileString/writeFileString helpers
- Directory creation uses runtime.exec('mkdir -p') instead of fs.mkdir
- Test helpers updated to accept Runtime parameter
- All tests updated to use createRuntime() for local testing
This enables todo persistence to work correctly on both local and SSH
runtimes.
ammario
approved these changes
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
SSH runtime agents encounter ENOENT errors when calling
todo_write:The root cause was that the todo tool was using Node's
fsmodule directly, which only works on the local filesystem. For SSH runtimes, file operations must go through the runtime abstraction.Solution
Refactored todo tool to use runtime abstraction for all file operations:
readTodos/writeTodosnow usereadFileString/writeFileStringhelpers from@/utils/runtime/helpersruntime.exec('mkdir -p')instead offs.mkdir()RuntimeparametercreateRuntime({ type: 'local' })Testing
Generated with
cmux