Execute local prompts in SSH remote shells
Local prompts execute remotely over SSH with zero server setup and keys never leave your machine.

Local prompt execution over SSH channels means zero server-side installation.
DevOps engineers and sysadmins working with remote servers
sshfs · rsync · Teleport
$ promptctl ssh user@server
makes a set of locally defined prompts "magically" appear within the remote shell as executable command line programs.For example, I have locally defined prompts for `llm-analyze-config` and `askai`. Then on (any) remote host I can:
$ promptctl ssh user@host # Now on remote host $ llm-analyze-config /etc/nginx.conf $ cat docker-compose.yml | askai "add a load balancer"
the prompts behind `llm-analyze-config` and `askai` execute on my local computer (even though they're invoked remotely) via the llm of my choosing.This way LLM tools are never granted SSH access to the server, and nothing needs to be installed to the server. In fact, the server does not even need outbound internet connections to be enabled.
Local prompts execute remotely over SSH with zero server setup and keys never leave your machine.
Local prompts appear as remote commands over SSH — no server install, no key exposure.
Executes local LLM prompts on remote SSH shells without installing agents or opening firewalls.
Prompts execute locally over SSH — no API keys or LLM access on production servers.
SSH integration where prompts execute locally but appear remotely is genuinely clever security-wise.
SSH integration means prompts work remotely without installing anything on target servers.