Help

Start from the symptom, then open the shortest route to the fix.

Symptom-led routes

Check the quickest path for startup failures, port conflicts, and runtime setup issues.

Match the message to a known failure and its first recovery step.

Sort out expected behavior, stale memory, and common query questions.

Gather the right logs and diagnostics before asking for help.

See the current boundaries before you spend time debugging the wrong layer.

Use the doc-editing path when the page itself needs a fix.

memory status --project <project-slug>
memory doctor

Use these once, then follow the symptom-specific route above instead of repeating the same checks on every page.