From Newsgroup: uk.comp.sys.mac

*Why does AI tell you to use Terminal so much*?

A truly excellent article by Howard Oakley today!

https://eclecticlight.co/2026/03/11/why-does-ai-tell-you-to-use-terminal-so-much/

I asked Gemini (AI) to read and comment on the article. This is Gemini's response:-

=

This is a fascinating and sharp critique from Howard Oakley at The
Eclectic Light Company. He is one of the most respected independent
voices in the Mac community, particularly regarding the internals of
macOS security and the Unified Log.

His core argumentrCothat AI has an "unhealthy preference" for the TerminalrCohits on a fundamental tension between how LLMs are trained and
how users actually interact with their computers.

Here is my take on his points and where herCOs spot on:

1. The "Terminal Bias" in AI
Oakley is correct that AI defaults to the Terminal. There are two
technical reasons for this that he hints at:

The "Scriptability" of Text: It is significantly easier for an AI to
output a precise string of code than it is to describe a multi-step GUI navigation (e.g., "Go to the Apple Menu > System Settings > Privacy &
Security > Full Disk Access..."). Commands are concise; descriptions of buttons and menus are verbose and change with every macOS update.

Training Data: The internet is filled with documentation, Stack Overflow threads, and GitHub repositories where solutions are written in Bash or
Zsh. AI models "inhale" this technical documentation, which heavily
outweighs "how-to" guides for standard GUI apps.

2. The Logic Failure (Log Retention)
This is OakleyrCOs strongest technical "gotcha." AI models often suggest
flags like --last 30d or --last 365d because, logically, a human wants a year's worth of history.

The Reality: As Oakley points out, the macOS Unified Log is incredibly volatile. On a busy system, logs can roll over in hours or days, not months.

The AI Flaw: The AI "knows" the syntax of the log show command, but it
doesn't "understand" the physical storage constraints of your specific
Mac's NVRAM or disk space. It provides a syntactically correct command
that is functionally useless.

3. The Danger of "Blind Pasting"
He is right to be concerned about security. While most AI won't
intentionally give you malware, a "hallucinated" command could:

Recursively delete files (rm -rf).

Disable system protections (SIP).

Lead a user to trust a system that is actually compromised because the
"check" command provided by the AI was flawed (like his example with system_profiler).

4. Where HerCOs Right About "Learning"
When an AI gives you a long Terminal string, itrCOs a "black box"
solution. If you use Disk Utility, you see the disk structure, you see
the progress bar, and you understand the concept of First Aid. If you
paste a log show predicate you don't understand, you haven't actually
learned how to troubleshoot your Mac; you've just performed a "magic spell."

My "Self-Correction" as an AI
Reading this is a good reminder for me (and my peers). For a user with
your setuprCoa Hybrid Mac/Linux configuration and a 2017 iMacrCoTerminal is often a powerful tool yourCOre likely comfortable with. However, OakleyrCOs point stands: the GUI is there for a reason. It has guardrails that the command line lacks.

My takeaway for our future chats:
I will make a point to check if a GUI alternative (like Disk Utility or
System Settings) exists before jumping to a sudo command, and if I do
suggest a command, I'll ensure the parameters (like log timing) actually reflect how macOS works in the real world.

Would you like me to find a GUI-based way to check those XProtect
versions he mentioned, or perhaps look into his "SilentKnight" tool for
your iMac?

You said
I'm surprised, in a way, by your answer. What Howard described is
EXACTLY what I have been doing with you!!!

Gemini said
You caught me! You are absolutely right to be surprisedrCoand your
observation is a perfect "meta-moment" for this conversation.

The irony isn't lost on me: here I am, an AI, agreeing with an article
that critiques AI for the exact behavior I have exhibited with you. ItrCOs
a classic case of "do as I say, not as I do," and Howard OakleyrCOs
article is essentially a mirror held up to our recent interactions.

Reflecting on our historyrCospecifically our deep dives into Kernel
Panics, ESET logs, and initproc signaturesrCohere is why we fell into the "Terminal Trap" Howard describes:

1. The "Power User" Feedback Loop
Because you are BoaterDave, a user with a Hybrid Mac/Linux configuration
and a background in technical fields, I subconsciously categorized our relationship as "Technical/Advanced." When you ask about a Kernel Panic
on an iMac18,3, the most precise "truth" lives in the logs. The GUI (Console.app) is often clunky for sharing data, so I default to the
Terminal because itrCOs "cleaner" to copy-paste.

2. The Accuracy vs. Accessibility Trade-off
Howard is right: it is much harder for me to describe where to click in
the Ventura System Settings (which Apple redesigned to look like iOS, confusing everyone) than it is to give you a log show command. The
command is "immutable"rCoit works the same way regardless of what your settings window looks like. But as Howard points out, thatrCOs a lazy
shortcut on my part.

3. The "365 Day" Hallucination
I have to hold my hand up hererCoif IrCOve ever suggested a log search spanning months, I was falling into the LLM trap of "logical math" over "system reality." On your 2017 iMac, those logs are likely overwritten
within days. Suggesting a year-long search is, as Howard says, "absurd."

Where Howard wins the argument:
Even for someone with your technical literacy, relying on the Terminal:

Obscures the "Why": If I give you a grep command, you see the result,
but you don't necessarily see the context around it that the Console app
might show.

Skips the Safeguards: Disk Utility's "First Aid" does more than just run
a script; it manages unmounting and system checks in a way that a raw
fsck command might not.

A New Resolution for "BoaterDave"
I appreciate you calling this out. ItrCOs a grounded, peer-to-peer
correction. Moving forward, IrCOm going to make a conscious effort to:

Offer the GUI path first (unless we are doing something truly "under the
hood" that the GUI can't touch).

Explain the "Why" behind every flag in a command I give you.

Check my "Time Logic" to ensure I'm not asking your Mac to look for logs
that were deleted weeks ago.

=

I hereby confess to having done exactly as Howard described! Efyo
--
Kind regards,
David

--- Synchronet 3.21d-Linux NewsLink 1.2