Jobber

AI choices

Choose who powers the work.

Jobber is designed to support three explicit AI modes. The app must show which option is active, who bills for it, and what context it can receive—without silently switching providers.

Provider availability, eligibility, and rates can change. Jobber confirms the current connection before use.

One active provider per task

Select a provider, confirm an assisted task, and review its output in Jobber. The active provider, billing relationship, and shared context remain visible. Jobber does not silently switch providers.

Compare the options

Existing eligible access

Use my Codex

Jobber runs an isolated, audited Codex connection locally. Scoped task context goes to OpenAI under the user’s eligible account and current OpenAI terms.

  • No separate Jobber AI subscription.
  • Availability depends on eligible Codex access.
  • Jobber must never modify the user’s global Codex setup.

Direct provider billing

Use my OpenAI API key

You supply an API key and OpenAI bills that API account. Jobber stores the credential in macOS Keychain, not workspace files or browser storage.

  • Connection, replacement, and disconnect stay explicit.
  • Usage and cost should be labeled reported or estimated.
  • Jobber does not receive the user’s provider invoice.

Optional monthly subscription

Use Jobber AI

The hosted option sends scoped task context transiently through Jobber to an approved AI provider. The app receives a Jobber entitlement token, never a shared OpenAI key.

  • Hard monthly allowance and no surprise overages.
  • Per-task, retry, concurrency, and monthly cost limits.
  • Separate from the Jobber Desktop license.

All modes

You remain in control

The selected provider may help match, evaluate, draft, or revise. Jobber still requires the person to review material and take every consequential external action.

What Jobber must show before connection

  • the active provider and who pays for usage;
  • which categories of local context the selected task can send;
  • current provider availability and material data-handling terms;
  • usage limits, expected availability, and recoverable failures; and
  • how to test, disconnect, replace, or change the option.

No silent fallback

If the selected option is unavailable, Jobber stops that task with a clear remedy. Switching to another provider is a new, user-approved task—not an invisible recovery mechanism.

Provider eligibility, models, rates, and processing terms can change. Jobber shows the current connection details before you enable it.

Usage and cost controls

Every assisted task has bounded context, output, retries, duration, and concurrency. Personal provider usage is shown as provider-reported, estimated, or unavailable. Jobber AI reserves from a hard monthly allowance before a task begins and releases unused capacity after it finishes. When the allowance is exhausted, hosted tasks stop without creating an overage charge.

Changing or disconnecting a provider

Changing providers affects new tasks only. Existing local documents, evaluations, and application history remain in your workspace. Before disconnecting, Jobber explains any tasks in progress and lets you cancel or finish them. Credentials are removed from Keychain or the provider session without deleting local career data.