Repository navigation
Allow setting HOST - access outside of localhost #8
Description
For users who want to run this on a different mac and connect using a different computer (like using omp on a windows PC), this is currently impossible because of the localhost checks.
There needs to be either a config variable or other way of indicating remote access.
I'm not asking for full tailscale/other config, just opening up to same network connections, and we can even still use the generated API keys rec already creates.
Reacted by Kevan Emmott
Activity
raarts commentedon Oct 22, 2026
Yes, just listen to 0.0.0.0, so I can run opencode on my lower-powered laptop, and rec on my MacMini M4 Pro. Please.
ChrisCummins commentedon Oct 22, 2026
Hi @nintendo424 and @raarts, that seems like a very reasonable request. We'd not thought to support this use case. Looking into it now. Thanks!
Chris, MTS @ Recursive
KaiRawal commentedon Oct 22, 2026
Workaround that was seamless for me was to run
rec serveon mac mini, and open an ssh tunnel to it from my macbook (tested via opencode on the macbook, works great!)raarts commentedon Oct 22, 2026
I fixed it another way: I wanted to run Flint as a backend model for Claude, but Flint doesn't support the Anthropic protocol. To work around that I installed the LiteLLM-proxy on my MacMini, which incidentally can listen on 0.0.0.0, so I killed two birds with one stone. Now happily running Claude on Flint!
ccbiff commentedon Oct 23, 2026
Yes please. I'm rarely working on the same machine where I serve models.
kemmott commentedon Oct 23, 2026
++ for this! Hermes in Umbrel running on an older Mac mini, m4 pro Mac mini to serve models...
strin commentedon Nov 5, 2026
Thanks for your patience here. I reviewed both host-binding PRs and recommend #31 as the focused base rather than the broader #18. I requested one follow-up on #31 to keep authentication explicit for non-loopback serving through the direct engine entry point, with regression coverage. The host feature is not merged or released yet; the SSH-tunnel workaround discussed above remains the available option in the meantime. I have not closed either contribution.