Manual/Get started
Your first conversation
Type what you want in plain words and press enter. moh reads what it needs, works on your request and reports as it goes. While it works you are never a spectator: you can redirect it, pause it, or stop it.
Ask for something
Good first requests are concrete and small. For example:
› look at this project and explain what it does › the contact form doesn't send — find out why › add a "last updated" date to the footer of every page
Press shift+enter for a new line inside the same message (on older terminals, option+enter or ctrl+j). To attach a file, type @ — see Files, images and the shell.
Watch it work
The bottom of the screen always tells you where you are: which AI model is answering, the project folder, how full the conversation's memory is, and which caution level is on (more in the three caution levels).
Steer, pause, stop
| You want to… | Do this |
|---|---|
| Add an instruction mid-task | Just type and press enter. moh reads it while it works and adjusts course — "also keep the old behaviour", "use the blue button instead". |
| Stop everything now | Press esc twice. The work done so far stays; nothing is half-written behind your back. |
| Take the composer back | ctrl+c clears what you are typing (ctrl+z brings it back). On an empty line, press it twice to quit. |
| See every key | ? or ctrl+k. |
When moh needs your permission
Before it changes a file or runs a command it pauses and shows you exactly what it wants to do:
y allows it this once, a allows it for the rest of this conversation, e lets you change it before it runs, n says no — moh then looks for another way or asks you. The whole system is explained in moh asks before it acts.
Two ways to read the screen
Press ctrl+o to switch between the two views of the same conversation:
Plain language. Actions read like "edited a file", "ran a command", and the numbers stay out of the way. Good when you care about the result.
The detail: exact commands, file paths, token counts and turn numbers. Good when you want to check how the work was done.
Nothing changes in the work itself — only how it is shown.
New to the terminal?
That's fine. The only skills moh asks of you are typing and pressing enter. If you are unsure what something on screen means, ask moh directly: "what did you just do?" is a perfectly good message.
Written for moh 0.61. Inside moh, ctrl+h opens the built-in manual for your exact version.