Modes and approvals
Modes and approvals
The mode under the message box sets what Hypheus may touch. Operating modes are Ask, Plan and Build.
The modes
| Mode | What it does | Files and commands |
|---|---|---|
| Ask | Answers questions and explains code. | Text only. No files are read or changed. |
| Plan | Works out an approach before any change. | Text only. No files are read or changed. |
| Build | Makes the change. | Reads and lists files, proposes edits, and runs commands. With Autopilot off, each proposed action waits for your decision. |
A session can also be set to Review, which checks work that has been done. Automatic plan and review passes inside one turn are not available: run them as separate turns.
Approval cards
In Build mode, when the agent wants to act, it stops and shows a card with:
- the action, such as an edit or a command;
- the target path;
- the effect, in plain words;
- for edits, a diff excerpt and Review native diff, which opens the full diff;
- Full arguments and binding, which shows the exact input and the digest the approval is bound to.
Select Approve once or Deny. An approval applies to that exact action only. Decisions stay in the conversation as "approved once", "denied" or "awaiting decision".
Results are not tests
A model response, a file change and a passing test are three different things. Hypheus reports what was done and points you to verifying it. Run your own tests.
For longer tasks
Use Autopilot to authorize eligible workspace file actions and commands for a bounded task. Commands rejected by its policy, or which it cannot classify, return for your decision.