OMP
The support matrix is the main reference for what Farhelm does with OMP. This page only adds what is specific to OMP.
Gotchas and quirks
Section titled “Gotchas and quirks”- Guarded uses
--approval-mode write, automatically approving workspace edits and asking before other actions. The separate approve choice asks before every tool action. Project rules and plugins can loosen either; see Permission modes. - New OMP launches default to Guarded unless you chose another mode or the launcher remembered one. Farhelm does not recognize OMP’s approval prompts: a session waiting for your approval still shows as running or idle, with no waiting alert.
- After
/new, the new conversation can be restarted right away, before OMP has replied to it. - OMP matches model names loosely: a typo or a retired model name can quietly start a different model instead of failing. If the exact model matters, check it in OMP itself after launch.
- Farhelm can follow the conversation when OMP is run as
omp(installed with npm or Bun), throughbun x, or as OMP’s compiled binary. Annpxlaunch runs, but on Debian, Ubuntu and other Linux systems whoseshis dash, Farhelm cannot follow its conversation, so Restart stays greyed out; elsewhere, including macOS,npxis untested. A wrapper prefix mustexecthe OMP command; a resident wrapper or Node launcher runs it normally, but Restart stays greyed out. - Restart refuses, rather than starting fresh, when OMP has compressed the conversation’s file into a
.jsonl.gzarchive, or has moved it and not yet said where. Replace the session to start over.