Things you might ask.

Starting from your explicit intent, review how the implementation meets requirements, what evidence supports it, and which choices or uncertainties need your judgment. This can cover product rules, architectural constraints, or algorithm logic.

No. Start with one requirement that matters. Refine it through conversation or edit Markdown directly, then examine the implementation and evidence.

Yes. You don’t have to move your whole codebase into Noea first. Write intent only for the parts you care about most; the agent keeps implementing the rest as before.

Your Agent can propose changes to intent. Review and adjust them; they enter the intent document only after you accept.

Plain Markdown files ending in .noea.md. Any editor can open them, and they go into Git.

Explanations and investigation results provide traceable evidence, not a guarantee of correctness. Review code, tests, and runtime results according to risk, and make the final judgment yourself. Noea works with your Coding Agent.

If no coding agent is available, the app walks you through choosing, installing, signing in and verifying one. The first verification downloads a runtime, and the app tells you how large it is.

Error reports and usage statistics are two separate switches, on the Privacy page in Settings. Only fixed categories of action events are collected, never your text, files or paths.