Bring cumulative RemCodex improvements upstream - #1
Open
john-craig wants to merge 14 commits into
Open
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.
Summary
This pull request brings the cumulative RemCodex improvements from the
john-craig/remcodexfork intolupishan/remcodex. The source of truth remains the Gitea repository; the fork is configured as a public push mirror.Changes
Session and project workflows
Interactive Codex app-server support
remcodex-tuiwrapper. Bare invocation starts a discoverable Unix-socket app-server and launches the TUI throughcodex --remote; explicit Codex arguments pass through unchanged.MCP and diagnostics
Web UI and deployment
/directorypage driven by validatedREMCODEX_DIRECTORY_INSTANCESJSON configuration, with links to multiple RemCodex instances.REMCODEX_HOSTNAMEsupport so API/MCP session links can use the hostname seen by end users, while retaining relative links when unset.Validation
npm run buildnode --check web/app.jsThe Gitea source and public GitHub fork are configured to stay synchronized through the Gitea push mirror.