<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LLM – Linux und Ich</title>
	<atom:link href="https://linuxundich.de/en/tag/llm/feed/" rel="self" type="application/rss+xml" />
	<link>https://linuxundich.de/en</link>
	<description>A German Linux blog, in English</description>
	<lastBuildDate>Sun, 22 Nov 2026 04:01:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>
	<item>
		<title>lxask: Linux commands from everyday language, powered by offline AI</title>
		<link>https://linuxundich.de/en/lxask-offline-ai-linux-commands/</link>
					<comments>https://linuxundich.de/en/lxask-offline-ai-linux-commands/#respond</comments>
		
		<dc:creator><![CDATA[Christoph Langner]]></dc:creator>
		<pubDate>Sun, 22 Nov 2026 07:15:24 +0000</pubDate>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Arch Linux]]></category>
		<category><![CDATA[Bash]]></category>
		<category><![CDATA[LLM]]></category>
		<category><![CDATA[Terminal]]></category>
		<guid isPermaLink="false">https://linuxundich.de/en/?p=470</guid>

					<description><![CDATA[lxask translates everyday language into Linux commands – offline, without a GPU, and without a cloud account. A hands-on test on Arch Linux with GNOME shows how well that works day to day, and where the small AI model hits its limits.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">A language model is great for plenty of things. For commands in the terminal, though, I wouldn&#8217;t necessarily reach for ChatGPT. A local model on your own drive is more practical – except not everyone has the hardware for it: a machine with plenty of GPU memory can easily cost more than 3,000 euros. <a href="https://linuxundich.de/en/llmfit-which-ai-models-run-on-my-machine/">llmfit</a> shows you what&#8217;s realistic on your own machine. <a href="https://github.com/arxhr007/lxask">lxask</a> takes a different approach: a small, optimized model that translates everyday language into Linux commands without needing a graphics card at all.</p>



<h2 class="wp-block-heading">Installation</h2>



<p class="wp-block-paragraph">lxask is built with Rust and llama.cpp and ships with a model trimmed down to 1.5 billion parameters (built on Qwen2.5-Coder, code under the MIT license). According to the project, it needs about 1.1 GB of disk space and up to 1.3 GB of RAM while running, and it doesn&#8217;t need root privileges. It runs on x86_64 and ARM64 with a current glibc, so practically any current distribution. I installed it on Arch Linux with the script from the project:</p>



<pre class="wp-block-code"><code>$ curl -fsSLO https://github.com/arxhr007/lxask/releases/latest/download/install.sh
$ sh install.sh</code></pre>



<p class="wp-block-paragraph">The script downloads all the files, checks them against the included checksums, and drops the program into <code>~/.local/bin/lxask</code>. If you want, the model stays loaded in memory, so answers take about 2 seconds instead of 7. The only thing you have to add yourself is the path – if <code>~/.local/bin</code> is missing from your <code>PATH</code>, the shell will just tell you &#8220;command not found&#8221; at first. Here&#8217;s how to add it permanently:</p>



<pre class="wp-block-code"><code>$ echo 'export PATH=&quot;$HOME/.local/bin:$PATH&quot;' &gt;&gt; ~/.bashrc
$ source ~/.bashrc</code></pre>



<figure data-wp-context="{&quot;imageId&quot;:&quot;6b029c608d251&quot;}" data-wp-interactive="core/image" data-wp-key="6b029c608d251" class="wp-block-image size-large wp-lightbox-container"><img fetchpriority="high" decoding="async" width="1024" height="576" data-wp-class--hide="state.isContentHidden" data-wp-class--show="state.isContentVisible" data-wp-init="callbacks.setButtonStyles" data-wp-on--click="actions.showLightbox" data-wp-on--load="callbacks.setButtonStyles" data-wp-on--pointerdown="actions.preloadImage" data-wp-on--pointerenter="actions.preloadImageWithDelay" data-wp-on--pointerleave="actions.cancelPreload" data-wp-on-window--resize="callbacks.setButtonStyles" src="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_-1024x576.webp" alt="Terminal showing the output of lxask --version after installation" class="wp-image-478" srcset="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_-1024x576.webp 1024w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_-300x169.webp 300w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_-768x432.webp 768w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_-1280x720.webp 1280w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-01-installation.en_.webp 1460w" sizes="(max-width: 781px) 100vw, 680px" /><button
			class="lightbox-trigger"
			type="button"
			aria-haspopup="dialog"
			data-wp-bind--aria-label="state.thisImage.triggerButtonAriaLabel"
			data-wp-init="callbacks.initTriggerButton"
			data-wp-on--click="actions.showLightbox"
			data-wp-style--right="state.thisImage.buttonRight"
			data-wp-style--top="state.thisImage.buttonTop"
		>
			<svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" fill="none" viewBox="0 0 12 12">
				<path fill="#fff" d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" />
			</svg>
		</button><figcaption class="wp-element-caption">The installer is done: lxask reports its version number, along with the installed files – model, extensions, and license – in the home directory.</figcaption></figure>



<p class="wp-block-paragraph">The second neat trick, the <code>Ctrl</code>+<code>G</code> shortcut right on the command line, needs one more line in your shell configuration. Best to make that permanent in <code>~/.bashrc</code> too:</p>



<pre class="wp-block-code"><code>$ echo 'eval &quot;$(lxask --shell-init bash)&quot;' &gt;&gt; ~/.bashrc
$ source ~/.bashrc</code></pre>



<p class="wp-block-paragraph">The same goes for zsh with <code>~/.zshrc</code>; fish has its own variant.</p>



<h2 class="wp-block-heading">Everyday use</h2>



<p class="wp-block-paragraph">I started by giving lxask a few everyday tasks in plain English: finding what&#8217;s eating up disk space, searching for PDF files, checking free disk space, and unpacking an archive. Every answer came with a short explanation of the options used – handy if you don&#8217;t have every man page memorized. All four suggestions were correct and ready to run as-is:</p>



<pre class="wp-block-code"><code>$ lxask &quot;show me which folders in my home directory take up the most space&quot;
du -h --max-depth=1 &quot;$HOME&quot; | sort -hr
$ lxask &quot;find all PDF files in my Downloads folder&quot;
find &quot;$HOME/Downloads&quot; -type f -name '*.pdf'
$ lxask &quot;how much space is left on the drive&quot;
df -h
$ lxask &quot;extract archive.tar.gz here in this folder&quot;
tar -xzf archive.tar.gz</code></pre>



<figure data-wp-context="{&quot;imageId&quot;:&quot;6b029c608dd28&quot;}" data-wp-interactive="core/image" data-wp-key="6b029c608dd28" class="wp-block-image size-large wp-lightbox-container"><img decoding="async" width="1024" height="576" data-wp-class--hide="state.isContentHidden" data-wp-class--show="state.isContentVisible" data-wp-init="callbacks.setButtonStyles" data-wp-on--click="actions.showLightbox" data-wp-on--load="callbacks.setButtonStyles" data-wp-on--pointerdown="actions.preloadImage" data-wp-on--pointerenter="actions.preloadImageWithDelay" data-wp-on--pointerleave="actions.cancelPreload" data-wp-on-window--resize="callbacks.setButtonStyles" src="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_-1024x576.webp" alt="Terminal with four lxask requests in English and the suggested commands" class="wp-image-479" srcset="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_-1024x576.webp 1024w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_-300x169.webp 300w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_-768x432.webp 768w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_-1280x720.webp 1280w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-02-alltag.en_.webp 1460w" sizes="(max-width: 781px) 100vw, 680px" /><button
			class="lightbox-trigger"
			type="button"
			aria-haspopup="dialog"
			data-wp-bind--aria-label="state.thisImage.triggerButtonAriaLabel"
			data-wp-init="callbacks.initTriggerButton"
			data-wp-on--click="actions.showLightbox"
			data-wp-style--right="state.thisImage.buttonRight"
			data-wp-style--top="state.thisImage.buttonTop"
		>
			<svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" fill="none" viewBox="0 0 12 12">
				<path fill="#fff" d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" />
			</svg>
		</button><figcaption class="wp-element-caption">Four everyday requests to lxask in the terminal: each prompt is shown above its answer, with the suggested command and an explanation of its options below.</figcaption></figure>



<p class="wp-block-paragraph">The first answer after installation took around 4.7 seconds on my machine, since the model still had to load. After that it stays in memory, and further answers came back in about 2 seconds – so the numbers from the project description check out. Even more convenient is <code>Ctrl</code>+<code>G</code>: you type your question right on the command line, hit the shortcut, and lxask swaps it for the matching command. If you&#8217;re upgrading your shell anyway, <a href="https://linuxundich.de/en/search-bash-history-hstr-fzf-atuin-mcfly/">my comparison of hstr, fzf, Atuin, and McFly</a> rounds up the right helpers for your command history.</p>



<figure data-wp-context="{&quot;imageId&quot;:&quot;6b029c608e775&quot;}" data-wp-interactive="core/image" data-wp-key="6b029c608e775" class="wp-block-image size-large wp-lightbox-container"><img decoding="async" width="1024" height="576" data-wp-class--hide="state.isContentHidden" data-wp-class--show="state.isContentVisible" data-wp-init="callbacks.setButtonStyles" data-wp-on--click="actions.showLightbox" data-wp-on--load="callbacks.setButtonStyles" data-wp-on--pointerdown="actions.preloadImage" data-wp-on--pointerenter="actions.preloadImageWithDelay" data-wp-on--pointerleave="actions.cancelPreload" data-wp-on-window--resize="callbacks.setButtonStyles" src="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_-1024x576.webp" alt="Terminal showing the Ctrl+G shortcut replacing a typed request with the matching command" class="wp-image-480" srcset="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_-1024x576.webp 1024w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_-300x169.webp 300w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_-768x432.webp 768w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_-1280x720.webp 1280w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-03-strg-g.en_.webp 1360w" sizes="(max-width: 781px) 100vw, 680px" /><button
			class="lightbox-trigger"
			type="button"
			aria-haspopup="dialog"
			data-wp-bind--aria-label="state.thisImage.triggerButtonAriaLabel"
			data-wp-init="callbacks.initTriggerButton"
			data-wp-on--click="actions.showLightbox"
			data-wp-style--right="state.thisImage.buttonRight"
			data-wp-style--top="state.thisImage.buttonTop"
		>
			<svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" fill="none" viewBox="0 0 12 12">
				<path fill="#fff" d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" />
			</svg>
		</button><figcaption class="wp-element-caption">Ctrl+G on the command line: the typed question above has been replaced by the finished command, ready to confirm with Enter.</figcaption></figure>



<p class="wp-block-paragraph"><code>--explain</code> goes the other way: if you&#8217;ve got a command from a forum post or your own shell history in front of you, lxask breaks it down into its parts:</p>



<pre class="wp-block-code"><code>$ lxask --explain &quot;tar -xzvf archive.tar.gz&quot;</code></pre>



<p class="wp-block-paragraph">For this, lxask doesn&#8217;t load the language model at all – the explanation showed up in my terminal after about 0.05 seconds. If you want to understand a command you copied from somewhere before you run it, this is a handy complement to the actual translation feature – and the explanations come from man pages and tldr, not from the model.</p>



<figure data-wp-context="{&quot;imageId&quot;:&quot;6b029c608f544&quot;}" data-wp-interactive="core/image" data-wp-key="6b029c608f544" class="wp-block-image size-large wp-lightbox-container"><img loading="lazy" decoding="async" width="1024" height="576" data-wp-class--hide="state.isContentHidden" data-wp-class--show="state.isContentVisible" data-wp-init="callbacks.setButtonStyles" data-wp-on--click="actions.showLightbox" data-wp-on--load="callbacks.setButtonStyles" data-wp-on--pointerdown="actions.preloadImage" data-wp-on--pointerenter="actions.preloadImageWithDelay" data-wp-on--pointerleave="actions.cancelPreload" data-wp-on-window--resize="callbacks.setButtonStyles" src="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_-1024x576.webp" alt="Terminal showing the output of lxask --explain for an existing tar command" class="wp-image-481" srcset="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_-1024x576.webp 1024w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_-300x169.webp 300w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_-768x432.webp 768w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_-1280x720.webp 1280w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-04-explain.en_.webp 1360w" sizes="auto, (max-width: 781px) 100vw, 680px" /><button
			class="lightbox-trigger"
			type="button"
			aria-haspopup="dialog"
			data-wp-bind--aria-label="state.thisImage.triggerButtonAriaLabel"
			data-wp-init="callbacks.initTriggerButton"
			data-wp-on--click="actions.showLightbox"
			data-wp-style--right="state.thisImage.buttonRight"
			data-wp-style--top="state.thisImage.buttonTop"
		>
			<svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" fill="none" viewBox="0 0 12 12">
				<path fill="#fff" d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" />
			</svg>
		</button><figcaption class="wp-element-caption">lxask &#8211;explain breaks an existing tar command down into its options and explains each one individually, without loading the language model.</figcaption></figure>



<h2 class="wp-block-heading">Where it struggles</h2>



<p class="wp-block-paragraph">According to the project description, lxask is supposed to ask follow-up questions for vague requests and flag uncertain answers. I tried that with four deliberately tricky prompts, and every one of them went wrong in its own way. &#8220;Clean this up&#8221; got no follow-up question at all – just <code>git clean --dry-run</code>, quietly assuming a Git repository nobody mentioned. Asking it to find large files &#8220;without using find&#8221; did avoid find this time, but the replacement doesn&#8217;t actually work:</p>



<pre class="wp-block-code"><code>$ lxask &quot;clean this up&quot;
git clean --dry-run
$ lxask &quot;find all files larger than 100 megabytes, but do not use find for it&quot;
ls --sort=size -1 | awk '$1 &gt; 100*1024*1024 {print}'</code></pre>



<figure data-wp-context="{&quot;imageId&quot;:&quot;6b029c608fe67&quot;}" data-wp-interactive="core/image" data-wp-key="6b029c608fe67" class="wp-block-image size-large wp-lightbox-container"><img loading="lazy" decoding="async" width="1024" height="576" data-wp-class--hide="state.isContentHidden" data-wp-class--show="state.isContentVisible" data-wp-init="callbacks.setButtonStyles" data-wp-on--click="actions.showLightbox" data-wp-on--load="callbacks.setButtonStyles" data-wp-on--pointerdown="actions.preloadImage" data-wp-on--pointerenter="actions.preloadImageWithDelay" data-wp-on--pointerleave="actions.cancelPreload" data-wp-on-window--resize="callbacks.setButtonStyles" src="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_-1024x576.webp" alt="Terminal showing a vague request and a request whose suggested fix doesn't hold up" class="wp-image-482" srcset="https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_-1024x576.webp 1024w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_-300x169.webp 300w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_-768x432.webp 768w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_-1280x720.webp 1280w, https://linuxundich.de/en/wp-content/uploads/2026/11/lxask-05-grenzen.en_.webp 1460w" sizes="auto, (max-width: 781px) 100vw, 680px" /><button
			class="lightbox-trigger"
			type="button"
			aria-haspopup="dialog"
			data-wp-bind--aria-label="state.thisImage.triggerButtonAriaLabel"
			data-wp-init="callbacks.initTriggerButton"
			data-wp-on--click="actions.showLightbox"
			data-wp-style--right="state.thisImage.buttonRight"
			data-wp-style--top="state.thisImage.buttonTop"
		>
			<svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" fill="none" viewBox="0 0 12 12">
				<path fill="#fff" d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" />
			</svg>
		</button><figcaption class="wp-element-caption">Two edge cases in the terminal: a vague request answered with a Git command out of nowhere, and a size-limit request whose replacement command doesn&#8217;t actually work.</figcaption></figure>



<p class="wp-block-paragraph">Plain <code>ls -1</code> doesn&#8217;t print file sizes, so the <code>awk</code> condition never actually fires. For a made-up task (&#8220;turn off airplane mode on my server&#8221;), lxask suggested <code>sudo nmcli radio wifi off</code>– a real command this time, but one that only switches off Wi-Fi, not airplane mode as a whole, and servers rarely have a radio to turn off to begin with. Sorting processes by GPU usage produced an invented <code>ps</code> column yet again. None of these answers came with any kind of uncertainty flag. So, as with any AI tool: read the suggestion before you run it. If you&#8217;d rather skip the AI altogether, The Fuck fixes mistyped commands after you&#8217;ve already hit enter.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">lxask shows that a small local model is enough for Linux commands, as long as the tasks come from everyday life: finding disk space, searching for files, unpacking archives. That worked for me without a graphics card, without a network connection, and with answers in about two seconds. That&#8217;s exactly what makes it interesting for anyone who doesn&#8217;t have a 3,000-euro machine under their desk but still doesn&#8217;t want to send their commands to the cloud.</p>



<p class="wp-block-paragraph">Still, you shouldn&#8217;t trust lxask blindly. With vague or unusual requests, it makes up commands and options without warning you. If you know your way around a shell and give the suggestion a quick read, <code>Ctrl</code>+<code>G</code> and <code>--explain</code> make for a fast helper. For newcomers especially, <code>--explain</code> is a real win, since its explanations come straight from the man pages.</p>
<hr><p>☕ <strong>Support Linux und Ich</strong><br>Thanks for reading <a href="https://linuxundich.de/en/">Linux und Ich</a>. If you enjoy the blog and would like to support my work, you will find more information on the <a href="https://linuxundich.de/en/support/">donation page</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://linuxundich.de/en/lxask-offline-ai-linux-commands/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
