Ofte stillede spørgsmål

Er PRECC sikkert at bruge?

Ja. PRECC bruger den officielle Claude Code PreToolUse hook-mekanisme – det samme udvidelsespunkt som Anthropic har designet til netop dette formål. Hook:

• Kører helt offline (ingen netværkskald i den kritiske sti)
• Fuldfører på under 5 millisekunder
• Er fail-open: hvis noget går galt, køres den originale kommando uændret
• Ændrer kun kommandoer, udfører dem aldrig selv
• Gemmer data lokalt i SQLite-databaser

Virker PRECC med andre AI-kodningsværktøjer?

PRECC er designet specifikt til Claude Code. Det bruger PreToolUse hook-protokollen fra Claude Code. Det virker ikke med Cursor, Copilot, Windsurf eller andre AI-kodningsværktøjer.

Hvilke data sender telemetrien?

Telemetri er kun opt-in. Når aktiveret, sender den:

• PRECC-version, OS og arkitektur
• Aggregerede tællinger (opfangede kommandoer, aktiverede færdigheder)
• Gennemsnitlig hook-latens

Den sender ikke kommandotekst, filstier, projektnavne eller personligt identificerbare oplysninger. Du kan forhåndsvise den nøjagtige payload med precc telemetry preview før tilmelding. Se Telemetry for alle detaljer.

Hvordan afinstallerer jeg PRECC?

PRECC is fully reversible — remove it in three steps:

1. Fjern hook-registreringen:

   # Delete the hook entry from Claude Code's settings
   # (precc init added it; removing it disables PRECC)
   

2. Fjern binærfilen:

   rm ~/.local/bin/precc ~/.local/bin/precc-hook ~/.local/bin/precc-learner
   

3. Fjern data (valgfrit):

   rm -rf ~/.local/share/precc/
   rm -rf ~/.config/precc/
   

Min licens er udløbet. Hvad sker der?

PRECC vender tilbage til Community-niveauet. Al kernefunktionalitet fortsætter med at virke:

• Indbyggede færdigheder forbliver aktive
• Hook pipeline kører normalt
• precc savings viser oversigtvisningen
• precc ingest og sessionsanalyse virker

Pro-funktioner bliver utilgængelige indtil fornyelse:

• precc savings --all (detaljeret oversigt)
• precc compress
• precc gif
• precc gha
• precc geofence
• E-mail-rapporter

Hook ser ikke ud til at køre. Hvordan fejlfinder jeg?

Run precc doctor first — it automates every check below. To diagnose by hand:

1. Kontroller at hook er registreret:

   precc init
   

2. Test hook manuelt:

   echo '{"tool_input":{"command":"cargo build"}}' | precc-hook
   

3. Kontroller at binærfilen er i din PATH:

   which precc-hook
   

4. Kontroller Claude Codes hook-konfiguration i ~/.claude/settings.json.

Gør PRECC Claude Code langsommere?

Nej. Hook fuldfører på under 5 millisekunder (p99). Dette er umærkeligt sammenlignet med den tid, Claude bruger på at ræsonnere og generere svar.

Kan jeg bruge PRECC i CI/CD?

PRECC er designet til interaktive Claude Code-sessioner. I CI/CD er der ingen Claude Code-instans at tilslutte. Dog kan precc gha analysere fejlede GitHub Actions-kørsler fra ethvert miljø.

Hvordan adskiller lærte færdigheder sig fra indbyggede?

Indbyggede færdigheder leveres med PRECC og dækker almindelige forkert-mappe-mønstre. Lærte færdigheder udvindes fra dine specifikke sessionslogfiler – de fanger mønstre unikke for din arbejdsgang. Begge gemmes i SQLite og evalueres identisk af hook pipeline.

Kan jeg dele færdigheder med mit team?

Ja. Eksporter enhver færdighed til TOML med precc skills export NAME og del filen. Teammedlemmer kan placere den i deres skills/-mappe eller importere den i deres heuristikdatabase.

Why do I see zero tokens saved?

