DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run the agent 24/7 on a VPS with health checks with Noraz Agent

Deploy the PM2 daemon, check diagnostics, and update the agent on a Linux server.

  • Money
  • Advanced
  • 90 minutes
  • From the README
  • Any agent

Who it is forA developer or operator who wants the bot to keep screening markets around the clock on a Linux VPS.

The problemA bot that stops when a terminal closes misses signals, and manual updates and restarts are easy to forget.

The outcomeA PM2-managed daemon that stays up, a diagnostic report from doctor, and a self-update path with deployment notifications.

What you need first

  • Node.js and npm installed
  • Git installed to clone the repository
  • API keys and chat credentials for the onboarding wizard (for example Discord or Telegram setup)
  • Familiarity with a terminal on Windows, Linux, or macOS

Steps

  1. Complete the Linux or VPS setup with bash setup.sh, then run noraz onboard to create the .env file.
  2. Run noraz deploy (or npm run deploy) to start the PM2 24/7 daemon.
  3. Run noraz doctor to check the full set of diagnostics.
  4. Run npx pm2 status and npx pm2 logs noraz-agent to confirm the daemon is up and reading logs.
  5. Run noraz update to pull the latest code, install, build, and restart PM2 with deployment notifications.

Prompt for your agent

Using the noraz-agent repo on a Linux VPS, run `noraz deploy` and then `noraz doctor`. Expected output: PM2 shows noraz-agent as online and the doctor report lists no failed checks. Verify the result with `npx pm2 status` before reporting success.

Caveat. The README describes the self-updater as pulling from git and restarting PM2, so review changes before updating a server that holds live API keys.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page