# Give Helm the right context

Make the workspace, instance, and source of a request explicit.

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



A good answer depends on the right context. Minds has several boundaries that are easy to confuse: your signed-in account, your organization, the selected instance, and the namespace an operation may access.

## Check the selected Mind [#check-the-selected-mind]

Before asking about an instance, confirm the selected Mind in the workspace. Switching the visible instance does not grant additional permissions. Direct requests still require credentials that authorize the target namespace and action.

## Refer to a source [#refer-to-a-source]

The composer can insert reference tokens such as `@memory:`, `@keyspace:`, and `@file:`. Add the relevant identifier or description. The current control inserts text into the draft; it does not by itself upload a file or fetch its contents.

When the answer depends on a source, ask for the source and the basis of the conclusion. If retrieval is unavailable, open the relevant workspace view or use an authenticated instance request.

## Keep conversation history and memory distinct [#keep-conversation-history-and-memory-distinct]

A message visible in a chat is not automatically proof that it was written into persistent Akasha memory. For application workflows, explicitly store the information using the appropriate memory API, retain the returned identifier, and verify recall in a separate request.

[Memory concepts](/docs/concepts/memory) · [Connect an agent](/docs/agents) · [Verify a connection](/docs/getting-started/connection-check)