I think the point isn&#x27;t what the author knows or does not know but rather a question for the rest of us - what does this tool offer that bash history doesn&#x27;t?The list of features on the Github page doesn&#x27;t provide an answer:- Starts and stops on demand: Only logs commands when you explicitly turn it on.- Saves to a custom file: You can specify the log file name.- Cross-platform: Works on both Linux and macOS using bash or zsh.- Minimal overhead: Runs in the background and has no noticeable impact on shell performance.Bash largely covers all of those too.

...is this program just copying lines from shell history inti a different file?

The readme uses history so surely the author knows this?<pre><code> function preexec_go() {
 local command_line=$(history 1 | sed &#x27;s&#x2F;^ *[0-9]* *&#x2F;&#x2F;&#x27;)
 if [[ -n &quot;$command_line&quot; &amp;&amp; &quot;$command_line&quot; != &quot;preexec_go&quot; ]]; then
 # CHANGE THIS PATH to the location of your &#x27;envoy&#x27; executable
 ( 
 ~&#x2F;Desktop&#x2F;projects&#x2F;envoy&#x2F;envoy &quot;$command_line&quot; &gt;&#x2F;dev&#x2F;null 2&gt;&amp;1 &amp; ) disown
 fi
 }
 trap &#x27;preexec_go&#x27; DEBUG</code></pre>

I&#x27;m confused: doesn&#x27;t bash already log all commands in it&#x27;s history file?

Well this one looks like AI slop, so..

How does this differ from Atuin? <a href="https:&#x2F;&#x2F;atuin.sh" rel="nofollow">https:&#x2F;&#x2F;atuin.sh</a>

Not at my computer so I cannot share the sauce, but each mahcine I use has a shared bash eternal history - shared between every interactive bash instance on that machine, using nothing but bashisms.If I think of it later, I&#x27;ll add it....

Then you should look at <a href="https:&#x2F;&#x2F;atuin.sh&#x2F;" rel="nofollow">https:&#x2F;&#x2F;atuin.sh&#x2F;</a> although I am not certain about exit code.

The godoc on logging.go is in the &quot;AI style&quot; rather than in the style of a typical godoc.

Comments on every other line stating what the line does is very LLM

Why do you suspect it was vibe coded? There are 2 substantive files that are each less than 100 lines...Also the readme doesn&#x27;t have the usual emojis for every bullet point.

In charity, I think there is actually a product opportunity for improvements to the standard shell histfile.I&#x27;ve often been frustrated by my history not being easily shared between concurrent terminals, difficulties in searching, and lack of other metadata such as timestamp, duration and exit code.Although I suspect this repo was vibe-coded so far, I think there&#x27;s a promising problem to solve here.

Envoy is a lightweight, background utility that logs your terminal commands. It&#x27;s designed to be a simple and unobtrusive way to keep a history of your shell usage, which can be useful for debugging, tracking work, or just remembering what you did.

Show HN: Envoy – Command Logger