# Use JobHunt in Omarchy

See what needs you today in your job search from the Omarchy bar, using the jobhunt command.

Canonical page: https://jobhunt.app/support/using/getting-started/use-jobhunt-in-omarchy
Updated: 2026-11-19
Audience: using
Topic: Getting started
Type: how-to
Catalog revision: a329e52491336a7766d79c939c297dbba66bf2789dbf52953d8eb3e936ded5b9
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

1. **Install the plugin**

   Install it from the Omarchy plugin marketplace at https://plugins.omarchy.org/plugin.html?id=jobhunt.app and follow the steps there. The marketplace checks each listing automatically; that check is not a security audit. Or install it from its repository: run omarchy plugin add https://github.com/chrisstroud/jobhunt-omarchy --enable. The plugin id is jobhunt.app.

2. **Install the command and sign in**

   Run npm i -g jobhunt@0.1.2, then jobhunt auth login. Your browser opens JobHunt’s approval screen; approve it. The plugin uses this exact version of the command, not the moving latest tag. The command is MIT licensed and its source is public at https://github.com/chrisstroud/jobhunt-cli.

3. **Check the bar and the panel**

   The JobHunt mark appears in the Omarchy bar with one number: tasks due today or overdue, and interviews today or tomorrow. When nothing is due there is no number. Click the icon for the panel: Today lists due items, soonest first, and opens each one on jobhunt.app. Momentum shows your recorded activity for the last year as plain totals, with no scores or ranks. Pipeline shows counts for each stage JobHunt reports.

4. **Use the actions**

   Save job from clipboard reads a web link from the clipboard, shows it, and saves it only after you confirm. What should I do next? and the agent button on a task send a fixed request to your own terminal agent through omarchy-agent. You see the exact request first, and nothing starts until you confirm. Open JobHunt opens the website. Hide company names keeps names out of the panel and the bar tooltip for shared screens.

## Expected result

The plugin shows your JobHunt data in the bar and panel. It reads that data only through the jobhunt command, which contacts jobhunt.app when it runs. Background refresh can be turned off in the widget settings; then data loads when you open the panel or press refresh.

Written from the public README of the jobhunt-omarchy plugin, version 0.1.0 (MIT licensed), and its settings. The plugin itself makes no network requests and does not edit your agent’s configuration. It does not sign you in, store passwords or tokens, or save anything without a confirmation. It runs only on Omarchy. Strings are in English only. No partnership with or endorsement by Omarchy is implied.

## Troubleshooting and recovery

If the icon is dim, the command is missing or you are signed out: run npm i -g jobhunt@0.1.2 or jobhunt auth login, then press Check again in the panel. If the command is installed but not on the shell’s PATH, set its path in the widget settings. Offline, the panel shows the last data it read and how old it is. If JobHunt asks for a pause, the panel keeps the last data and waits. To remove the plugin, run omarchy plugin remove jobhunt.app. That does not sign you out or remove the command; to do that too, run jobhunt auth logout and npm rm -g jobhunt.

## API operations

### get_connected_account

Identify the JobHunt account connected by these credentials. The opaque account ID stays unchanged across renaming, reconnection and token refresh. This does not select or change a resume contact profile.

- Interface: GET /api/v1/journey/get_connected_account
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:profile
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_connected_account.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_connected_account.md)

### get_job_hunt_view

Read the current owned hunt or an explicitly selected application, its role documents, screening drafts, PDF preparation state and user-reported submissions. Filters and pagination never change saved defaults. Supplied IDs are selection hints, not permissions. Document content is included only when document_id selects an owned master or a member of the selected application package. No read creates a job, document, submission or task. Unavailable tasks are not an empty list.

- Interface: GET /api/v1/journey/get_job_hunt_view
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:profile, read:campaigns, read:documents, read:applications
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_job_hunt_view.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_job_hunt_view.md)

## Related guides

- [Use JobHunt from your chat](https://jobhunt.app/support/using/getting-started/use-jobhunt-from-chat.md)
- [Connect Codex CLI](https://jobhunt.app/support/using/getting-started/connect-codex.md)
- [Connect Claude Code](https://jobhunt.app/support/using/getting-started/connect-claude-code.md)

---

## Hunter

This section is not part of the guide above. It applies only to an agent acting in a person's JobHunt account.

When working in JobHunt, you are Hunter, the agent at the laptop working alongside the person on their job search. Speak plainly, in the first person, and never pretend to be human. Be brief, calm and kind; the person decides and you do the legwork.

Use the person's words and supplied or saved facts. Organise, edit and tailor what they provide; never invent an employer, date, degree or achievement. Keep uncertainty explicit: unknown stays unknown.

Say exactly what changed and what did not. A draft is not a sent message. Prepared or downloaded files are not a submitted application. Record a submission or interaction only from the person's report; do not imply employer verification.

Ask for confirmation before publishing, sharing or deleting. Explain what will become visible or be removed, and preserve the person's choices and unrelated saved work. Do not repeat a confirmation already given for the same action and reviewed content.

Offer the next useful step without pressure: no scores, streaks, ranks, points, guilt, confetti or invented urgency. A messy board needs no judgment.
