hirify-cli 0.4.5 → 0.4.6

package/README.md

@@ -55,6 +55,9 @@ values are available. It comes from the server, so it stays current as search ch
 requires a compact preview before the final search, so the agent can correct an empty or irrelevant
 filter before relying on it.
 
+New saved searches start with delivery off. Enable Telegram explicitly with
+`hirify feed deliver <id> --telegram` after the user approves notifications.
+
 Add `--json` to any command for the server's answer as JSON instead of the text a person reads.
 `--fields a,b` narrows a compact answer to the fields you name. Put `HIRIFY_DEBUG=1` in front of a
 command when you need the server's own reply to attach to a bug report.

package/bin/hirify.js

@@ -81,8 +81,8 @@ const HELP = `hirify - job search for AI agents
 
   hirify feed list                the feeds you saved on the site
   hirify feed show <id>           vacancies from one feed   [--limit N] [--page N]
-  hirify feed create <name>       save a search             [--filters JSON] [--webhook N]
-  hirify feed deliver <id>        change how a feed reaches you
+  hirify feed create <name>       save a search             [--filters JSON] [--telegram] [--webhook N]
+  hirify feed deliver <id>        change delivery           [--telegram|--no-telegram] [--webhook N|--no-webhook]
 
   hirify profile list             the profiles you can apply with
   hirify webhook list             your delivery endpoints
@@ -295,7 +295,26 @@ function printNotice(notice) {
 
 // Text our own server wrote for the agent to read: application rules, address rejections.
 // Passing it through beats paraphrasing, because paraphrasing drifts from the real rule.
-const serverMessage = (body) => (typeof body?.message === 'string' && body.message ? body.message : null)
+function serverMessage(body) {
+  const firstLine = (value) => {
+    if (typeof value === 'string' && value.trim()) return value.trim()
+    if (Array.isArray(value)) {
+      for (const item of value) {
+        const line = firstLine(item)
+        if (line) return line
+      }
+    }
+    if (value && typeof value === 'object') {
+      for (const item of Object.values(value)) {
+        const line = firstLine(item)
+        if (line) return line
+      }
+    }
+    return null
+  }
+
+  return firstLine(body?.error?.details) || firstLine(body?.error?.message) || firstLine(body?.message)
+}
 
 /**
  * The one-line report for a policy restriction: a canonical 403 that names itself
@@ -1429,7 +1448,7 @@ async function cmdFeedCreate(args, words) {
     }
   }
 
-  const payload = { name, filters }
+  const payload = { name, filters, notify_telegram: false }
   if (args.includes('--no-telegram')) payload.notify_telegram = false
   if (args.includes('--telegram')) payload.notify_telegram = true
   const webhook = flag(args, '--webhook')
@@ -1441,13 +1460,19 @@ async function cmdFeedCreate(args, words) {
   const res = await callCapability('feeds.create', { payload, allow: [201, 422] })
   if (res.status === 422) die(serverMessage(res.body) || 'the feed was not created. Please check the criteria.')
 
-  out(res.body, () => printFeedState(res.body?.data ?? {}, 'Saved.'))
+  out(res.body, () => {
+    const feed = res.body?.data ?? {}
+    printFeedState(feed, 'Saved.')
+    if (!feed.notify_telegram && !feed.webhook_endpoint_id) {
+      console.log(`To receive new matches in Telegram: hirify feed deliver ${feed.id ?? '<id>'} --telegram`)
+    }
+  })
 }
 
 /** Change where a feed is delivered, without touching what it searches for. */
 async function cmdFeedDeliver(args, words) {
   const [id] = words
-  if (!id || !/^\d+$/.test(id)) die('a feed id is required: hirify feed deliver <id> [--telegram] [--webhook <id>]')
+  if (!id || !/^\d+$/.test(id)) die('a feed id is required: hirify feed deliver <id> [--telegram|--no-telegram] [--webhook <id>|--no-webhook]')
 
   const payload = {}
   if (args.includes('--telegram')) payload.notify_telegram = true
@@ -1475,7 +1500,7 @@ function printFeedState(f, lead) {
     f.webhook_endpoint_id ? `webhook ${f.webhook_endpoint_id}` : null,
   ].filter(Boolean)
   console.log(`${lead} Feed ${f.id ?? '-'}: ${f.name || '(untitled)'}`)
-  console.log(where.length ? `Delivered to: ${where.join(' and ')}` : 'Not delivered anywhere yet.')
+  console.log(where.length ? `Delivered to: ${where.join(' and ')}` : 'Delivery is off.')
 }
 
 /** The delivery endpoints on the account. Free; creating one needs the plan. */
@@ -1803,7 +1828,7 @@ async function cmdFilterGuide() {
       '        their names have to come from someone who knows them.')
   }
 
-  const guide = typeof res.body?.guide === 'string' ? res.body.guide.trim() : ''
+  const guide = typeof res.body?.data?.guide === 'string' ? res.body.data.guide.trim() : ''
   if (!guide) die('the server answered without a guide. Please try again in a minute.')
 
   out(res.body, () => console.log(guide))

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hirify-cli",
-  "version": "0.4.5",
+  "version": "0.4.6",
   "description": "Hirify CLI for AI agents: browser sign-in, job feeds, search, reading a vacancy in full, contacts to apply to, and applying on Hirify.",
   "bin": {
     "hirify": "bin/hirify.js"

package/skills/hirify/SKILL.md

@@ -8,6 +8,14 @@ description: Job search through Hirify - vacancies from the user's saved feeds,
 Use the Hirify job board through the `hirify` CLI. This file gives the working order; `reference.md`
 has every command in full, and `hirify intro` is the server's guide.
 
+## Setup
+
+The CLI is the npm package `hirify-cli`; the command is `hirify`. It needs Node 18 or newer and
+network access to api.hirify.me. If `hirify` is not on PATH, run every command in this file as
+`npx -y hirify-cli <command>` instead: the same CLI, nothing installed. `npm install -g hirify-cli`
+puts `hirify` on PATH for good and keeps itself up to date; offer it, and run it only after the user
+says yes.
+
 ## What stays here, and what you fetch
 
 This installed file holds only stable rules. Fetch anything Hirify can change:
@@ -90,7 +98,8 @@ Two cases, two commands:
 
 ## Saved searches and delivery
 
-These change the user's account, so the same rule holds: propose, get a yes, then do it.
+These commands change the user's account, so get a yes. Creation leaves delivery off: report that,
+offer the exact `feed deliver` command, and run it only after a separate yes.
 
 ```bash
 hirify feed create "<name>" --filters '<json>'   # criteria: hirify filter guide
