💥 oops

Turn cryptic error messages into actionable fixes

The AI-powered error explainer and debug assistant that turns stack traces into instant solutions. Pipe any error to this stack-trace-ai analyzer for AI-powered error fixes in under 2 seconds.

Pipe any error → AI analysis → copy-paste fix. Under 2 seconds.

The Problem

Your build breaks. A 40-line stack trace stares back at you. You copy the error, open a browser, paste it into Google, click three Stack Overflow links from 2017, try two solutions that don't work, dig through GitHub issues, and finally find the fix 15 minutes later.

Meanwhile, your flow state is gone.

oops is your error message decoder: pipe cryptic errors to AI, get actionable fixes instantly, stay in the terminal, and keep coding.

Quick Start (30 seconds)

# Option 1: Use without installing (fastest)
npx oops-ai

# Option 2: Install globally
npm install -g oops-ai

# Set your API key (get one at console.anthropic.com)
export ANTHROPIC_API_KEY="sk-ant-..."

That's it. Now pipe any error:

npm run build 2>&1 | oops
python script.py 2>&1 | oops
cargo build 2>&1 | oops
docker build . 2>&1 | oops
kubectl logs pod/api-xyz 2>&1 | oops

Why 2>&1? This redirects stderr (where errors live) to stdout so oops catches everything.

Real Error Scenarios: Before → After

1. `ENOENT: no such file or directory`

Before 😩

$ npm run dev
Error: ENOENT: no such file or directory, 
open '/Users/dev/app/config/database.json'
    at Object.openSync (node:fs:603:3)
    at Object.readFileSync (node:fs:471:35)
    at loadConfig (/app/server.js:12:18)
    ... 18 more lines ...

*Google: "ENOENT error node"*
*Stack Overflow: "What is ENOENT?"*
*15 minutes later: finally check if file exists*

After ⚡

$ npm run dev 2>&1 | oops

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Problem: File not found
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Missing: config/database.json

Solution:
  1. Create the file:
     $ mkdir -p config
     $ touch config/database.json
  
  2. Or check path typo in server.js:12

