chyroc

Claude Code Reset — Development skill for Claude Code

Development community

Backup-first CLI to inspect and reset Claude Code local state (credentials, account/billing cache, telemetry, backups) on Linux/macOS.

How to install Claude Code Reset

This entry records only its repository, not the path inside it, so there is no exact command to give. Open chyroc/claude-code-reset and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Reset does

Backup-first CLI to inspect and reset Claude Code local state (credentials, account/billing cache, telemetry, backups) on Linux/macOS. Zero dependencies, fully offline.

Alternatives in Development

  • Backup 14.5k ★
  • Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
  • Memory Gc — Inspect or rotate the autopilot ledger JSONL files (findings.jsonl, negatives.jsonl) 3.8k ★

README

ccreset — Claude Code local state reset (CLI)

A tiny, **zero-dependency** Node.js CLI for inspecting and resetting the **local** data that [Claude Code](https://claude.com/claude-code) stores on your own machine — login credentials, cached account/entitlement state, the telemetry event buffer, and auto-backups.

It is the command-line equivalent of "sign out and clear the app's local data / do a clean reinstall", without reinstalling anything. Linux and macOS.

**What this is not.** It only manages files under your own `~/.claude` / `~/.claude.json`. It does **not** modify network, DNS, timezone, browser, or proxy settings, does not spoof identifiers (it simply deletes them so the official client regenerates its own), makes **zero network calls**, and contains no license server or telemetry of its own.

Why

Claude Code keeps several kinds of local state that a normal "log out" may not fully clear:

  • OAuth tokens in ~/.claude/.credentials.json
  • Account / identity / entitlement cache in ~/.claude.json (oauthAccount, userID, machineID, firstStartTime, numStartups, passesEligibility, extraUsage, metrics)
  • Unsent analytics events buffered in ~/.claude/telemetry/
  • Automatic backups in ~/.claude/backups/ that may contain plaintext copies of older state

`ccreset` lets you see exactly what's there, clear just the groups you want, and **automatically snapshots everything first** so a reset is reversible.

Install

Requires Node.js 18+.

git clone https://github.com/chyroc/claude-code-reset.git
cd claude-code-reset
npm link          # makes the `ccreset` command available
# …or run directly without linking:
node bin/ccreset.js status

Usage

ccreset status                     Show what local state exists (default, read-only)
ccreset reset [groups] [flags]     Reset selected groups (dry run without --apply)
ccreset snapshots                  List auto-created snapshots
ccreset restore         R