Done. I ran the real Limboo app, drove its navigation, captured a ful…#50
Conversation
…l set of high-quality screenshots, and wired them into the README. **What I did** - **Ran the app** — launched `npm start` with a CDP debug port, then drove the live Electron window over the Chrome DevTools Protocol (playwright-core installed only in the scratchpad, so the project stays untouched). - **Captured 10 screenshots at 2× resolution (3200×1900 PNG)** into a new [assets/screenshots/](assets/screenshots) folder, covering the whole navigation: - `01-main-shell` — the clean conversation-first shell - `02`–`07` — each activity-rail panel: Files, Changes, Git, Memory, Tasks, Terminal - `08`–`10` — command palette (Ctrl+K), global search (Ctrl+P), and the Settings modal - **Verified every frame visually** and fixed two problems along the way: the Files panel initially showed "No files indexed," so I clicked *Reindex workspace* first to capture a populated tree; and the terminal's PTY was swallowing the Ctrl+K/Ctrl+P shortcuts (the `^K` literally landed in the shell), so I retook those with focus moved off the terminal. - **Updated [README.md](README.md)** — a hero shot of the main shell right under the title, plus a new **Screenshots** section with a two-column captioned gallery of the eight panels/overlays and a full-width settings shot. - **Cleaned up** — shut the app down afterward; the dev process exited cleanly. The changes are uncommitted on the `attachment` branch (`README.md` modified + the new `assets/screenshots/` folder, ~3.4 MB total). Say the word if you'd like them committed.
|
Warning Review limit reached
Next review available in: 30 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (10)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Summary
This PR adds valuable documentation with a hero screenshot and a comprehensive Screenshots section to the README. However, there is a critical blocker that must be resolved before merge:
Blocking Issue:
The README references 10 screenshot files in assets/screenshots/ directory, but none of these image files are included in this commit. According to your PR description, the screenshots are "uncommitted on the attachment branch." This will result in all image links being broken when the PR is merged.
Required Action:
Add all 10 screenshot files (01-main-shell.png through 10-settings.png) in the assets/screenshots/ directory to this commit before merging.
Once the screenshot files are added, the documentation changes look good and will significantly improve the README's visual appeal and clarity.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
|
|
||
| <br /> | ||
|
|
||
| <img src="assets/screenshots/01-main-shell.png" alt="Limboo — sessions, the conversation-first workspace, and the composer on the pure-black shell" width="920" /> |
There was a problem hiding this comment.
🛑 Broken Image Reference: The PR references assets/screenshots/01-main-shell.png but the screenshot files are not included in this commit. According to the PR description, the screenshots are "uncommitted on the attachment branch". This will create a broken image link when merged. Include all 10 screenshot files in the commit before merging.
| ## Screenshots | ||
|
|
||
| A tour of the shell: sessions on the left, the conversation in the center, and | ||
| the activity rail on the right — every panel below is one click on the rail. | ||
|
|
||
| | | | | ||
| | --- | --- | | ||
| | **Files** — the indexed workspace tree with per-language icons<br /><img src="assets/screenshots/02-files-panel.png" alt="Files panel — indexed workspace tree" /> | **Changes** — live git status with per-file diff stats<br /><img src="assets/screenshots/03-changes-panel.png" alt="Changes panel — live git status" /> | | ||
| | **Git** — stage, commit, history, branches, and checkpoints<br /><img src="assets/screenshots/04-git-panel.png" alt="Git panel — staging and commit" /> | **Memory** — durable project knowledge with tiered proposals<br /><img src="assets/screenshots/05-memory-panel.png" alt="Memory panel — project knowledge" /> | | ||
| | **Tasks** — the agent's live plan and progress<br /><img src="assets/screenshots/06-tasks-panel.png" alt="Tasks panel — agent plan" /> | **Terminal** — workspace-scoped PTY sessions<br /><img src="assets/screenshots/07-terminal-panel.png" alt="Terminal panel — integrated PTY" /> | | ||
| | **Command palette** — every command behind <kbd>Ctrl/Cmd</kbd>+<kbd>K</kbd><br /><img src="assets/screenshots/08-command-palette.png" alt="Command palette overlay" /> | **Global search** — files, symbols, docs, memory, commits, sessions<br /><img src="assets/screenshots/09-global-search.png" alt="Global search overlay" /> | | ||
|
|
||
| **Settings** — general, appearance, agent, git, memory, and advanced JSON editing | ||
| in one modal: | ||
|
|
||
| <img src="assets/screenshots/10-settings.png" alt="Settings modal" width="920" /> |
There was a problem hiding this comment.
🛑 Broken Image References: This entire Screenshots section references 9 image files (02-10) in assets/screenshots/ that are not included in this commit. All markdown image links will be broken when merged. Add all screenshot files to the commit.
1 participant
…l set of high-quality screenshots, and wired them into the README.
What I did
npm startwith a CDP debug port, then drove the live Electron window over the Chrome DevTools Protocol (playwright-core installed only in the scratchpad, so the project stays untouched).01-main-shell— the clean conversation-first shell02–07— each activity-rail panel: Files, Changes, Git, Memory, Tasks, Terminal08–10— command palette (Ctrl+K), global search (Ctrl+P), and the Settings modal^Kliterally landed in the shell), so I retook those with focus moved off the terminal.The changes are uncommitted on the
attachmentbranch (README.mdmodified + the newassets/screenshots/folder, ~3.4 MB total). Say the word if you'd like them committed.Summary
Type of change
Architectural reasoning
Verification
npm run lintpassesnpx vite build --config vite.renderer.config.mtspassesnpm start(for main/preload changes)Security checklist (if touching main process)
shell: true)contextIsolation/sandbox/ CSP / navigation lockdownDocumentation and changelog
docs/CHANGELOG.mdentry (if user-facing)Theme discipline (for UI changes)
dark:variants, no gradients)Note
Low Risk
Documentation-only README and image assets; no runtime or security surface affected.
Overview
Adds marketing visuals to the README so newcomers can see the product before cloning: a hero image of the main three-pane shell under the header links, plus a new Screenshots section.
The gallery is a two-column table of captioned PNGs for the activity-rail panels (Files, Changes, Git, Memory, Tasks, Terminal), command palette, and global search, with a full-width Settings modal shot. Images live under
assets/screenshots/(01–10).No application, IPC, or build code changes—documentation and static assets only.
Reviewed by Cursor Bugbot for commit b807652. Bugbot is set up for automated code reviews on this repo. Configure here.