Show HN: Wut – a CLI that explains the output of your last command with an LLM • Hacker News Board

Show HN: Wut – a CLI that explains the output of your last command with an LLM

#1

Post by jshobrook » Thu, Dec 19, 2024, 4:05 PM UTC

Just type wut and an LLM will explain whatever's in your terminal. You’ll be surprised how useful this is. I use it mainly to understand and debug stack traces, but there are a bunch of other use cases:

- Deciphering error codes

- Fixing incorrect commands

- Summarizing logs

You can connect wut to OpenAI, Anthropic, or a local model via Ollama.

I hope y’all find this as helpful as I do!

Show HN: Wut – a CLI that explains the output of your last command with an LLM
github.com

Re: Show HN: Wut – a CLI that explains the output of your last command with an LLM

#2

Post by jas39 » Sun, Dec 22, 2024, 9:47 PM UTC

Very useful tool. The tmux/screen requirement is a design flaw though.

Re: Show HN: Wut – a CLI that explains the output of your last command with an LLM

#3

Post by jshobrook » Sun, Jan 05, 2025, 5:24 AM UTC

jas39 wrote: post #2

Very useful tool. The tmux/screen requirement is a design flaw though.

Unfortunately, I don't see a way around it. There's no other way to capture the output buffer.

Re: Show HN: Wut – a CLI that explains the output of your last command with an LLM

#4

Post by jas39 » Fri, Jan 10, 2025, 7:23 PM UTC

jshobrook wrote: post #3

jas39 wrote: post #2

Very useful tool. The tmux/screen requirement is a design flaw though.

Unfortunately, I don't see a way around it. There's no other way to capture the output buffer.

Of course there is; tmux does it. Try redirecting the file descriptor so that you can capture stdout. For bash, something like: 'exec > >(tee -a "$LOG_FILE") 2>&1'.

This could be injected in .bashrc, and activated by default or by a bash function. The >(...) syntax is called process substitution.