sudojidocs
Getting Started

How to use Sudoji

Diagnose server errors, research official docs, and get fix steps — without leaving your terminal or browser.

What is Sudoji?

Sudoji is an AI-powered IT support assistant built for engineers managing Linux servers, cloud infra, and developer tooling. Instead of trawling Stack Overflow and vendor docs for hours, you describe the problem and Sudoji surfaces the cause and a concrete fix — often in under a minute.

There are two ways to use Sudoji: through the web chat at sudoji.io, or by installing the Sudoji Agent CLI directly on your server for hands-free log analysis and automated triage. This guide covers the web interface.

Starting a conversation

Go to /chat and describe the problem you're seeing. You don't need to phrase it perfectly — natural language works fine.

The more context you give upfront, the faster Sudoji can narrow down the cause. Include your OS, the service that's failing, and any error codes you've already seen.

Good openers:

example prompts
nginx is returning 502 on my Ubuntu 22 server, restarted it but the error persists
pm2 app keeps crashing on startup — exits with code 1, no useful logs
postgres connection pool is exhausted after deploying a new feature

Attaching context

Paste raw error messages, stack traces, log excerpts, or config snippets directly into the chat. Sudoji reads them as part of the context and uses them to give a precise diagnosis rather than a generic answer.

Useful things to paste:

  • The last 20–50 lines of the failing service's log (journalctl -u nginx -n 50)
  • The full error output including the stack trace — not just the final line
  • Your package.json, nginx.conf, or relevant config file
  • The output of systemctl status <service>
Sudoji automatically redacts secrets and credentials before sending anything to the model. Even so, avoid pasting private keys or passwords — use placeholder values instead.

Searching official documentation

Sudoji can scan vendor documentation in real time using Perplexity. This is useful when you need the exact steps from official sources rather than community guesses.

Trigger a doc search by phrasing your message with intent words like:

example prompts that trigger a documentation search
scan the official nginx docs for the steps to enable http2
look up the official postgres docs for connection pooling settings
fetch the official pm2 guide for log rotation

Keywords like scan, official docs, look up, the steps, and official guide all activate vendor doc search automatically.

Understanding the output

Sudoji structures its responses in three parts:

  • Root cause — what actually went wrong, not just what the error message says
  • Fix steps — exact commands you can copy and run, in order
  • Verification — how to confirm the fix worked

If Sudoji isn't confident, it will say so and ask a follow-up question rather than guessing. If it needs more information — like the output of a specific command — it will tell you exactly what to run and ask you to paste the result.

Tips & best practices

  • Always mention the OS and version: Ubuntu 22.04, Debian 12, CentOS 9
  • If the error is intermittent, mention frequency: "happens every few minutes under load"
  • Tell Sudoji what you've already tried — it won't repeat suggestions you've ruled out
  • Use the follow-up thread to refine: paste the output of a fix step if it didn't work
  • For recurring issues, install the Sudoji Agent CLI — it gathers context from your server automatically

Using the Sudoji Agent CLI

For deeper server access, install the @sudoji/cli package directly on your Linux server. The agent reads files, checks logs, and can execute commands with your approval — no copy-pasting required.

install
npm install -g @sudoji/cli
sudoji login        # paste your API key from Dashboard → Settings
sudoji doctor       # verify everything works

Two ways to keep the agent available

Two-terminal workflow
  1. SSH window 1: run sudoji daemon to connect the server to the portal
  2. SSH window 2: run sudoji chat to start an interactive session
  3. Both share the same thread — visible in the portal
Daemon disconnects when you close the SSH window.
PM2 background workflow (recommended)
  1. sudo npm install -g pm2
  2. pm2 start "sudoji daemon" --name sudoji-daemon
  3. pm2 save && pm2 startup # survives reboots
  4. One SSH window is enough — daemon runs in the background
Daemon stays connected even after you log out.

Interactive chat: plan before you act

sudoji chat opens a multi-turn terminal REPL. The default mode is diagnose — the agent reads files and explains what it finds but never executes commands. This makes it safe to use as a planning tool: describe what you want to do, let the agent walk through it step by step, then run the commands yourself or switch to --mode fix to let it do it.

example — plan a change
sudoji chat

  sudoji › I want to migrate from pm2 to systemd for the api process — plan it out
  [agent reads ecosystem.config.js, existing systemd units…]
  › Here's a safe migration plan:
    1. Generate a systemd unit from your pm2 config
    2. Verify the unit starts correctly
    3. Disable pm2 auto-start for the process
    4. Enable the systemd unit

  sudoji › show me the unit file it would generate
  …
You can also send messages from the portal web UI (Sessions → Chat tab) while the daemon is running. The agent handles your messages on the server and streams the response back to your browser — no terminal needed.
Next: Installing the Sudoji Agent →
How to use Sudoji — Sudoji Docs