Repository navigation
[codex] Show desktop interface and explain engineering - #26
Merged
Merged
Conversation
AndreKalberer
marked this pull request as ready for review
October 21, 2026 23:31
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 Harbor's actual desktop interface in the README and explain the application structure, local state, shared modules, desktop isolation, and release tooling. Add a repeatable screenshot command that launches the real app with a disposable profile, completes onboarding, and captures its browsing screen without personal state.
Validation:
npm test,node --check tests/capture-readme.cjs, andnode tests/capture-readme.cjs; visually inspected the resulting screenshot. No application or release behavior is changed.The existing
capture-ui.cjsroutine failed a keyboard-dialog/focus assertion, then reached its harness timeout. That existing UI issue was not changed by this documentation task. The new capture verifies loaded media cards and closed onboarding only; it does not establish full interactive smoke-test success.