Applies to the current boss-agent-cli low-risk CLI contract as of May 18, 2026.
- the agent runs terminal commands directly
- you need a low-risk chain such as
schema -> status -> search -> detail -> shortlist - you want stdout JSON to feed the next decision step programmatically
Teach the agent to follow this working pattern:
When the task involves BOSS Zhipin search, detail inspection, or local job organization:
1. Run `boss schema` first to get capabilities and arguments
2. Run `boss status` to check authentication
3. If not logged in, run `boss login` and tell the user to complete the QR flow if needed
4. Use `boss search` for discovery
5. Use `boss detail` after a promising hit
6. Use `boss shortlist add` for local organization; ask the user to complete outreach manually on the official website
7. In recruiter workflows, prefer `boss hr jobs for low-risk job-list management; candidate workflows are restricted by default`
8. Parse stdout JSON only; when `ok=false`, inspect `error.code` and `error.recovery_action`
Minimal candidate-side command chain:
boss schema
boss status
boss search "Golang" --city 广州 --welfare "双休,五险一金"
boss detail <security_id>
boss shortlist add <security_id> <job_id>Minimal recruiter-side chain:
boss schema
boss status
boss hr jobs list
# Candidate applications, search, resumes, chat, and replies stay manual on the official recruiter UIRecommended fields to parse:
ok: success or failuredata: jobs, details, or action resultshints.next_actions: suggested next commanderror.code: recovery routingerror.recovery_action: what the agent should do next
Preferred order:
boss doctor
boss status
boss login
boss search "Golang" --city 广州Common branches:
AUTH_REQUIRED/AUTH_EXPIRED: runboss loginagainINVALID_PARAM: return toboss schemaand validate argumentsRATE_LIMITED: back off before retrying; do not continue sensitive automation