CLI - trexi

The trexi CLI manages jobs and candidates from the terminal. It speaks the same API as the dashboard, so anything you script here maps 1:1 to what the web app does — and the same client core also backs the MCP server.

Authenticate

In the web app, open Settings → API keys and create a key. Copy it (trexi_sk_…) — it’s shown once.
Log in with it:

trexi auth login trexi_sk_your_key

The CLI targets the hosted backend when you point it there:

export TREXI_API_URL=https://api.trexi.ai

Every request is attributed to you, in the org the key belongs to, and your role is enforced. Check who you’re acting as with trexi auth whoami, and sign out with trexi auth logout. See Your team.

Commands

Command	Description
`jobs list`	List jobs in the active org
`candidates list -j <jobId>`	List a job’s pipeline (stages + candidates)
`candidates move -j <jobId> -c <appId> -t <stage>`	Move a candidate to a stage (name or id)
`candidates hire -c <appId>`	Mark a candidate hired
`candidates reject -c <appId>`	Reject a candidate
`candidates reopen -c <appId>`	Reopen a candidate (back to active)
`team list`	List members and roles
`team invite -e <email> -r <admin\|user>`	Invite a member
`team set-role -u <userId> -t <owner\|admin\|user>`	Change a member’s role
`team transfer-ownership -u <userId>`	Hand off ownership (you step down to admin)
`feedback list -c <appId>`	List interview feedback for a candidate
`feedback add -c <appId> -r <strong_no\|no\|yes\|strong_yes> [-n <notes>]`	Add or update your feedback

candidates has the alias c. A “candidate” id is the application id (a person’s application to a specific job).

Example

# Look at a job's pipeline, advance a candidate, then hire them.
trexi jobs list
trexi c list -j 1
trexi c move -j 1 -c 5 -t Interview
trexi feedback add -c 5 -r strong_yes -n "Excellent onsite."
trexi c hire -c 5