Search and context

Atmina searches the files you can reach and returns the source for each match. Ask plainly for a subject, add dates when recency matters, and open a cited result before acting on an important claim.

An agent can search one Knowledge Base or, when its configuration permits, across several accessible bases. It can also list files, read a file, inspect its outline, follow related memories, and request the Knowledge Base context assembled from current state and recent activity.

When searchable Companion text represents a picture, the result still cites the Companion you can read and edit. It may also include an asset block with the picture's path, file ID, format, dimensions or page count, media state and thumbnail address. Fields are omitted when the search path cannot resolve them; treat the Companion citation as the evidence.

Search respects access at the time of the request. A missing result may mean the file is outside the selected Knowledge Bases, excluded from search, still indexing, or unavailable to the person responsible for the agent. Check Files, the active agent’s knowledge scope, and team health.

Anonymous public search

An anonymous MCP connection to a public Knowledge Base exposes only search. It searches the current public collection: published pages and permitted referenced assets by default, plus any folders the owner explicitly included. It cannot search the rest of the Knowledge Base. Assets contribute only eligible searchable projections, such as verified Companion text.

_system/, _staged/, _pulse/, and _exports/ are always excluded from anonymous access. _sources/ and _consolidated/ require separate owner opt-ins. A scope change applies to every anonymous access method, not just the search box. See Publish a Knowledge Base for the controls.

See reading memory in the app to inspect the evidence behind a result.