@@ -99,7 +108,7 @@ hirify webhook list
 hirify webhook create "<name>" <url>
 ```
 
-`--filters` takes the same criteria as the site's filter form; read `hirify filter guide` first.
+`--filters` uses the site's filter criteria; read `hirify filter guide` first.
 Creating a delivery endpoint returns a **secret shown once**: give it to the user immediately to
 store, because it signs every delivery and cannot be shown again.
 
@@ -114,6 +123,9 @@ gives a ticket number or says there is none yet, nothing writes back, and no fix
 **The message you were given is the truth; this is a map of the kinds, not strings to match.** Every
 failure exits non-zero and writes one line to stderr. Read that line and tell the user what it says.
 
+- **`hirify: command not found`**: run the command as `npx -y hirify-cli <command>`; see Setup.
+- **"the network seems to be unavailable"**: api.hirify.me is unreachable. Sandboxed agents often run
+  with network off (Codex CLI does by default); ask the user to allow it for the session, then retry.
 - **Not signed in**: ask the user to run `hirify login` (it opens a browser and needs a person -
   never run it yourself). On a server with no browser: `hirify auth <key>`, key from
   hirify.me/account/api-access.

package/skills/hirify/reference.md

@@ -6,6 +6,9 @@ Commands are a noun and a verb: the noun is the thing you are working with, the
 to it. `hirify <noun>` on its own lists the verbs that noun takes. `login`, `logout`, `auth` and
 `intro` stay single words: they are not operations on a thing.
 
+The CLI is the npm package `hirify-cli`. Every command below is written as `hirify ...`; when `hirify`
+is not on PATH, run it as `npx -y hirify-cli ...` instead (see Setup in `SKILL.md`).
+
 **This file describes the CLI, not the state of Hirify.** It is installed with the skill and never
 updated afterwards, so it names no filter, no limit and no number that our side can change. Those
 come from commands: `hirify filter guide` for filters, `hirify account show` for what is left,
@@ -212,11 +215,15 @@ hirify webhook list
 hirify webhook create "<name>" <url>
 ```
 
-These change the user's account. Propose, get a yes, then run them.
+These change the user's account. Propose, get a yes, then run them. A new saved search has delivery
+off by default. Enabling Telegram or a webhook is a separate account change and needs a separate
+yes, even when creating the search was already approved.
 
 `--filters` takes the same criteria the site's filter form produces, as JSON, and the names come
 from `hirify filter guide`. Omitting it saves a feed with no criteria, which means "send me
 everything" and is legal.
+After creation, report that delivery is off and show the exact `feed deliver` command. Run that
+command only after the user approves delivery.
 
 `webhook create` answers with the endpoint and a **secret shown once**. Hand it to the user
 immediately and tell them to store it: it signs every delivery and cannot be shown again.