Help · Setup
One tool at a time.
No rush.
Quotchi finds your tools on its own. If one says “needs setup”, here’s exactly what it’s waiting for. You only need the tools you actually use.

Start with the setup check
Open the panel (click the sloth in your menu bar), then the gear → AI tools → Run setup check. For each tool it checks three things: found, signed in, and a test read. When something is missing it says what, and offers Copy command for the one Terminal line that fixes it. It never asks for a password.
Run it again after you fix something with Check again.
Claude Code
Quotchi reads your Claude plan limits through Claude Code, the command-line tool. You need Claude Code 2.1 or later, signed in with your Claude Pro or Max subscription (not an API key).
- Install Claude Code if you haven’t: follow Anthropic’s setup guide. Homebrew, npm, nvm, Volta, Bun and the native installer are all found automatically.
- Sign in once. Run
claudein Terminal and sign in with the same account you use in the Claude app. The Claude app and Claude Code keep separate sign-ins, so being signed in to the app isn’t enough. Or use Quotchi’s Sign in to Claude Code button: it opens Terminal with the sign-in command and notices when you’re done. - Refresh in the panel. Your 5-hour and weekly windows appear with their reset times.
Checking usage doesn’t send a prompt or use your allowance. Some model-specific limits may not be reported; Quotchi labels them as unknown rather than guessing.
Codex
You need the Codex CLI 0.160 or later, signed in with your ChatGPT account.
- Install the Codex CLI (
npm install -g @openai/codex, or your usual package manager). - Sign in with ChatGPT: run
codex loginand choose Sign in with ChatGPT. API-key sign-ins have a separate allowance, so there are no plan limits to show. - Refresh in the panel.
The Codex desktop app on its own isn’t enough: Quotchi needs the CLI that it can run.
Only use the Claude app?
No Claude Code, or it’s signed out? Quotchi can read the session and weekly bars from the Claude desktop app instead.
- In Settings → AI tools → Claude, open More ways to connect and turn on Read the Claude app’s Usage page.
- Allow Quotchi in Accessibility when macOS asks.
- In the Claude app, open Settings → Usage and leave it open (it can sit behind other windows). The page must be in English.
Quotchi only reads the usage bars. It never clicks, types or reads chats. When Claude Code has its own reading, that one always wins.
Import your Claude app history
Turn on Import history from the Claude app in Settings → AI tools → Claude → More ways to connect to add your past session and weekly percentages to History. Quotchi reads one local file the Claude app keeps and ignores everything else in it, including your account ID. No permission is needed, it never changes the current reading, and you can remove imported history at any time. History itself is a Pro feature.
Gemini
Quotchi can read usage from the Gemini Mac app (not the Gemini CLI).
- In Settings → AI tools → Gemini, turn on Read the Usage limits pane.
- Allow Quotchi in Accessibility.
- In Gemini, open Settings → Usage limits and keep that pane open. It must be in English.
You get app usage only: Gemini doesn’t show reset times or token counts there. If the numbers look old, refresh inside Gemini.
The Accessibility permission
Only the optional Claude app and Gemini readers need it. Claude Code, Codex, alerts, widgets and the keyboard shortcut don’t.
- Open System Settings → Privacy & Security → Accessibility (the reader’s card has an Open Accessibility Settings button).
- Switch on Quotchi. If it isn’t listed, click + and choose Quotchi from Applications.
- Back in Quotchi, choose Refresh.
Changed your mind? Turn the reader off in Quotchi and switch Quotchi off in that same Accessibility list.
Show or hide tools
Each tool in Settings → AI tools has a menu: Automatic shows it when it’s found, Show keeps it visible even before setup, and Hide removes it. Hidden tools aren’t checked at all.
Still stuck?
Write to [email protected]. A real person reads every email (that’s Thomas). Here’s what to include so we can help on the first reply.