Why: ENOENT = Error NO ENTry (file doesn't exist)

Done. 0.9s ✓

2. `EADDRINUSE: address already in use`

Before 😩

$ npm start
Error: listen EADDRINUSE: address already in use :::3000
    at Server.setupListenHandle [as _listen2] (node:net:1380:16)
    at listenInCluster (node:net:1428:12)
    at Server.listen (node:net:1515:7)
    ... 12 more lines ...

*Google: "port 3000 already in use"*
*Try: lsof -i :3000 (what does this do?)*
*Copy PID, kill, restart*
*5 minutes of trial and error*

After ⚡

$ npm start 2>&1 | oops

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Problem: Port 3000 already in use
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Another process is using port 3000

Solution:
  # Option 1: Kill the process
  $ lsof -ti :3000 | xargs kill -9

  # Option 2: Use a different port
  $ PORT=3001 npm start

Pro tip: Install portguard to avoid this:
  $ npx portguard 3000

Done. 0.7s ✓

3. `Cannot find module 'xyz'`

Before 😩

$ node server.js
Error: Cannot find module 'express'
Require stack:
- /Users/dev/app/server.js
- /Users/dev/app/index.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Function.Module._load (node:internal/modules/cjs/loader:920:27)
    ... 22 more lines ...

*Google: "Cannot find module express"*
*Stack Overflow: "Did you npm install?"*
*Me: "I thought I did..."*
*Checks package.json, missing dependency*
*3 minutes wasted*

After ⚡

$ node server.js 2>&1 | oops

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Problem: Missing npm package
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

'express' is not installed

Solution:
  $ npm install express

If it's a dev dependency:
  $ npm install --save-dev express

Why: Node can't find the module because 
it's not in node_modules/

Done. 0.6s ✓

4. `Permission denied (EACCES)`

Before 😩

$ npm install -g typescript
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/lib/node_modules/typescript
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/typescript'
npm ERR! [Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/typescript'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: '/usr/local/lib/node_modules/typescript'
npm ERR! }

*Google: "npm EACCES permission denied"*
*Stack Overflow: "Use sudo" (risky!)*
*Another answer: "Fix npm permissions" (how?)*
*10 minutes of frustration*

After ⚡

$ npm install -g typescript 2>&1 | oops

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Problem: Permission denied (npm global)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Can't write to /usr/local/lib/node_modules

Solution (safe):
  # Fix npm permissions once
  $ mkdir ~/.npm-global
  $ npm config set prefix '~/.npm-global'
  $ echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.zshrc
  $ source ~/.zshrc
  
  # Then retry
  $ npm install -g typescript

⚠️  Don't use sudo! It creates permission issues.

Done. 1.1s ✓

5. `Uncaught ReferenceError: x is not defined`

Before 😩

$ node app.js
/Users/dev/app.js:42
  console.log(userData);
              ^
ReferenceError: userData is not defined
    at processUser (/Users/dev/app.js:42:15)
    at main (/Users/dev/app.js:78:3)
    at Object.<anonymous> (/Users/dev/app.js:85:1)
    ... 8 more lines ...

*Scroll through 200 lines of code*
*Find typo: used userData instead of userdata*
*Could've been caught with a linter*
*7 minutes of debugging*

After ⚡

$ node app.js 2>&1 | oops

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Problem: Variable not defined
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

'userData' doesn't exist at line 42

Common causes:
  1. Typo in variable name
  2. Missing variable declaration
  3. Wrong scope (var/let/const)

Solution:
  Check app.js:42
  
  // If it's a typo:
  const userData = ...  // Define it
  
  // Or check nearby lines for similar names:
  - userdata
  - user_data
  - userInfo

Pro tip: Use ESLint to catch this before runtime:
  $ npx eslint app.js

Done. 0.8s ✓

More Examples

Rust Borrow Checker

$ cargo build 2>&1 | oops

Problem: Cannot borrow `users` as mutable while borrowed as immutable

Solution: Limit the lifetime of the immutable borrow

  let first_name = users[0].name.clone();
  users.push(new_user);     // Now OK
  println!("{}", first_name);

Docker Build Failure

$ docker build -t myapp . 2>&1 | oops

Problem: Dockerfile parse error - unexpected EOF at line 12

Solution: Missing backslash in multi-line RUN command

  RUN apt-get update && \
      apt-get install -y curl

Git Push Rejected

$ git push origin main 2>&1 | oops

Problem: Remote contains commits you don't have locally

Solution:
  $ git pull --rebase origin main
  $ git push origin main

Kubernetes Pod Crash

$ kubectl logs pod/api-7d9f8b-xk2m 2>&1 | oops

Problem: ECONNREFUSED 10.0.0.5:5432 — Can't reach PostgreSQL

Solution:
  1. Check DB service: kubectl get svc postgres-service
  2. Verify DB_HOST env var in deployment
  3. Test: kubectl run debug --image=postgres:15 ...

Why `oops` Beats Alternatives

vs Google Search 🔍

Google: Copy error → open browser → paste → click 3 links → try 2 wrong answers → find fix (5+ minutes)
oops: Pipe error → get fix (< 2 seconds)

Winner: oops (150x faster)

vs Stack Overflow 📚

Stack Overflow: Answers from 2017, language version mismatches, no project context
oops: Current AI model trained on latest docs, adapts to your specific error

Winner: oops (accurate + fresh)

vs ChatGPT 🤖

ChatGPT: Copy error → switch to browser → paste → wait 30s → copy solution → switch back to terminal
oops: Never leave the terminal

Winner: oops (native terminal workflow)

`oops` Advantages

✅ AI-powered instant analysis (Claude Sonnet 4.5)
✅ Project context aware (detects language, framework, error type)
✅ Terminal-native (pipe → fix, no browser)
✅ ~$0.003 per query (99% cheaper than 15 min of dev time)

Use Cases

1. Stay in Flow During Development

Don't break focus hunting for fixes. Pipe the error, get the solution, keep coding.

npm test 2>&1 | oops

2. Onboard Junior Developers Faster

New to the codebase? Don't Slack teammates for every error. Pipe it to oops first.

npm run build 2>&1 | oops  # Instant learning

3. Debug Production CI/CD Failures

Build broke at 3am? No time to Google. Pipe the logs, ship the fix.

# GitHub Actions / GitLab CI logs
cat build.log | oops

4. Learn New Languages

Rust borrow checker cryptic? Go interfaces confusing? oops explains while you learn.

cargo build 2>&1 | oops   # "Oh, THAT'S why it won't compile"

5. Pre-Commit Sanity Check

Catch errors before pushing broken code to main.

npm test 2>&1 | oops || exit 1  # Git pre-commit hook

How It Works

Reads error from stdin (your failed command's output)
Auto-detects context (language, framework, error type)
Sends to Claude AI for analysis (~0.5–1.5s)
Returns concise fix (copy-paste ready)

Privacy note: Error text is sent to Anthropic's API. Don't pipe secrets (API keys, passwords, tokens).

Supported Languages & Tools

JavaScript · TypeScript · Python · Go · Rust · Java · C/C++ · Ruby · PHP · Docker · Kubernetes · Git · Shell · PostgreSQL · MySQL · npm · pip · cargo · and more

If it outputs an error, oops can decode it.

Options

-v, --verbose    Detailed analysis with multiple approaches
--no-color       Disable colored output
-V, --version    Show version
-h, --help       Show help

Pro Tips

Shell Aliases for Speed

# Add to ~/.zshrc or ~/.bashrc
alias oops-build='npm run build 2>&1 | oops'
alias oops-test='npm test 2>&1 | oops'
alias oops-start='npm start 2>&1 | oops'

Trim Huge Logs

Docker builds spitting 10,000 lines? Trim for faster analysis:

docker build . 2>&1 | tail -100 | oops

Save Solutions for Later

npm run build 2>&1 | oops > solution.txt

Git Pre-Commit Hook

# .git/hooks/pre-commit
npm test 2>&1 | oops || exit 1

Kubernetes Debug Helper

# Add to ~/.zshrc
k8s-debug() {
  kubectl logs "$1" 2>&1 | oops
}

# Usage:
k8s-debug pod/api-7d9f8b-xk2m

Requirements

Node.js 18+ (check with node --version)
Anthropic API key (get one here)

export ANTHROPIC_API_KEY="sk-ant-..."  # Add to ~/.zshrc to persist

Also From MUIN

Love oops? Check out our other developer CLI tools:

roast-cli — AI code reviews with Gordon Ramsay energy. Get brutally honest feedback before errors even happen.
git-why — AI-powered git history explainer. Understand why that buggy code exists before you fix it.
portguard — Monitor and kill zombie processes hogging your ports. Fix the EADDRINUSE before you even need oops.

Featured On

Read the launch article on Dev.to: 4 CLI Tools Every Developer Needs (That You've Never Heard Of)

License

MIT © MUIN

Built by MUIN — 일하는 AI, 누리는 인간

💥 Stop Googling errors. Pipe them to AI instead.

npm · GitHub · Dev.to Article

Name		Name	Last commit message	Last commit date
Latest commit History 25 Commits
bin		bin
examples		examples
lib		lib
.gitignore		.gitignore
.npmignore		.npmignore
COMPLETION-REPORT.md		COMPLETION-REPORT.md
CONTRIBUTING.md		CONTRIBUTING.md
DEMO.md		DEMO.md
LICENSE		LICENSE
PROJECT-SUMMARY.md		PROJECT-SUMMARY.md
QUICKSTART.md		QUICKSTART.md
README.md		README.md
VISUAL-DEMO.md		VISUAL-DEMO.md
demo.gif		demo.gif
package-lock.json		package-lock.json
package.json		package.json
test.js		test.js

Folders and files

Latest commit

History

Repository files navigation

💥 oops

The Problem

Quick Start (30 seconds)

Real Error Scenarios: Before → After

1. ENOENT: no such file or directory

2. EADDRINUSE: address already in use

3. Cannot find module 'xyz'

4. Permission denied (EACCES)

5. Uncaught ReferenceError: x is not defined

More Examples

Rust Borrow Checker

Docker Build Failure

Git Push Rejected

Kubernetes Pod Crash

Why oops Beats Alternatives

vs Google Search 🔍

vs Stack Overflow 📚

vs ChatGPT 🤖

oops Advantages

Use Cases

1. Stay in Flow During Development

2. Onboard Junior Developers Faster

3. Debug Production CI/CD Failures

4. Learn New Languages

5. Pre-Commit Sanity Check

How It Works

Supported Languages & Tools

Options

Pro Tips

Shell Aliases for Speed

Trim Huge Logs

Save Solutions for Later

Git Pre-Commit Hook

Kubernetes Debug Helper

Requirements

Also From MUIN

Featured On

License

About

Topics

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

1. `ENOENT: no such file or directory`

2. `EADDRINUSE: address already in use`

3. `Cannot find module 'xyz'`

4. `Permission denied (EACCES)`

5. `Uncaught ReferenceError: x is not defined`

Why `oops` Beats Alternatives

`oops` Advantages

Packages