jobhunt.app/mcp

Keep track of your next steps

Keep preparation and follow-ups tied to the right work and people.

Updated

Step by step

  1. Make the next step concrete

    Open Tasks on an application. Give the task a clear action, such as preparing questions or checking back after an interview.

  2. Choose a date when useful

    Set a date for work you want to return to. A date-only reminder needs no invented time. For a timed deadline, keep the intended timezone and check the saved local date and time; the UTC date can differ. Use recurrence only when the action really repeats. For a repeating task, your agent sees the next date the schedule falls on that is still to do.

  3. Set your time zone once

    Choose your time zone in Settings, under Appearance or JobHunt preferences. Either one now saves it for everything: task dates and which tasks are overdue, the Today agenda, repeating tasks, the date you report an application on, and the date a highlight gets when you give none. Before this, the two pages kept separate values and could disagree; saving either one again brings them back into line. Choosing Automatic on the Appearance page removes the saved choice from both pages. Without a saved time zone, dates are counted in UTC, and a submission dated up to a day ahead of UTC is still accepted. Use an area and city name, such as America/Los_Angeles; an older name such as PST8PDT is saved as the place it stands for.

  4. Resume with the saved context

    In a fresh chat, ask: “Find my follow-up due Thursday and show the saved conversation and unsent draft for the correct person.” Your agent should find the saved task first and match its exact ID, not just a repeated title or person’s name. For a one-off task without an application, it can follow the contact/company lists and their related-task pages until it finds that exact ID.

  5. Check the direct relationship

    An application task can appear under several people connected to the same role. That membership does not identify its direct recipient. The existing task list can return explicit contact/company links; match the exact task ID there, then open that saved relationship. If a link cannot be recovered or the list is unavailable, ask which person the user means instead of guessing. Follow related pages when reading their saved notes and conversations.

  6. Recover an unfinished save

    Creating a contact/company follow-up and giving it a date are separate steps. If only creation succeeded, keep its saved task ID, read its current state and finish setting the requested date. Reconcile an interrupted save using its original request rather than creating another task. A calendar date needs no invented time; a timed deadline needs a timezone.

  7. Mark what you did

    Complete the selected task when the action is done. Reopen it if you need to correct the record. Reading its context does not complete it, and an unsent draft remains an unsent note.

  8. Read Today from the CLI or an agent

    In the CLI and through an agent (get_today_agenda and get_workspace_today_v2), Today lists your open tasks and the tasks you completed today, where today is the day in your account’s time zone. Tasks completed on an earlier day are no longer listed. The website’s Today view is unchanged. An account with more than about 1,000 open tasks still gets an error (processing_failed, HTTP 502) from Today; complete or remove some tasks, then read it again.

What happens next

Your saved tasks describe the work you plan to do and the work you have done.

Troubleshooting

A follow-up task is a record, not an email. JobHunt does not contact the employer just because you create or complete it. Missing access or an incomplete page is not proof that a relationship or conversation does not exist; do not substitute another person’s record.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist tasks

List owned follow-ups and recurring tasks with revisions and due dates, optionally for an application or hunt. Defaults to open tasks; is_active=false reads completed tasks for reopening and null reads both. Results are paginated in groups of 20; honor has_more. Recurring results retain schedule is_active separately from recurrence.completed_at for the requested occurrence_date (defaults to account-local today). Stage templates are separate. Requires read:tasks and read:applications, plus read:campaigns when selecting a hunt.

GET /api/v1/journey/list_tasks_v2

DECLARED PERMISSIONS

  • read:tasks
  • read:applications
View input, output and access requirements →
READget task

Read one owned task and its current revision before editing. Application-linked tasks also require read:applications. Recurring tasks include their schedule and date-specific completion fingerprint; stage templates use application records.

GET /api/v1/journey/get_task_v2

DECLARED PERMISSIONS

  • read:tasks
View input, output and access requirements →
WRITEcreate task

Create one requested follow-up, standalone or linked to an owned application/search. Reuse request_id after a lost response and check get_job_hunt_operation. Calendar dates stay on their supplied day; timed due_at values require a timezone. Use recurrence for explicit repeating requests; weekly/custom_days use Monday=0 through Sunday=6, and optional due_time uses the account timezone. Do not invent a time or turn a recurring request into a one-off. Linking a job/search also requires its read grant. Records a task only: no email, invitation, calendar sync or scheduled outreach.

POST /api/v1/journey/create_task_v2

DECLARED PERMISSIONS

  • write:tasks
View input, output and access requirements →
WRITEupdate task

Edit, reschedule, complete (is_active=false) or reopen (is_active=true) one task using get_task_v2's current revision. For recurring tasks, edit title/description here and use set_recurring_task_completion_v2 for completion; do not change is_active or due_at. Omitted fields stay unchanged; null description/due_at clears them. Keep request_id for an exact retry. A conflict requires a fresh read, never blind overwrite. Does not send messages or calendar invitations.

POST /api/v1/journey/update_task_v2

DECLARED PERMISSIONS

  • write:tasks
View input, output and access requirements →
WRITEset recurring task completion

Complete or reopen one date of a recurring task without ending its schedule. Read get_task_v2 with occurrence_date first; use its revision and recurrence fingerprint and date. Completion dates must not be in the future; reopening also removes future skip exceptions. Keep request_id for retries. No messages or calendar sync.

POST /api/v1/journey/set_recurring_task_completion_v2

DECLARED PERMISSIONS

  • write:tasks
View input, output and access requirements →
READlist workspace crm

Read one owned CRM page. Counts and filters apply to this page; follow has_more.

GET /api/v1/journey/list_workspace_crm_v2

DECLARED PERMISSIONS

  • read:contacts
  • read:companies
  • read:applications
View input, output and access requirements →
READget workspace crm

Read an owned contact or company with a page of related notes, tasks, applications and history. Follow related_has_more by increasing related_page; never infer missing records from one page.

GET /api/v1/journey/get_workspace_crm_v2

DECLARED PERMISSIONS

  • read:contacts
  • read:companies
  • read:applications
  • read:tasks
View input, output and access requirements →
WRITEsave workspace contact

Save an explicitly reviewed owned contact action. Existing records require the exact fingerprint. Deletion unlinks relationships but preserves applications. Interaction notes record a conversation; they never send a message. Reuse the same request ID after an uncertain response.

POST /api/v1/journey/save_workspace_contact_v2

DECLARED PERMISSIONS

  • write:contacts
View input, output and access requirements →
WRITEsave workspace company

Save an explicitly reviewed owned company action. Existing records require the exact fingerprint. Deletion unlinks relationships but preserves applications. Interaction notes record a conversation; they never send a message. Reuse the same request ID after an uncertain response.

POST /api/v1/journey/save_workspace_company_v2

DECLARED PERMISSIONS

  • write:companies
View input, output and access requirements →