When debugging, you probably will need a couple of attempts to find the source of the bug. For each attempt, you could opt to use a new screen, so you will only see the output of your current attempt. There are three ways for creating a new screen.
Clicking the + button in the menubar
By executing ray()->newScreen() somewhere in your code. Optionally, you can pass a screen name as an argument to newScreen.
By pressing cmd+K on Mac or ctrl+K on Windows when the Ray app is active. When the Ray app is not the active one, press cmd+shift+K on Mac or ctrl+shift+K` on Windows to clear the screen.
If you want Ray always to be on top, just toggle on the Keep on top toggle on the menubar. In our experience, this is pretty handy to make sure that Ray is always visible, event when switching applications or workspaces.
At the bottom of every item that displayed in Ray, you'll see a link that, when clicked, will take you to where this item was sent to ray. You can use this to, after debugging, quickly find locations where ray() calls are made, so you can remove them.
When a Ray screen is displaying many items, it might be bothersome to click each item. In this case, you can click "List files" to get a unique list of locations where a Ray call is in your source code.
Should you forget to remove a ray() call in a Laravel app, and push your code to production, no worries. Ray will not try to transmit any info in a production environment.