Repository navigation
Show the web UI and explain tool safety and macOS permissions - #3
Merged
Merged
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.
Show the web UI with four screenshots: desktop chat, memory, Codex settings, and phone layout. The images use an explicitly labelled offline imported sample, with no personal chats or live provider calls.
Explain that macOS screen permissions belong to the app launching the server rather than the browser, and clarify that EternalChat's own tools are not sandboxed even though its Codex subprocess is read-only. Document computer-access Off and the separate after-turn command setting.
Validation: visually reviewed all four screenshots, checked the screenshot links, confirmed the docs against the tool/adapter code, and passed git diff --check. Documentation and image changes only.