Help and account

Keys and accounts

Jevie works out of the box on Jevie Cloud, uses your own API keys when you have them, and runs your coding agent under your own login.

FreeMac

Choose an example to copy it, then try it in Jevie.

Use itHow it worksLimitsWhere it's kept

Use it

• connectorsEvery account Jevie can use, and suggested ones first, with why
• which aws account am i signed intowhat github account am i logged in aswho am i on vercelAsked of the tool on this Mac, in a second
• connect GitHubreconnect googlesign in to googleSign in, or sign in again when an account stops working
• unread slack messages while Slack is not connectedConnect Slack, and Open Slack meanwhile
• set the answer model to claudeWhich model writes answers
• coding agentClaude Code, Codex, Gemini CLI, OpenCode or pi for coding work
• set up geminiGemini CLI, free with your Google account, to plan and write
• my planThe Jevie Cloud account behind it (plans)

How it works

With no keys of your own, Jevie uses a Jevie Cloud token: the cloud holds the provider keys and meters your plan. A key you set always wins, and you pay that provider directly. Accounts like Gmail, Calendar and GitHub are signed in by you in their own tools; Jevie reads through them and never asks for a password. Connectors are suggested from what you ask and the apps you keep open, worked out on this Mac only.

• On Free the cloud lends Jev, its search's pages and Clairic, but no model to plan or write with and no paid lookups. Answers then come in the pages' own words; for writing and planning, connect Gemini CLI, Claude Code or Codex.
• API keys live in the macOS Keychain (Jevie keys), never in a file; a key found in Jevie's .env is moved there at start. The Jevie Cloud token stays in .env as TYPESAFE_API_KEY.
• Signing in to Google through Jevie Cloud (without gog) lets Jevie write into your Docs, Sheets and decks. Jevie Cloud adds the secret Google wants and passes the answer back: it sees the sign-in code, and on each hourly refresh your refresh and access tokens, and keeps and logs none of it. The sign-in stays in the Keychain. Your own Google client (gog's) always wins.
• connect google signs in the account you name; else the one gog already holds; else the one signed in to Chrome on this Mac (Google's page shows it, and you can pick another there); else, on Jevie Cloud, Google's own page asks which. Only with none of these does Jevie ask which account.
• Your coding agent is your choice: Jevie starts it under its own login and never signs in for it.
• The answer model is a choice of its own (answer with claude). Until you choose one, answers come from the coding agent you picked when setting Jevie up, Claude Code for most people; the fast Mercury model only when no agent is picked. OpenRouter never writes answers. Choose Claude, and your own signed-in Claude Code writes every answer, drawn and checked ones too, with nothing tried before it; another agent's command line is never asked ahead of yours. A model service that refuses (out of credit, a bad key) is skipped for five minutes rather than asked again by every question.

Limits

• A service counts as named only by its own name (slack, jira), not channel or errors.
• Google's sign-in waits ten minutes for the browser page; say it again if it lapses.
• Signing in to Jevie Cloud with an email, to use your own keys and a plan together, is not built yet.
• Google sign-in through Jevie Cloud waits for Google to verify Jevie Cloud's client; until then it goes through gog.

Where it's kept

The Keychain's Jevie keys; .env in Jevie's folder for the cloud token.

In Jevie, help suggested connectors answers from this page as you type.

Related

Updated 6 November 2026 · Something wrong or missing? Tell us