# Meet Helm

Describe the work. Keep the relevant controls in the conversation.

Source: https://docs.minds.sh/docs/helm



Helm is the conversational operator for Minds. It gives you a place to ask questions, work through setup, and review structured responses without starting in an administrative dashboard.

**Tell Helm what you want to accomplish.** When an action is supported, the conversation can show the choices, fields, and progress you need. Open the workspace when you want to inspect the underlying state.

<Callout title="A note on the current interface">
  The live chat screen still uses the name **Operator**. These guides use **Helm**, the Minds product name. The current implemented action flow creates a Mind; other rendered cards are not proof that an arbitrary management or memory action was executed.
</Callout>

## Start with a clear request [#start-with-a-clear-request]

* “Create a new Mind for my research.”
* “Explain what this instance setting means.”
* “Help me understand the difference between episodic and procedural memory.”

Include the outcome and the relevant scope. If a request concerns stored data, verify that the right instance is selected and that the relevant retrieval tool is actually connected.

## Conversation and control belong together [#conversation-and-control-belong-together]

A reply can contain an explanation, a form, a choice, or a link to a detailed view. A confirmation should make the proposed action understandable before it runs. A result should show what happened, rather than simply repeating what you requested.

[Write useful requests](/docs/helm/conversations) · [Understand artifacts](/docs/helm/artifacts) · [Use context](/docs/helm/context)