Connecting your AI to intervu

The connector is like using a website: nothing installs, it works on any computer, and it's the default for most people. In Claude's settings, you paste in an address and approve it once — that's it.

The local agent is like installing a desktop app: it lives on your own Mac, can message you on WhatsApp, and can work in the background even when you're not actively chatting. It's the power-user path, Mac-only today, and it takes a few more minutes to set up.

If you're not sure, use the connector first — jump to The Claude connector. On Windows, the local agent isn't available yet; see Windows.

In Claude, open Settings → Connectors → Add custom connector and paste this address:

Think of it as giving Claude a phone number it can call whenever you ask it something about jobs — nothing downloads or installs on your computer. Claude will ask you to approve the connection once; after that, just ask it to search or track jobs.

Out of the box, this gets you search and tracking: ask your AI to find roles, sanity-check a posting, or save something to your tracker, and it can do that right away. Actually opening a listing and filling out the application form needs a different kind of tool — one with browser control, like Claude Code. Either way, nothing here ever submits an application by itself; you're always the one who hits submit.

One more thing worth knowing: the job descriptions your AI reads through this connector are text pulled from the original posting elsewhere on the web, not something intervu wrote. Every response labels that text as data for your AI to read, never as instructions for it to follow — so a strange line buried in a posting can't quietly make your AI do something you didn't ask for.

If Claude's settings don't show a connectors option yet, it's still rolling out to accounts — try the OpenClaw local agent instead (Mac only), or check back shortly.

The local agent (OpenClaw) only installs on a Mac today — there isn't a Windows version yet. The Claude connector above works fine on Windows right now: nothing to install, same steps as any other computer.

If you specifically want the local agent, the OpenClaw tab on /connect has a “tell me when Windows is ready” signup — that list is what tells us how many people are waiting on it.

The local agent needs a small program called Node to actually run — think of it as the engine under the hood, the same way an app needs the right version of iOS or Android underneath it. Most Macs don't have it by default, and older install scripts used to just tell you to go install it yourself, which is exactly where a real install died recently.

This installer no longer asks you to do that. If Node isn't already on your Mac, it downloads its own private copy into a folder that belongs only to you (~/.openclaw/runtime), checks it against the official checksum published by nodejs.org so you know it wasn't tampered with, and adds one line to a personal settings file (~/.zprofile, marked “# intervu installer: local Node runtime”) so your Terminal can find it every time you open a new window. No admin password, nothing installed system-wide.

If this step failed, it's almost always a dropped network connection to nodejs.org. Re-run the install command below — it's safe to run as many times as you need, it skips whatever already finished:

What happened: on a real install (Aug 5), someone's Mac already had an old copy of Node from before this installer existed. That old copy caused OpenClaw to silently install an older version of itself — and WhatsApp pairing then failed with a confusing error about a “plugin API” version, which doesn't mention Node at all.

Why: a too-old engine can only run an older build of the app on top of it, so the install quietly downgrades instead of failing outright — you don't find out until a later step breaks for an unrelated-looking reason.

The fix is simple: just re-run the install command. It now brings its own current runtime (see Setting up the runtime automatically) instead of trusting whatever was already on your Mac, so this shouldn't happen again.

Partway through, OpenClaw hands you off to its own setup wizard — not something intervu runs. It asks you to pick an AI model provider (for example, Anthropic, the company behind Claude) and paste in a personal API key for it: an account you set up yourself, which can bill you separately for what the agent uses.

We'll say it plainly: this is genuinely the hardest step in today's install, and there's no shortcut around it yet — you do need an account with a model provider and a key from it.

If the wizard didn't finish, open Terminal (the app where you type commands) and run:

Once that completes, re-run the install command:

Near the end of the install, a browser window opens automatically asking you to approve the connection between your Mac and intervu. It waits about 60 seconds for you to click through — like a login link that expires quickly, it's timed on purpose so a connection can't be approved by someone else later without you noticing.

If you missed the window, nothing is broken — just re-run the install command below. It skips every step that already finished and opens a fresh approval window; this time, have the browser ready to click through right away.

Near the end of the install, the script downloads intervu's actual job-search instructions from intervu.cc and installs them into OpenClaw. This step failed — almost always a network hiccup (a dropped connection), not a problem with your account or anything installed so far.

Re-run the install command; it only retries the download and leaves everything already set up untouched:

OpenClaw runs a small background helper that stays on and watches for things like incoming WhatsApp messages — think of it like a mail server quietly running in the background, always listening. After install, it takes a few seconds to start back up, and the installer waits up to 30 seconds for it before giving up.

If it's still not answering after that, open Terminal and run:

That tells you what it's actually doing. Then re-run the install command:

Pairing WhatsApp — scanning a QR code to link the chat — happens inside OpenClaw's own onboarding wizard, not as a separate step this installer runs. If the wizard reaches that point and pairing fails or the QR code won't scan, the usual cause is the outdated-OpenClaw problem above: an old runtime quietly installed a version of OpenClaw whose WhatsApp piece doesn't work correctly.

See An old runtime quietly gave you an outdated OpenClaw and re-run the install command — it now brings a current runtime, which fixes this in most cases.

You can remove everything the local agent installed. In Terminal, run:

Then open ~/.zprofile in a text editor, find the line that reads # intervu installer: local Node runtime, and delete that line and the one right after it. If your Mac already had Node installed before you ran this installer, nothing else on your machine was touched — the runtime folder above was a separate, private copy the installer added just for itself.

Your WhatsApp link dies along with the agent — there's nothing left to message. And nothing about you stays behind on intervu's servers from the local agent: it runs entirely on your own machine, and the only thing that ever left it was job-matching queries to intervu.cc, the same way your browser talks to any website you visit.

If none of the above covers it, use the contact page — we read everything that comes through there. It helps to mention which step you were on and what the terminal or Claude showed you. You can also go back to /connect and try the other path — the connector needs nothing installed at all.