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.
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.
