No client-side file provider, unsaved buffers are invisible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Codex with our Eclipse IDE plugin (codexide.org)
What feature would you like to see?
fs/* goes from client to server (the client reads the server's FS), never the other way around. Codex therefore always reads from disk.
If the user has uncommitted changes in Eclipse, the agent reasons on a stale version and then overwrites it.
There is no overlay mechanism or dryRun anywhere in the schema.
Request: a server -> client fs/readFile request (the client serves the buffer content), or an unsavedFiles field per turn.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the fs/* schema and the client/server request handling, especially the proposed fs/readFile direction. Compare that path with the suggested unsavedFiles and dryRun concepts. Done means the agent can account for Eclipse's unsaved buffer content instead of relying only on disk and overwriting newer edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100