viy1204/recruiting-copilot

An AI recruitment workflow for HR/headhunters: Pressur-style clarification of real job requirements → Boss Zhipin + Liepin dual-channel daily source screening → Greeting → Interview scheduling → Candidate ledger → Daily report. There are also market talent inventory, resume evaluations, and resume attachments for Liepin/BOSS from Feishu mailbox on demand.

Compatible with any AI programming assistant: Claude Code, Codex, Workbuddy, qoderwork, MiniMax Code, Z Code, etc. As long as your tool can read AGENTS.md in the workspace, it can run this process.

⚠️ Account Security Guidelines (Updated 2026-08-19, Please Read)

**Two rules: Don’t use a headless setup; For daily recruitment, use CLI commands; don’t manually click operations in the ‘Recruitment Browser’ panel. **

About headless:* *BOSS and Liepin now have heads by default (real window, steals keyboard focus once when launched). Both companies have tested samples and share the same root cause:

• BOSS (2026-08-19 Return to Head) — An account was restricted from logging in via web for 24 hours, page copy Clearly stated: “Your account has been detected to use third-party recruitment management systems, plugins, plugins, software, or other auxiliary tools”; Another team Using the upstream version (default headline) is inactive for a long time, but their AI arbitrarily changes the headless version and bans the account on the same day.
• Liepin (2026-09-21 Flipped back to ‘Head’) — Tested on 2026-09-20 After consecutive headless calls, the account was judged as ‘abnormal behavior’, 302 arrived safe.liepin.com/.../captchaPage_PC, the business interface begins silent interception. liepin-cli v0.2.7 synchronizes to default.

The root cause is the same: the UA of the headless Chrome self-reports HeadlessChrome, while the Client Hints still says Google Chrome, This paradoxical signal is zero false alarm. All three parties deliberately avoid disguising UA (camouflage and ‘not recognizing the direction of automation’ confrontation) This red line conflicts), so you can’t avoid it, so you can’t use the headless one.

Additional RECRUIT_BROWSER_HIDDEN=true—This is the Unified Overlay Switch, which drags both players into the headless category. Grabbing attention is an experience issue; account restrictions are a business issue. If you want to see the screen, use the laptop panel, not flip back to nowhere to go.

By the way: During the time limit, only the web version is restricted; the BOSS Zhipin app and PC client can still be used as usual, without interruption.

Reason: boss-cli anti-detection protection (blocking risk control SDK, pretending to succeed with 204 on reported endpoints, injecting page guard, etc. All are attached to the CLI process’s own CDP session, and the process becomes invalid as soon as it exits. Confirmed by actual testing. So browser During cross-command residency, you are completely naked; panel operations and panel navigation are unprotected during this period.