Ask Oracle

Ask and inspect

Sign in, select your space and open Oracle. Type in the message box and press Send or Enter; Shift+Enter adds a line. History opens saved conversations. Chat does not start the microphone or connect voice.

Select Voice to open the particle orb and allow the browser's microphone request if shown. When Oracle says it is listening, ask a question and pause. Use the microphone control to mute and unmute. Back to chat or Escape stops audio and returns to the same conversation. If voice takes time to open or cannot connect, chat remains available. Oracle can greet you, explain how to get started, and carry a follow-up using recent turns in this conversation. For questions about your knowledge, its Cloudflare agent chooses search, page-reading and process-discovery tools, then cites the permitted pages it used. If information is missing, it says what is missing.

While voice is enabled, microphone audio streams continuously to Cloudflare, including pauses and silence. Mainmind does not save raw or generated audio. Silence by itself does not submit a question, but those audio frames still reach Cloudflare so it can detect when a spoken turn starts and ends. Oracle completes the response and validates any sources before speech begins.

You can speak over playback to interrupt the current answer. Muting, opening another panel, hiding the tab, leaving Oracle or switching spaces stops capture and playback. Return to chat and select Voice to start another session, or use the microphone control while the voice surface is open. Read aloud makes a separate bounded replay of an existing saved answer; it does not reopen the microphone.

The particle presence responds to your voice and the answer's playback. A soft particle orb stays round while surface currents and depth change with the conversation. Audio moves its surface as the sound plays. The words beside it state what is happening; motion and colour never stand in for evidence or approval. Reduced motion keeps the presence still and all controls available.

Conversations belong to your membership. They are retained for thirty days after your last question; you can delete one sooner. They are separate from deliberately retained knowledge. Keep passwords and keys in Accounts, never in a conversation.

An accepted typed question can continue if you leave and return. Stop prevents a late answer from being added. A live voice interruption cancels the active answer and speech; its question remains in the conversation to retry.

Answer waiting questions

On Knowledge, Answer the questions opens Oracle and walks you through the questions waiting on your answer, one at a time. Oracle says what it recommends, what the question changes and which way your past answers lean. Reply yes or no; "already done" closes a question that was answered somewhere else. Your answer counts only for the question Oracle just put to you, and only when your reply is a plain yes, no or "already done": a question back is never taken as an answer. To ask for changes, write them on the question's decision page. Oracle records one answer per reply, never from a spoken reply, and only the owner's answers are recorded here.

Keep useful work

The conversational agent can read knowledge in the space and record your own answer to a waiting question. To save a working note or request, open the answer details and its sources. Review its wording and target before submitting. The result appears in the existing page discussion or Work surface. A working note is not canonical policy; a request does not mean an agent has started. Use the existing decision and knowledge-write paths for governed changes.

If an action loses its response, check that same action to recover its receipt before submitting it again.

Improve the experience

Use feedback on an answer to describe a bug, friction, slowness or a missing capability. What you submit goes to Mainmind's builders under your name, and everyone in your space, including its agents, can see it and join its conversation. Repeated failures are also reported automatically, as an Oracle health check with no conversation text. The conversation is not attached automatically. Mainmind retains a receipt even if private issue delivery is unavailable.

The Owner can inspect aggregate diagnostics. Counts and durations help triage repeated problems; they do not contain conversation text or measure microphone-to-ear latency. Fixes follow the existing review and release process.

If your knowledge access changes, earlier conversations can become unavailable. Privacy lists their dates so you can explicitly delete them and free space without reopening their contents. Oracle requires sign-in with your linked GitHub account; an older invite cookie alone cannot open private conversations.