If precc savings reports 0 tokens despite an active Claude Code session burning input/output tokens, the hook is not firing. Three causes account for almost every reported instance:

1. You are on v0.3.42 or v0.3.43. These releases shipped a data-path regression where the hook wrote metrics to a directory that the CLI then read from a different directory — both ran, but the savings number stayed at 0. Fixed in v0.3.44 (data paths routed through db::data_dir()). Upgrade with:

   precc update
   

2. Your settings.json is missing the hook entry. Run precc doctor (available in v0.3.53+). It checks each precondition of the hot path — settings file, hook entry, binary on $PATH, heuristics DB, recent invocations — and reports the first one that fails:

   precc doctor
   

   If doctor is not available because you are on an older release, run precc init to (re)register the hook.

3. Your session has not yet hit a skill trigger. PRECC only intercepts Bash commands matching one of the active skills. If your session has been pure file editing or pure web fetching against domains not covered by webfetch-opencli, you have not yet given the hook anything to compress or rewrite. This is normal. Run precc skills list to see what triggers exist.

If after upgrading and running precc doctor you still see zero savings, file an issue at https://github.com/peri-a-i/precc-cc/issues with the output of precc doctor.

My MCP server (e.g. lean-ctx) is pegging CPU. How do I kill it safely without taking Claude Code down with it?

PRECC does not ship or supervise MCP servers — but this is a recurring trap because some MCP binaries (notably lean-ctx) are also invoked as per-Bash-tool-call wrappers by the Claude Code harness, not just as long-running servers. A naive pkill <name> then matches many short-lived wrappers in addition to the server.

Identify the runaway PID, do not kill by name:

pgrep -f "^lean-ctx$" \
  | xargs -I{} ps -o pid,%cpu,etime,args -p {} \
  | sort -k2 -nr | head -3

The top row is the long-running server (large etime, high %cpu). Send SIGTERM to only that PID:

kill -TERM <pid>

Avoid these forms, all of which can also kill Claude Code or break in-flight tool calls:

• pkill lean-ctx — matches transient lean-ctx -c <cmd> wrappers spawned per Bash tool call.
• pkill -9 -f lean-ctx — same broad match, plus ungraceful exit leaves the MCP stdio half-open.
• pkill -g <pgid> / kill -- -<pgid> — kills the whole process group, which includes claude itself when the MCP server shares a session with it.

If after a clean SIGTERM the server does not exit within a few seconds, escalate with kill -KILL <pid> on the same single PID (still not by name). Claude Code will lose those MCP tools until you restart it; it should not exit on its own.

This advice is independent of PRECC — but PRECC users frequently run lean-ctx, so it is worth documenting here.

What is OpenCLI and do I need it?

OpenCLI is a third-party Node.js tool that turns ~148 websites into structured-output CLI commands (opencli hackernews top, opencli reddit search <q>, opencli arxiv search <q>, …). PRECC ships two built-in skills that work with it:

• webfetch-opencli-hint — fires on curl/wget/http/fetch against any of 11 OpenCLI-supported domains and suggest_fix-es the equivalent opencli <site> … command. Suggestion only; never modifies the command.
• webfetch-opencli-hackernews — auto-rewrites curl|wget news.ycombinator.com to opencli hackernews top with an inline command -v opencli fallback to the original command if OpenCLI isn’t installed.

You don’t need OpenCLI for PRECC to work. The hint skill costs nothing; the auto-rewrite skill is safe to ship default-on because of the fallback.

If you want OpenCLI’s WebFetch token savings, install it with:

precc init --opencli

That runs npm install -g @jackwener/opencli (Node.js 20+ required). For cookie-reuse on logged-in pages, also install OpenCLI’s Chrome extension separately — see the project README. The extension requests broad permissions (debugger, <all_urls>, cookies); review them before installing.

precc doctor reports OpenCLI’s presence on $PATH as an informational line:

i opencli: installed (webfetch-opencli skills will auto-rewrite)

or

i opencli: not installed (run `precc init --opencli` if you want WebFetch token savings)

Never marks doctor as failing — the integration is fully opt-in.