Claude Cowork
Install the Hyreflow plugin in Claude Cowork and run your first play.
Cowork runs Claude's agent inside Claude Desktop, without a terminal. The Hyreflow plugin
gives it the recruit skills and the hyreflow CLI, so you can source, enrich, and qualify
candidates from a Cowork session.
Before you start
- Claude Desktop with access to Cowork.
- A folder for the session to work in. Hyreflow writes CSVs and run output there, so pick a folder you're happy to keep.
- Code execution and network access turned on — see Allow API access below. Skills need code execution, and Hyreflow calls live provider APIs, so a session without egress can't run anything. Do this before your first request, not after it fails.
Install the plugin
Open the Plugins page
In Claude Desktop, open Cowork, then Customize in the sidebar, then Plugins.
Add the marketplace
Select Add marketplace and enter:
https://github.com/automindz-solutions/hyreflow-pluginsInstall Hyreflow
The hyreflow plugin now appears alongside your other marketplaces. Select it and click
Install.
Start a session
Open a Cowork session and pick your working folder.
Allow API access
This is the step people miss, and it fails in a way that looks like Hyreflow is broken when it isn't. The Cowork sandbox reaches the network only as far as you allow. Every Hyreflow call — signing in, sourcing, enrichment — is a live HTTPS call, so all of them fail until egress is on.
Open Capabilities
In Claude Desktop, open Settings → Capabilities.
Turn on code execution
Enable Cloud code execution and file creation. It's required for skills, so the Hyreflow skills don't load without it.
Turn on network egress
Enable Allow network egress.
Set the domain allowlist to All domains
Domain allowlist controls which domains the sandbox can reach. It offers None, Package managers only, and All domains — choose All domains.
Package managers only is the trap. It's enough to install the hyreflow CLI and then fails
everything the CLI is for: the install succeeds, sign-in and every provider call don't. Because a
waterfall charges only on a usable result, a blocked provider completes and reports nothing found —
identical to a provider that genuinely had no data. You get a session that looks like it works and
quietly returns empty results. Use All domains.
On Team and Enterprise plans an administrator can lock Cowork and network access. If the settings are greyed out, ask your workspace owner to enable Cowork and outbound network access for your account.
First run
The plugin ships the skills; the skills install the CLI. On your first Hyreflow request the agent
installs hyreflow, then opens your browser to connect your account — relay the link it prints and
approve it. Sign-in is resumable, so if the agent finishes before you've approved, just ask again
and it continues the same sign-in.
Let that first command finish before sending a second request.
Then try the guided demo:
/hyreflow-quickstartOr go straight at a real task:
/hyreflow-recruit Source 20 senior backend engineers in Berlin with verified personal emailsCowork may list plugin skills under the plugin's name — /hyreflow:hyreflow-recruit rather than
/hyreflow-recruit. Either form reaches the same skill; use whichever your session offers.
New accounts start with +25 credits. Check the balance any time:
hyreflow billing balanceWhat the plugin adds
| Skill | What it's for |
|---|---|
hyreflow-recruit | The meta skill — sourcing, enrichment, qualification, sequencing, ATS push |
hyreflow-quickstart | A guided demo run, good for a first session |
hyreflow-workflows | Scheduled and event-driven runs |
hyreflow-feedback | Send a bug report or feature request to the team |
It also installs an approval hook. Cowork normally asks before every shell command; the hook
auto-approves the hyreflow calls that neither spend credits nor touch your sign-in —
auth status, tools search, skills list, update --check, and session progress. Anything that
spends or mutates — tools execute, enrich, workflows run, auth login — still prompts you.
Your own deny rules always win over the hook.
Keeping it current
In Cowork the two pieces arrive by different routes, so they update differently:
- The CLI — installed into the session, so each new session gets the current one. Mid-session,
hyreflow updatepulls a newer CLI; it's live on the nexthyreflowcommand. Everything the CLI resolves at call time — provider routing, waterfall order, credit cost — comes from the engine, so it's current regardless of the plugin's age. - The skills — these ship inside the plugin, so they refresh when the plugin does. Open Customize → Plugins and click Update on the marketplace.
The plugin is stuck on an old version
Remove the marketplace and add it back, then reinstall the plugin — a fresh add fetches the current version.
Under Customize → Plugins, open the marketplace's ⋯ menu and select Remove. Then Add marketplace, enter the same URL, and install Hyreflow again. Your account and credits are unaffected; only the local copy of the skills is replaced.
Outside Cowork — in a terminal, or any agent driven by the CLI — the CLI owns the skills instead,
and hyreflow update refreshes them in place.
Refresh the skills without the marketplace or the CLI
The skills are published as a public catalog, so any generic skill installer can pull the current
copies straight from it — useful when you're on the plugin install and don't have hyreflow on your
path:
npx skills@latest add https://recruit.hyreflow.ai/.well-known/skills/index.json \
--agent claude-code --global --skill '*' -yThat writes all four skills into your agent's global skills directory, replacing whatever copies are
there. Add --list instead of --skill to see what the catalog offers first, or name one skill
(--skill hyreflow-recruit) to take just that package. Each package is served with a SHA-256 digest
the installer verifies before it writes anything, so run it again whenever you want the current
skills.
Troubleshoot
A provider call fails or times out — check egress first
Always check this before anything else. Open Settings → Capabilities and confirm Cloud code execution and file creation is on, Allow network egress is on, and Domain allowlist is All domains — not Package managers only. A blocked domain and a provider with no data look the same from inside the session, so an egress problem reads as bad results rather than as a connection error.
Once egress is confirmed, check where you stand:
hyreflow auth status
hyreflow billing balanceThe CLI installed fine but nothing else works
That's the signature of Domain allowlist: Package managers only — npm is reachable, so the
install succeeds, but recruit.hyreflow.ai and every provider are not. Switch the allowlist to
All domains and run the request again.
The agent asks you to sign in again
A new sandbox doesn't carry the previous session's credentials. Re-run the sign-in the skill offers; it's the same resumable flow, so approving in the browser is all that's needed.
`hyreflow: command not found`
The CLI install didn't land, or it's outside the session's PATH. Ask the agent to install it to
your user prefix and add it to the path:
npm install -g hyreflow --prefix "$HOME/.local"
export PATH="$HOME/.local/bin:$PATH"
hyreflow setupnpm install -g hyreflow --prefix "$HOME\.local"
$env:Path = "$HOME\.local;$env:Path"
hyreflow setupBlocked from npmjs.com? Add --registry https://recruit.hyreflow.ai/api/v2/npm/.
A run costs more than you expected
Pilot before you pull. --dry-run prices a call without charging, and --rows 0:1 runs a single
row through an enrichment waterfall:
hyreflow tools execute people_search --dry-run --payload '{"titles":["CTO"],"limit":1}'See Credits and billing for how charging works.