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

How to schedule automatic scans for new postings with Pinloop CLI

Set a Pro routine that saves new matching postings on Pinloop's servers.

Who it is forAn active job seeker who wants new matching postings saved for them without rerunning searches each day.

The problemChecking job boards by hand every day is slow, and a laptop must stay on for local scripts to run.

The outcomeMatching postings are scanned and saved automatically on a schedule or as new postings arrive, even when your laptop is closed.

What you need first

  • Node 22 or newer
  • A coding agent such as Claude Code, Codex, or Cursor
  • A Pinloop account, created with `pinloop login` through a browser (no password)
  • Your resume and any preference files, if you want postings judged against them

Steps

  1. Run npm install -g pinloop (Node 22 or newer is required).
  2. Run pinloop login and finish sign-in in the browser.
  3. Run pinloop upgrade to move to the Pro plan.
  4. Run pinloop guide and ask your coding agent to find how to set a routine for your search. (inferred, check the README)
  5. Choose whether the routine runs on a schedule or when new postings come in, then confirm it saved results.

Prompt for your agent

Using the pinloop-cli repo, read the output of `pinloop guide`, then set up a Pinloop routine that scans for <target role> on <schedule or new-posting trigger>. Expected output: a saved routine ID and a first set of saved postings. Verify that the routine is listed as active and that the saved postings match the search.

Caveat. Routines require the Pro plan and the README does not show the routine command, so confirm the exact steps with `pinloop guide` before relying on the schedule.

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