One KeepClaw CLI login for Claude Code, Hermes Agents, OpenClaw, and OpenCode
Authenticate with `npx @keepclawai/cli login`, complete the browser handshake once, and reuse that KeepClaw session across supported local clients while credits and activity stay visible in the dashboard.
Authenticate with NPM CLI
Run the KeepClaw CLI login command once, then keep using the same local session across supported clients.
npx @keepclawai/cli loginCopy the command and run it in your local environment.
Supported Clients
Built for the local clients already in your workflow
KeepClaw CLI access focuses on the tools shown in the dashboard today: Claude Code, Hermes Agents, OpenClaw, and OpenCode.
Claude Code
CLI session reuse
Authenticate once with the KeepClaw CLI, then continue working inside Claude Code with the same local session.
Hermes Agents
CLI session reuse
Keep agent runs tied to one KeepClaw wallet and one visible usage history instead of separate local credentials.
OpenClaw
CLI session reuse
Use the same KeepClaw login session across local OpenClaw workflows without copying dashboard tokens around.
OpenCode
CLI session reuse
Keep model access, billing, and activity visibility consistent when OpenCode joins the same local toolchain.
Why This Matters
The local auth layer is where setup usually becomes fragile
KeepClaw is not asking teams to manage more secrets. It is reducing the amount of auth work they repeat across local clients.
Manual token handoff is brittle
Copying secrets between local tools, machines, and teammates creates avoidable setup friction and rotation risk.
Onboarding every client repeats auth work
Without a CLI-first flow, each supported client ends up with its own setup path and its own room for mistakes.
Credits and history get harder to read
When external tools authenticate in different ways, it becomes harder to review spend, remaining balance, and recent activity in one place.
KeepClaw as the access layer
Unify login, credits, and visibility without inventing a second setup flow
Instead of handing each client a different token or provider key, you authenticate once through KeepClaw and keep the resulting session, remaining credits, and CLI activity history in one dashboard surface.
How It Works
Three steps from dashboard to your local client
The flow now mirrors the dashboard experience: one CLI command, one browser sign-in, then reuse the session where you work.
01
Run the CLI command
Start with `npx @keepclawai/cli login` from your local environment instead of copying a manual token.
02
Finish the browser sign-in
Complete the KeepClaw browser handshake once so the local session is authenticated and ready to reuse.
03
Open your supported client
Claude Code, Hermes Agents, OpenClaw, and OpenCode can all reuse that KeepClaw session from the same machine.
What's Included
KeepClaw provides the CLI entry point and the visibility around it
The goal is to make supported-client access predictable while keeping credits, remaining balance, and history visible inside KeepClaw.
NPM CLI login flow for supported local clients
One reusable KeepClaw session across Claude Code, Hermes Agents, OpenClaw, and OpenCode
Remaining credits with subscription and top-up breakdown in the dashboard
History log for CLI login and request activity
Copyable CLI command directly from the dashboard access page
FAQ
Questions teams usually ask before switching to the CLI-first flow
This page stays focused on the product direction and setup clarity. Day-to-day credits and activity remain in the dashboard.
Use one KeepClaw CLI login across your supported local AI tools
Keep setup, credits, remaining balance, and CLI history inside KeepClaw while Claude Code, Hermes Agents, OpenClaw, and OpenCode reuse the same authenticated local session.