Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

TERMy

A fast terminal assistant that does not use LLMs

Details

External ID
49562219
Source
HN
Company
—
Product
TERMy
Website domain
github.com
Launched
Sept. 4, 2026
Cohort
—
Upvotes
225
Upvotes percentile
0.9712918660287081
Tags
—
Fetched at
Sept. 10, 2026, 5:31 a.m.
Updated at
Sept. 10, 2026, 5:31 a.m.

Description

I love research and development, you may have heard of me because of PJON (Padded Jittering Operative Network). It is a network protocol I started developing in 2010, which was recently implemented in silicon by the ETH Zurich university thanks to the research of Pius Sieber.I am excited to share with you TERMy, a terminal assistant built on top of the NPC-Forge framework. Unlike everything else being built today, TERMy does not use embeddings, machine-learning or LLMs. It runs on the CPU (even on a Raspberry Pi Zero) both in the terminal or client-side in a browser tab and responds in milliseconds. It is a cynical but very knowledgeable Linux terminal assistant that translates your natural language into shell commands without relying on a single artificial neuron.I had a chance to focus for 2 months on my personal projects since early July, during the strange times of AI price hikes and the end of subsidized tokenmaxing. I was curious to see if I could develop from scratch a terminal assistant capable of handling simple natural language requests. I have a bad memory and got used to ask to copilot "activate the virtual environment" or similar trivial operations spending a non negligible sum every month. I started thinking, maybe I can do something to make my workflow more efficient? Do I really need trillions of parameters to accomplish those tasks?How it WorksWhen you type a prompt, it goes through a lightweight NLU pipeline written in ~1000 lines of Python that implement the following steps:1. Strip expletives, interjections, encouraging, discouraging and thanking words (remove noise)2. Sentiment analysis3. Exact Match (very fast)4. Template Match (slower)5. Probabilistic Match (even slower)Step 5 relies on:1. IDF (Inverse Document Frequency) to identify rare words.2. BOW (Bag Of Words) to accommodate word inversions.3. IDF weighted Levenshtein to safely handle typos.Permission gating is hardcoded into the dataset and enforced for all potentially destructive commands, so it's inherently safer than letting an unpredictable LLM run wild on your machine.- TERMy in operation: https://www.youtube.com/watch?v=qeIp0xePLBg- Variance and typo tolerance: https://www.youtube.com/watch?v=tQvGDk6fkk0- Copilot integration: https://www.youtube.com/watch?v=Wzzouhq2a8A- Advanced features: https://www.youtube.com/watch?v=qeIp0xePLBg- Source Code: https://github.com/gioblu/NPC-Forge

Enrichment

Theme
lightweight and on-device AI runtimes
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
terminal assistant without llms
Manually corrected
False

Could you build this?

Partial A terminal assistant is achievable, but making it fast, useful, and intelligent without relying on LLMs necessitates a custom natural-language rule engine, index, and command synthesizer.

What it would actually take: The engine likely uses C/C++ or Rust to parse shell command manpages, history, and syntax trees into an indexed trie or vector space with heuristic intent matching. The challenging part is achieving robust, fault-tolerant intent parsing and shell command generation purely through deterministic grammars, pattern matching, and rule bases rather than neural networks. This demands expertise in rule-based NLP, formal language parsing, and POSIX shell internals.

Discussion

20 comments analyzed.

Competitors mentioned: Local LLMs, Google Translate, ELIZA

Concerns raised: Anaphora resolution errors in complex dialogs leading to unintended commands like 'delete it', Performance degradation with larger datasets, Safety risks running shell commands from arbitrary questions

Feature requests: Dataset for coding tasks/commands, Package discovery tool to recall installed tools for past tasks, Sentiment analysis influence on adjectives and interjections in responses

Competitors

Other products that read as similar to this one — 63 launches clear the similarity bar, closest 8 shown.

Attention rank: #3 of 64 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 302 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.