Public Greenhouse Job Board API (https://developers.greenhouse.io/job-board.html).
Used by employer career pages that publish jobs through Greenhouse. All endpoints
are public and require no authentication — board_token is a path segment that
identifies the company (e.g. stripe, airbnb, anthropic).
Generic CLI: the board_token is the first positional argument on every command.
greenhouse jobs list stripe lists Stripe's open jobs.
Created by @veltri-23 (Hunter Veltri).
Quick Start
1. Install
See Install above.
2. Verify Setup
greenhouse-pp-cli doctor
This checks your configuration.
3. Try Your First Command
greenhouse-pp-cli departments mock-value
Usage
Run greenhouse-pp-cli --help for the full command reference and flag list.
Paths & environment variables
This CLI separates local files into four path kinds:
| Kind | Contents |
|---|
config | User-editable settings such as config.toml and saved profiles |
data | Durable local data such as data.db |
state | Runtime state such as persisted queries, jobs, and teach.log |
cache | Regenerable HTTP/cache files |
Each kind resolves independently. The ladder is:
- Per-kind env var:
GREENHOUSE_CONFIG_DIR, GREENHOUSE_DATA_DIR, GREENHOUSE_STATE_DIR, or GREENHOUSE_CACHE_DIR
--home <dir> for this invocationGREENHOUSE_HOME for a flat relocated root- XDG env vars:
XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME
- Platform defaults matching existing installs
For containers and agent sandboxes, prefer a single relocated root:
export GREENHOUSE_HOME=/srv/greenhouse
greenhouse-pp-cli doctor
Under GREENHOUSE_HOME=/srv/greenhouse, the four dirs resolve to /srv/greenhouse/config, /srv/greenhouse/data, /srv/greenhouse/state, and /srv/greenhouse/cache.
MCP servers do not receive CLI flags from the host. Put relocation in the host env block:
{
"mcpServers": {
"greenhouse": {
"command": "greenhouse-pp-mcp",
"env": {
"GREENHOUSE_HOME": "/srv/greenhouse"
}
}
}
}
Precedence matters in fleets: an ambient per-kind variable such as GREENHOUSE_DATA_DIR overrides an explicit --home for that kind. Use GREENHOUSE_HOME or the per-kind variables for durable fleet relocation; treat --home as the weaker per-invocation lever.
Relocation is one-way. Unsetting GREENHOUSE_HOME does not move files back to platform defaults, and doctor cannot find files left under a former root. Move the files manually before unsetting relocation variables.
Existing installs keep working because the platform-default rung matches the legacy layout. Run greenhouse-pp-cli doctor --fail-on warn to check path warnings in automation.
Commands
departments
Manage departments
greenhouse-pp-cli departments <board_token> - List departments for a company (each department contains its open jobs)
jobs
Manage greenhouse job board jobs
greenhouse-pp-cli jobs list <board_token> - List all open jobs for a companygreenhouse-pp-cli jobs get <board_token> <job_id> - Retrieve a single job posting
offices
Manage offices
greenhouse-pp-cli offices <board_token> - List offices for a company (each office contains its departments and their jobs)
Self-learning loop
This CLI caches per-question discovery so repeat queries skip the walk and structurally similar queries get answered via entity substitution. The loop also self-captures: every invocation is journaled locally, and failed-flag corrections plus fresh teaches surface as candidates on the next recall for confirm/reject judgment. Agents call recall before discovery and fire teach & after answering. See the ## Automatic learning section in SKILL.md for the full protocol.
greenhouse-pp-cli recall <query> - Look up cached resources for a query before running discoverygreenhouse-pp-cli teach - Record a query -> resource mapping (silent on success, safe to background with &)greenhouse-pp-cli learnings list - Inspect taught rowsgreenhouse-pp-cli learnings forget <query> - Undo a teachgreenhouse-pp-cli learnings candidates - List auto-captured candidates awaiting confirm/rejectgreenhouse-pp-cli learnings stats - Local loop metrics: recall hit rate, teach-to-reuse, playbook resolution, candidate countsgreenhouse-pp-cli teach-pattern - Install a query/resource template up frontgreenhouse-pp-cli teach-lookup - Add an entity mapping (e.g. country code, team alias) for pattern substitution
Pass --no-learn or set GREENHOUSE_NO_LEARN=true to disable the loop for deterministic flows.
The local store's schema version stamp is one-way: once this version of greenhouse-pp-cli opens the database, older binaries refuse it with a version error — upgrade the binary rather than downgrading.
Output Formats
# Human-readable table (default in terminal, JSON when piped)
greenhouse-pp-cli departments mock-value
# JSON for scripting and agents
greenhouse-pp-cli departments mock-value --json
# Filter to specific fields
greenhouse-pp-cli departments mock-value --json --select id,name,status
# Dry run — show the request without sending
greenhouse-pp-cli departments mock-value --dry-run
# Agent mode — JSON + compact + no prompts in one flag
greenhouse-pp-cli departments mock-value --agent
Agent Usage
This CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--json output to stdout, errors to stderr
- Filterable -
--select id,name returns only fields you need
- Previewable -
--dry-run shows the request without sending
- Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
- Offline-friendly - sync/search commands can use the local SQLite store when available
- Agent-safe by default - no colors or formatting unless
--human-friendly is set
Exit codes: 0 success, 2 usage error, 3 not found, 5 API error, 7 rate limited, 10 config error.
Health Check
greenhouse-pp-cli doctor
Verifies configuration and connectivity to the API.
Configuration
Run greenhouse-pp-cli doctor to see the resolved config, data, state, and cache directories. The platform-default config path is ~/.config/greenhouse-job-board-pp-cli/config.toml; --home, GREENHOUSE_HOME, and per-kind env vars can relocate it.
Static request headers can be configured under headers; per-command header overrides take precedence.
Troubleshooting
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
list command to see available items
Generated by CLI Printing Press