Credentials

The agent signs in to job boards as you, so it needs your board logins. It can also use a captcha-solving service for image challenges. Both live under Settings → Credentials.

Board logins

Add a credential per board domain: linkedin.com, indeed.com, and so on. When a board asks the agent to sign in, it looks up the credential for that domain and logs in before searching or applying. A credential with scope default is the fallback for boards without their own entry, useful if you reuse one email across boards.

Boards that send verification codes during sign-in are covered too: with email connected, the agent reads the code from your mailbox and continues on its own.

Captcha services

The agent solves simple captchas itself: checkboxes and distorted text. Image-grid challenges (reCAPTCHA, hCaptcha, Turnstile) need a token service. Add an API key for 2Captcha or CapSolver under Settings → Credentials and the agent falls back to it automatically; without a key it skips the job and tells you why.

How secrets are stored

Every secret (board passwords, captcha keys, your Gmail OAuth secret and tokens) is encrypted at rest with a key that belongs to your account alone. Deleting your account destroys that key, which makes the stored secrets unreadable. Secrets are decrypted only server-side when the agent needs them; they never appear in the dashboard after you save them.

Auto-apply defaults

These three live one tab over, under Settings → Profile, and apply to every auto-apply campaign:

• Min match score (0-100): jobs scoring below it are skipped.
• Max applications per campaign: the hard cap for one auto-apply run. This is separate from the Pilot's daily apply cap, which limits how many applications go out per day across everything.
• Default start date answer: the answer used for "When can you start?" fields.

Next up: the FAQ.