> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/flows/node-red-flow-editor/solution-ai.md).
# SolutionAI
SolutionAI is an assistant panel that helps you build and refine flows directly inside the Flow Editor. It can suggest nodes, explain configuration, and answer questions while you work.
## Where to Find It
Open any Flow and click **Edit Flow** to launch the Flow Editor. In the right sidebar, select the **SolutionAI** tab to open the panel.
SolutionAI in the Flow Editor right sidebar.
## What You Can Do
* Ask questions about nodes, Flow structure, and configuration.
* Get suggested nodes or changes and insert them into your flow.
* Start a new thread at any time using **New Conversation**.
## Web Search Support
SolutionAI can perform web search to pull in fresh sources when answering questions in the Flow Editor, Design, and Data Model experiences.
## Workspaces Per Flow
Each flow has its own SolutionAI workspace. When you switch flows, the conversation history stays scoped to the flow you are editing.
---
# 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.contextual.io/documentation-and-resources/components-and-data/flows/node-red-flow-editor/solution-ai.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.
