HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tgalal
promptcmd
Rust2026–2026
tgalal / promptcmd

promptcmd

GenAI prompts as runnable programs

2Distinct people
14Mentions
0Explicit recommenders
48GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

GenAI prompts as runnable programs

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:02:30 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week14 dated mentions

Observed mentions: 2026-01-21 13:46:46 UTC to 2026-03-19 14:41:30 UTC. Weeks start Monday, UTC.

02468102026-01-19 00:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsJan 192026-01-26 00:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 162026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 9 mentions; 8 submissions, 1 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsMar 16

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 192026-01-19 00:00:00 UTC2026-01-26 00:00:00 UTC220
Jan 262026-01-26 00:00:00 UTC2026-02-02 00:00:00 UTC000
Feb 22026-02-02 00:00:00 UTC2026-02-09 00:00:00 UTC000
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC000
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC981
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC330

What Hacker News says

9 sources

Show HN: Execute local LLM prompts in remote SSH shell sessions

Hi HN, This is a tool I've worked on the past few months (not vibe-coded). Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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
Read the rest
, the server does not even need outbound internet connections to be enabled. Eager to get feedback! Github: https://github.com/tgalal/promptcmd/
2 points · Open discussion

Show HN: Execute local LLM prompts in remote SSH shell sessions

Hi HN, This is a tool I've worked on the past few months. Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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
Read the rest
not even need outbound internet connections to be enabled. Eager to get feedback! Github: https://github.com/tgalal/promptcmd/
3 points · Open discussion
tgalal·Mar 12, 2026Submission

Show HN: Execute local LLM prompts in remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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
Read the rest
2 points · Open discussion
tgalal·Mar 11, 2026Submission

Show HN: Execute local prompts in SSH remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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
Read the rest
7 points · Open discussion
tgalal·Mar 10, 2026Submission

Show HN: Execute local prompts in SSH remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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
Read the rest
4 points · Open discussion
tgalal·Mar 10, 2026Submission

Show HN: Bring your own prompts in SSH remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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: # 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. Github: https://github.com/tgalal/promptcmd/ Docs: https://docs.promptcmd.sh/
1 points · Open discussion
tgalal·Mar 9, 2026Submission

Show HN: Execute local prompts in SSH remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following command: $ 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: # 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. Github: https://github.com/tgalal/promptcmd/ Docs: https://docs.promptcmd.sh/
2 points · Open discussion
tgalal·Mar 9, 2026Submission

Show HN: Bring your own prompts to remote shells

Instead of giving LLM tools SSH access or installing them on a server, the following: promptctl ssh user@server makes a set of locally defined prompts "appear" within the remote shell as executable command line programs. For example: # on remote host analyze-config --help Usage: analyze-config [OPTIONS] --path <path> Prompt inputs: --all --path <path> --opt --syntax --sec would render and execute the following prompt: You are an expert sysadmin and security auditor analyzing the configuration file {{path}}, with contents: {{cat path}} Identify: {{#if (or all syntax) }}- Syntax Problems{{/if}} {{#if (or all sec) }}- Misconfigurations and security risks{{/if}} {{#if (or all opt) }}- Optimizations{{/if}} For each finding,
Read the rest
state the setting, the impact, a fix, and a severity (Critical/Warning/Info). Nothing gets installed on the server, API keys never leave your computer, and you have full control over the context given to the LLM. Github: https://github.com/tgalal/promptcmd/ Documentation: https://docs.promptcmd.sh/
3 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.