Sentient Stderr

31 CLI tools that read your system's vitals and respond with existential dread, bad poetry, and unsolicited judgment.

⚠️ DISCLAIMER

WARNING: These tools are designed for entertainment purposes and contain "unhinged" humor. They may deliver savage judgments, provoke existential dread, or make you question your career choices.

• HR Notice: Running these in a professional environment is at your own risk.
• Side Effects: May cause spontaneous laughter, mild paranoia, or a sudden urge to refactor everything.
• Production Safety: All tools are read-only and non-destructive. The drama is 100% theatrical.

How This Happened

It started, as most bad ideas do, at 2am staring at Wireshark.

SYN floods have this visual pattern in packet capture: these rhythmic bursts, almost like breathing. And I thought: that looks like a Rorschach test. And then I thought: what if your network traffic could tell you something about yourself? And then I thought: what if it was wrong, but confidently wrong?

That was packet-portrait. Then the recipe became obvious:

1. Start with a real system thing (logs, processes, network packets)
2. Ask "what if this had a personality disorder?"
3. Mix in whatever you're currently obsessed with (geopolitics, crypto, philosophy, making things)
4. Season with technical plausibility: it has to actually build in Go

The Tools

Example Output

digital-twin, because your twin is disappointed:

────────────────────────────────────────
  DIGITAL-TWIN v0.2.0
────────────────────────────────────────
  Source: /Users/charlie/.zsh_history
  Commands analyzed: 500
────────────────────────────────────────
  navigation   42.0% ████████
  git          28.4% █████
  editor       15.2% ███
  network       8.0% █
────────────────────────────────────────
  Personality: Vibe-Based Developer
  You code like someone parallel parking a bus.
────────────────────────────────────────
  73% of your commands are after 10 PM. This is not dedication. 
  This is a sleep disorder.
────────────────────────────────────────
  42% navigation. You are lost in your own filesystem. 
  Your twin knows the way.
────────────────────────────────────────

standup-excuse, for the daily sync you didn't prepare for:

────────────────────────────────────────
  STANDUP EXCUSE v0.1.0
────────────────────────────────────────
  Yesterday: Spent 4 hours on a CSS issue. The fix was display: flex. 
             I have a master's degree.
  Today: Working on the same ticket as last sprint. It's a relationship now.
  Blockers: My IDE keeps suggesting I delete everything. It might be right.
────────────────────────────────────────

cron-horoscope, your workplace prophecy:

╔══════════════════════════════════════════════════╗
║                 CRON HOROSCOPE v0.2.0            ║
╠══════════════════════════════════════════════════╣
║  Date: Thursday, Feb 26 2026                     ║
║  Sign: Pisces                                    ║
╠══════════════════════════════════════════════════╣
║  Dreams and reality blur. Much like your staging ║
║  and production environments.                    ║
║  Prophecy: A colleague will say 'let's take this ║
║  offline' and you will never speak again.        ║
╠══════════════════════════════════════════════════╣
║  Lucky Port: 5432                                ║
║  Unlucky Command: rm -rf                         ║
║  Romance: You and your IDE: codependent.         ║
╠══════════════════════════════════════════════════╣
║  Thursday: close enough to Friday to feel the    ║
║  danger.                                         ║
╚══════════════════════════════════════════════════╝

"Things These Tools Have Said" (Hall of Fame)

• "You run a backup every 5 minutes. Trust issues." — sudo-therapist
• "Your node_modules weighs more than your career prospects." — dependency-horoscope
• "You typed 'ls' 84 times. You know the files haven't moved." — exit-interview
• "Thrilled to announce I deleted 200 lines of code today. Disruption is my love language." — linkedin-sigma
• "The intern will mass-ask a question that reveals you also don't understand it." — cron-horoscope

Use With AI Assistants

These tools were not designed for AI assistants. They are perfect for AI assistants.

If you're building with OpenClaw - or any agent that can call shell tools - you now have 31 ways to give it opinions about your infrastructure.

Your AI assistant, by default, is polite. It says things like "CPU usage is at 94%." That's fine. That's correct. That's also deeply boring.

With Sentient Stderr, it says: "Your CPU is dissociating. This is not a metaphor."

Shell tool / action setup

Register any tool as a callable action. In OpenClaw or any agent that supports shell execution:

# openclaw tool definition
- name: system_mood
  description: Get an emotional read on current system vitals
  command: sentient-stderr cpu-whisperer

- name: standup
  description: Generate today's standup update
  command: sentient-stderr standup-excuse

- name: roast_codebase
  description: Psychoanalyze project dependencies
  command: sentient-stderr dependency-horoscope

- name: process_eulogy
  description: Write epitaphs for top RAM consumers
  command: sentient-stderr process-graveyard

Then ask your assistant: "how's the server feeling?" and receive:

Your processor is running at 91% and has entered what engineers call
"thermal throttling" and what your CPU calls "a cry for help."
Three cores are doing 94% of the work. The others have checked out.
This is a management problem.

Pipe into context

# Feed live system state into your agent's context window
sentient-stderr cpu-whisperer | openclaw chat "given this, should I be worried about tonight's deploy?"

# Morning briefing
sentient-stderr cron-horoscope && sentient-stderr standup-excuse | openclaw chat "summarize my day"

# Post-incident analysis
sentient-stderr process-graveyard | openclaw chat "write the postmortem"

MCP server

If your agent supports MCP, wrap any tool as a resource:

{
  "mcpServers": {
    "sentient-stderr": {
      "command": "bash",
      "args": ["-c", "sentient-stderr cpu-whisperer && sentient-stderr memory-haunted && sentient-stderr process-graveyard"]
    }
  }
}

Your AI now has feelings about your uptime. You did this.

Things agents have said after running these tools

• "Based on process-graveyard output, Slack is consuming 1.4GB of RAM. I recommend filing a restraining order."
• "cron-horoscope suggests your lucky port is 5432. Your Postgres is already running on 5432. This is either destiny or a misconfigured firewall."
• "The kernel confessional reports 47 unresolved sins. I cannot absolve these. That is above my pay grade."
• "Your digital twin has 61% git commands and 0% documentation commits. I have shown this to no one. Yet."

Install

Go install:

go install github.com/AUAggy/sentient-stderr/cmd/sentient-stderr@latest

Download binary from releases — one binary, all 31 tools.

Build from source:

git clone https://github.com/AUAggy/sentient-stderr
cd sentient-stderr
make build        # builds ./build/sentient-stderr
make install      # installs to $GOPATH/bin

Usage:

sentient-stderr <tool> [flags]
sentient-stderr --help          # list all tools
sentient-stderr cpu-whisperer
sentient-stderr standup-excuse
sentient-stderr digital-pet -feed

# BusyBox-style symlinks still work:
ln -s $(which sentient-stderr) ~/.local/bin/cpu-whisperer
cpu-whisperer

Architecture

Built with a focused three-layer approach that applies the wrong framework to the right data:

1. Platform Layer (internal/platform): Hard metrics extracted from the kernel's cold, indifferent heart.
2. Logic Layer (cmd/*): Where data meets personality disorders.
3. Output Layer (internal/output): Four distinct styles of aesthetic failure (Absurd, Meta, Paranormal, Unhinged).

Built in Go. Runs everywhere. Solves nothing. Deeply necessary.

AI-assisted development. The existential dread is genuine.