Replies: 2 comments
|
Im looking into this |
|
Yes, you do still need to explicitly set PLANNOTATOR_REMOTE=1. Even though SSH_TTY is present in your shell, the background processes and plugins usually don't rely on it because it can be unreliable across different terminal multiplexers (like tmux) and sub-processes. By setting export PLANNOTATOR_REMOTE=1, you are explicitly telling Plannotator to: Stop trying to fire the underlying OS open or xdg-open command (which fails silently on a headless SSH machine, hence why you see the message but no URL). Since you are already SSHing over Tailscale, just add the port forward to your ssh command: ssh -L 19432:localhost:19432 user@your-tailscale-ip Or if you are using VS Code Remote / Cursor over SSH, use the built-in "Ports" tab at the bottom to forward 19432 Once you do that and run /plannotator-annotate with PLANNOTATOR_REMOTE=1, it will print http://localhost:19432 in the console, and you can just click it and it'll open perfectly on your local browser! |
Uh oh!
There was an error while loading. Please reload this page.
I'm ssh'ing into my dev machine (over tailscale/headscale) and trying to use this invocation with plannotator:
(Because SSH_TTY is set, I should not need to use
PLANNOTATOR_REMOTE=1, right?)But, when I invoke
/plannotator-annotateI never see a URL displayed in the web UI nor in the console. I see this message, but no URL at all:Is there something I need to do to get the URL to display in the web UI? And, will this URL go to localhost? If so, it won't point to the machine on which I am using the browser. Can I configure that to go to a remote URL (the same tailscale machine) and make sure plannotator is listening on 0.0.0.0? Or, just use the plannotator.ai URL since the URL contains the state encoded, right?
All reactions