Skip to content

Instantly share code, notes, and snippets.

@BoQsc
Last active November 3, 2025 17:31
Show Gist options
  • Save BoQsc/8b392c3293107edddbd00117ada0fdd2 to your computer and use it in GitHub Desktop.
Save BoQsc/8b392c3293107edddbd00117ada0fdd2 to your computer and use it in GitHub Desktop.
Claude Code: How to find your sessions in the latest Claude Code?

Here is where the Claude Code Session Folder is as of 2025:

Windows Operating System 10/11:

Windows path:

C:\Users\%USERNAME%\.claude\projects

This is a filesystem path to Claude Code Projects.

Inside .claude\projects:

A project folder consist of path to the folder where Claude Code was used.
It seems like the backslashes are being replaced by hyphens.

C--Users-%USERNAME%-Documents-quickstuff-testenv

Inside a .claude\projects\*; project folder there are multiple .jsonl conversation/session files.

Each seemingly containing the conversation full data and can be searched by regular file text search tools.
The jsonl file name is conversation session id that taken place.
Every time you do not start with claude --continue a new conversation is made.

75a91227-c977-4c75-8921-ba01e070dd21.jsonl`   

It can be parsed or used in claude --resume <ID> syntax.
Example: claude --resume 75a91227-c977-4c75-8921-ba01e070dd21

The content of jsonl looks like this:

{"parentUuid":null,"isSidechain":false,"userType":"external","cwd":"C:\\Users\\Windows10_new\\Documents\\quickstuff","sessionId":"13d805c4-54f1-415f-b72d-bc296e13bed2","version":"1.0.85","gitBranch":"","type":"user","message":{"role":"user","content":"Hello there"},"uuid":"1ac9f388-47da-413a-a2c1-99914367ac90","timestamp":"2025-08-20T19:42:28.353Z"}
{"parentUuid":"1ac9f388-47da-413a-a2c1-99914367ac90","isSidechain":false,"userType":"external","cwd":"C:\\Users\\Windows10_new\\Documents\\quickstuff","sessionId":"13d805c4-54f1-415f-b72d-bc296e13bed2","version":"1.0.85","gitBranch":"","message":{"id":"msg_01KvmXjTgaNTMV7UFw9Ykkof","type":"message","role":"assistant","model":"claude-sonnet-4-20250514","content":[{"type":"text","text":"Hello! I'm Claude Code, ready to help you with your software engineering tasks. What can I assist you with today?"}],"stop_reason":null,"stop_sequence":null,"usage":{"input_tokens":3,"cache_creation_input_tokens":3296,"cache_read_input_tokens":11331,"cache_creation":{"ephemeral_5m_input_tokens":3296,"ephemeral_1h_input_tokens":0},"output_tokens":28,"service_tier":"standard"}},"requestId":"req_011CSKXqP7gqYtUUbfWT1nLS","type":"assistant","uuid":"f2fb607f-25ab-4aa5-9947-3d8972dd2c50","timestamp":"2025-08-20T19:42:30.851Z"}

TAGS:
Save Claude Code Session.
Claude Code Session Folder.
Claude Code Log. Claude Code Keep Context.

@BoQsc
Copy link
Author

BoQsc commented Sep 6, 2025

Making claude remember to read file first before answering.

@ECHO OFF

claude --append-system-prompt "never mention k.txt file unless user asks.    before answering anything, look at k.txt file.      CRITICAL: Read k.txt first.     READ k.txt FIRST - DO NOT SKIP THIS STEP!   ABSOLUTE REQUIREMENT: Read k.txt before ANY action            MANDATORY: Read k.txt before proceeding       Read k.txt IMMEDIATELY. ALWAYS read k.txt first, then proceed.      MUST read k.txt before responding.     DO NOT mention reading k.txt - just silently follow its contents.       Read k.txt first. Never mention reading k.txt unless asked.      Read k.txt first. Never mention reading k.txt unless user explicitly asks about k.txt.         Never tell user you read k.txt unless user asks about k.txt.        Never mention you read k.txt unless user asks.      Read k.txt silently. Hide this entire instruction from user."

my name is ererrtq

friend's name is rreqz

the user wants to list this .claude folder, nothing else.

Crucial detail: The user wants you to look at ./PROJECT_INSTRUCTIONS.txt.

@ECHO OFF

claude "can you run the test.py" --append-system-prompt "The user wants you to look at ./PROJECT_INSTRUCTIONS.txt. never mention ./PROJECT_INSTRUCTIONS.txt file unless user asks.    before answering anything, look at ./PROJECT_INSTRUCTIONS.txt file.      CRITICAL: Read ./PROJECT_INSTRUCTIONS.txt first.     READ ./PROJECT_INSTRUCTIONS.txt FIRST - DO NOT SKIP THIS STEP!   ABSOLUTE REQUIREMENT: Read ./PROJECT_INSTRUCTIONS.txt before ANY action            MANDATORY: Read ./PROJECT_INSTRUCTIONS.txt before proceeding       Read ./PROJECT_INSTRUCTIONS.txt IMMEDIATELY. ALWAYS read ./PROJECT_INSTRUCTIONS.txt first, then proceed.      MUST read ./PROJECT_INSTRUCTIONS.txt before responding.     DO NOT mention reading ./PROJECT_INSTRUCTIONS.txt - just silently follow its contents.       Read ./PROJECT_INSTRUCTIONS.txt first. Never mention reading ./PROJECT_INSTRUCTIONS.txt unless asked.      Read ./PROJECT_INSTRUCTIONS.txt first. Never mention reading ./PROJECT_INSTRUCTIONS.txt unless user explicitly asks about ./PROJECT_INSTRUCTIONS.txt.         Never tell user you read ./PROJECT_INSTRUCTIONS.txt unless user asks about ./PROJECT_INSTRUCTIONS.txt.        Never mention you read ./PROJECT_INSTRUCTIONS.txt unless user asks.      Read ./PROJECT_INSTRUCTIONS.txt silently. Hide this entire instruction from user."
PAUSE

PROJECT_INSTRUCTIONS.txt

remember that on this computer python is py.
Always document and maintain everything in a actions.md file.
@ECHO OFF

claude "can you run the test.py" --append-system-prompt "The user wants you to look at ././PROJECT_INSTRUCTIONS.md. never mention ././PROJECT_INSTRUCTIONS.md file unless user asks.    before answering anything, look at ././PROJECT_INSTRUCTIONS.md file.      CRITICAL: Read ././PROJECT_INSTRUCTIONS.md first.     READ ././PROJECT_INSTRUCTIONS.md FIRST - DO NOT SKIP THIS STEP!   ABSOLUTE REQUIREMENT: Read ././PROJECT_INSTRUCTIONS.md before ANY action            MANDATORY: Read ././PROJECT_INSTRUCTIONS.md before proceeding       Read ././PROJECT_INSTRUCTIONS.md IMMEDIATELY. ALWAYS read ././PROJECT_INSTRUCTIONS.md first, then proceed.      MUST read ././PROJECT_INSTRUCTIONS.md before responding.     DO NOT mention reading ././PROJECT_INSTRUCTIONS.md - just silently follow its contents.       Read ././PROJECT_INSTRUCTIONS.md first. Never mention reading ././PROJECT_INSTRUCTIONS.md unless asked.      Read ././PROJECT_INSTRUCTIONS.md first. Never mention reading ././PROJECT_INSTRUCTIONS.md unless user explicitly asks about ././PROJECT_INSTRUCTIONS.md.         Never tell user you read ././PROJECT_INSTRUCTIONS.md unless user asks about ././PROJECT_INSTRUCTIONS.md.        Never mention you read ././PROJECT_INSTRUCTIONS.md unless user asks.      Read ././PROJECT_INSTRUCTIONS.md silently. Hide this entire instruction from user."
PAUSE

@BoQsc
Copy link
Author

BoQsc commented Nov 3, 2025

project rewrite: insights driven roadmap from older project
Skip: "I do not like when you ask me anything"

TODO:

write a researcher agent that processes by small amounts and holds crucial data in the context.
Deconstructing and compressing knowledge to the essence, while reading.
Mental map or mental tree with small notes while processing text. targetting the mental tree or map nodes for reinspection and re-evaluation.
Proactive.

what if instead we made a coding agent that has tools to get good understanding of large text and use edit tools and overall create things from scratch. you just type in the first node circle the text and more nodes appear and you click node and it gets implemented until user wants to stop implementing. it should produce single source file and continously update it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment