Sign in to your AI

A one-time sign-in that lets HISAB use your own AI account — Anthropic Claude (Claude Code) or OpenAI Codex — in Own-AI mode. Usage is billed to you by the provider with no markup. Using the built-in HISAB AI instead? No AI sign-in is needed at all — this page doesn't apply.

Where sign-in lives

Sign-in is a card in the HISAB Settings panel. The Claude and Codex engines were installed automatically with HISAB, so there is nothing to install first — just open Settings and sign in from the card. Each step also has a Copy command button so you can paste the exact command into a terminal yourself — running it from your own shell (not from Excel) keeps endpoint-security software from blocking it.

Signing in

On the sign-in card, click Sign in (Claude) or Sign in to OpenAI (Codex) — or use the Copy command button — and HISAB opens your browser to authenticate. Don't hand-type a bare login command; each engine needs a little setup the button handles for you —

Claude: adds Claude's install folder to your PATH (so a freshly-opened terminal can find claude), then signs in through your browser.
Codex: runs set CODEX_HOME=%APPDATA%\HISAB\codex-home && codex login, so the sign-in lands in HISAB's isolated Codex home — a bare codex login writes elsewhere and HISAB won't see it. You can alternatively set the OPENAI_API_KEY environment variable.

Each CLI asks how you want to authenticate — a subscription (a Claude or ChatGPT plan; strongly recommended, far more usage per dollar) or a pay-as-you-go API key. Accept the requested permissions; the browser shows a success page you can close.

What HISAB stores

The sign-in writes credentials owned by your Windows user — under ~/.claude for Claude, or HISAB's isolated %APPDATA%\HISAB\codex-home for Codex. HISAB never stores your AI credentials itself and never resells AI: it delegates auth entirely to the CLI, which handles token refresh. Usage is billed to you by Anthropic or OpenAI.

Verify

Back in the Settings card, click Verify sign-in (for Codex, Verify Codex). HISAB confirms the engine is installed, wires its tools into the CLI's config, and checks that you're signed in — all without restarting Excel (it reads the live PATH and the bundled-Node location). If the check says it can't detect the sign-in, the most common cause is closing the browser before the callback finished — run the command again, then click Verify.

The MCP pill

At the top of the Chat tab is the MCP pill — it shows the live link between your AI CLI and HISAB's local server. It is amber while idle and turns green once your engine has connected and is exchanging tool calls. Green means HISAB is ready to read and write your workbook on the AI's behalf.

Switching between Claude and Codex

Settings has a Claude / Codex radio toggle (Claude is the default). You can install and keep both engines and flip between them any time — the change takes effect on your next message. To switch the account within an engine, sign out of that CLI and sign back in using the panel's Sign in / Copy command button — it runs the right command for each engine. HISAB picks up the new identity on its next call.

Browser didn't open when you clicked Sign in?

The Sign in button normally opens your browser straight to the provider's authorization page and the sign-in completes automatically — there is no code to copy or paste. If the browser doesn't appear, click Sign in again, or use the card's Copy command button to run the same login from a terminal; it re-opens the browser and authorizes automatically.

Only if you ran a login by hand in a terminal and it asks for a pasted code: Windows consoles often sit in QuickEdit mode, which blocks input — click once inside the console (or press Esc), then paste. Using the panel button avoids this entirely.

One device at a time (your HISAB license)

Separately from your AI sign-in, your HISAB account is a floating single session: you can sign in on any number of devices, but only one is active at a time. Signing in on a second machine takes over the session, and the first machine returns to its login screen on its next check-in. A signed offline grace window (about 7 days) keeps brief offline use working. The 15-day free trial is once per machine — reinstalling does not reset it.