Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Workspace file access endpoints for Ralph server
Why?
The agent's workspace is the source of truth for everything it produces. Until now, the only way to browse that workspace was through the Gollum wiki viewer. These new endpoints give any HTTP client (the Gollum UI, custom dashboards, or future tools) direct read/write access to the live workspace, without requiring filesystem access or a separate process.
This could be important for the Gollum wiki workflow: users can now explore, edit, and manage workspace files through their own interfaces, and the /log endpoint exposes git history so clients can show what the agent has been doing without shelling out to git themselves. This adds a layer of accessibility for nightshift users.
Summary
Details
The Ralph daemon now serves as a file gateway for the workspace it manages. Clients can browse, read, create, and delete workspace files over HTTP without needing direct filesystem access. All file/tree endpoints validate that resolved paths stay within the workspace boundary and return 400 on traversal attempts, 404 on missing resources, and 501 if no workspace is configured. The limit param on /log is parsed and clamped to prevent injection.
Tests