Codex Integration Example

Applies to the current boss-agent-cli open-capability CLI contract as of August 10, 2026.

Good fit when

• the agent runs terminal commands directly
• you need an end-to-end chain such as schema -> status -> search -> detail -> apply
• you want stdout JSON to feed the next decision step programmatically

Minimal integration

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`, `boss apply`, or `boss greet` according to the user's goal
7. In recruiter workflows, use the candidate, application, resume, chat, reply, and job commands exposed by `boss schema`
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
boss hr candidates "Python" --city 101010100

Recommended fields to parse:

• ok: success or failure
• data: jobs, details, or action results
• hints.next_actions: suggested next command
• error.code: recovery routing
• error.recovery_action: what the agent should do next

Recovery flow

Preferred order:

boss doctor
boss status
boss login
boss search "Golang" --city 广州

Common branches:

• AUTH_REQUIRED / AUTH_EXPIRED: run boss login again
• INVALID_PARAM: return to boss schema and validate arguments
• RATE_LIMITED: back off before retrying; do not continue sensitive automation