> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/user-guide/using-the-open-brush-tools-quick-tools-and-menu-panels/extras-panel/lights-panel.md).
# Lights Panel
Use Lights to modify your scene's primary and secondary lighting colors and positioning.
* The sun is your primary light, and it casts shadows.
* The sun is the brighter light.
* The moon is your secondary light, it doesn’t cast shadows.
* The fill light floods the scene with an equal distribution of color and light. It's effects are most easily seen in the shadow color of your scene.
* You can grab and move the sun and moon by selecting with the trigger.
* You can change the color of all three light sources.
* The lighting effect is best observed on environments with a ground and object (i.e. pedestal), and in those sketches where there are at least a few strokes.
* The sphere the lights pivot around can be used as a representation/quick preview for placement of lights in the world.
* Custom lights save with sketches.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openbrush.app/user-guide/using-the-open-brush-tools-quick-tools-and-menu-panels/extras-panel/lights-panel.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
