Your First Session

The best first use of MindMux is not "ask a random question". It is to open a real project and let the app convert discussion into durable structure.

Recommended first flow

1. Open a project folder.
2. Let MindMux attach to or create a brain/.
3. Start a session about the project background, architecture, or current decision surface.
4. Review the generated knowledge outputs.
5. Turn settled work into a task when execution is needed.

Good first prompts

Useful starting prompts usually ask the system to compile or clarify project state:

• "Summarize this project's current architecture and open questions."
• "What context should go into the background and roadmap docs?"
• "Turn today's discussion into durable pages and decision notes."
• "Prepare a task for the implementation work we just agreed on."

What to expect

During early use, MindMux will feel like a chat app. The difference shows up after the session:

• the brain becomes more complete
• future sessions need less repeated explanation
• tasks can be dispatched with better context

First outputs to aim for

The highest-value initial outputs are usually:

• background.md
• architecture.md
• a small set of decision or concept pages
• one or two actionable tasks

That gives the project a usable memory foundation quickly.

What not to do

Avoid using the first session as an unstructured dumping ground. MindMux works best when the discussion is driving toward:

• clarified project context
• explicit decisions
• reusable knowledge
• clean execution handoff

After the first session

Once the project has a basic brain, the next good workflows are:

• forking sessions when one discussion splits into alternatives
• dispatching execution tasks with attached context
• refining root docs as the project evolves