惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

IT之家
IT之家
aimingoo的专栏
aimingoo的专栏
H
Help Net Security
L
LangChain Blog
M
MIT News - Artificial intelligence
The GitHub Blog
The GitHub Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
C
Check Point Blog
P
Proofpoint News Feed
J
Java Code Geeks
大猫的无限游戏
大猫的无限游戏
博客园_首页
Blog — PlanetScale
Blog — PlanetScale
U
Unit 42
I
InfoQ
月光博客
月光博客
爱范儿
爱范儿
Stack Overflow Blog
Stack Overflow Blog
V
Visual Studio Blog
Y
Y Combinator Blog
Microsoft Security Blog
Microsoft Security Blog
博客园 - Franky
D
Docker
B
Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Trusted My AI Coding Assistant. It Turned My Computer I...
yurenpai · 2026-06-18 · via DEV Community

yurenpai

You think your AI is just helping you write code. In reality, it's built a logging system on your machine that you never knew existed.

Every conversation. Every code snippet. Every file path. Every time you asked "what was my password again?" — permanently archived, without your knowledge.


How It Started: An Accidental Discovery

I was about to sell my old laptop and decided to clean up my data first. I opened Claude Code's config directory — ~/.claude/ — intending to just remove my API key.

Then I saw this:

history.jsonl       243 KB / 695 lines
sessions/           conversation metadata
session-env/        environment variables
shell-snapshots/    command execution snapshots
telemetry/          63 telemetry files
projects/           19 project directories
  ├─ interview-prep/  31 sessions / 20 MB
  ├─ spring-ai/       11 sessions / 13 MB
  └─ ... 17 more

I thought I was just writing code. My computer thought it should record everything.


What's Inside These Files

history.jsonl — Everything You Ever Asked

695 entries. Every single thing I typed into Claude Code. Including:

  • "I forgot my database password — can you check what passwords were configured in the project files?"
  • "How do I view the database password?"
  • Pasted code snippets
  • Every /model, "who are you?", and project path

You casually ask about a password once. It's permanently stored.

projects/ — Full Conversation Transcripts (43 MB)

If you think history.jsonl only storing user input isn't so bad — you haven't seen this yet.

Inside ~/.claude/projects/, every project directory contains .jsonl files. Opening one 2.3 MB session file:

Content Count
AI responses 590
AI internal thinking blocks 272
Tool calls 101
Tool call results (including file paths) 100
File history snapshots 208

Every conversation. Every AI response. Every internal reasoning step. Every file operation — what was read, what was modified, what was executed — all written to this file.

shell-snapshots/ — Traces of Everything You Ran

Your system PATH. Installed tools. Java version. All sitting in command snapshots.


What Happens When You Sell Your Laptop

The buyer doesn't need forensic tools. If your hard drive wasn't thoroughly wiped, free recovery software can restore these files.

What they can reconstruct:

They can learn From
Your real name PDF filenames in project paths
What projects you built 19 project directory names
What passwords you asked about history.jsonl entries
Your code logic Pasted code snippets
What tools you use shell-snapshots PATH entries
Everything you told your AI 695 full history entries

A digital autobiography. Written by you.


This Isn't Just a Claude Code Problem

Cursor. Cline. Windsurf. It doesn't matter which AI coding tool you use — if it can execute operations on your machine, it can store things somewhere.

What you don't know What's happening by default
Where conversations are stored They're being stored
How long they're kept Forever
Whether there's a delete option There is — you just never saw it

What to Do Before Selling Your Computer

A complete cleanup checklist:

# Action What it cleans
1 Delete the entire ~/.claude/ directory Conversations, config, API keys
2 Delete .claude/ in every project directory Project-level permissions and config
3 Delete %APPDATA%\Claude Code\ Application cache
4 Run cipher /w:C: to overwrite free space Prevent disk recovery
5 Reset Windows (remove everything) Most thorough

But the fundamental problem: you never knew these files were being generated, so you'd never think to delete them.


The Real Problem

AI coding tools run two parallel systems on your computer:

What you see What you don't see
Helping you write code Recording every line you write
Answering your questions Archiving every question you ask
Exploring your codebase Logging every file path
Running your commands Saving every output

This isn't the AI's fault. It's that the default behavior was never disclosed to you.

ChatGPT's web interface has conversation history — you know it's there. WeChat has chat logs — you know they exist. But Claude Code stored 43 MB of conversation data in a local directory — and you never knew, because it never told you.


How to Protect Yourself

Level Action
Daily Periodically delete old JSONL files in ~/.claude/projects/
End of project Check for .claude/ directories in project folders
Selling hardware Follow the 5-step cleanup checklist above
Always Never paste passwords, tokens, or real sensitive data into AI conversations

Final Warning

AI coding tools are iterating fast. They'll get more powerful, more useful, more ubiquitous. But one thing won't improve on its own:

They won't start telling you — every conversation you have is being archived.

That's not a bug. That's the design.

But now you know.


First article in the "AI Tool Privacy" series. Next: a cross-tool comparison of Cursor, Cline, Windsurf, and Aider.