今日已更新 123 条资讯 | 累计 42534 条内容
关于我们

"Keeping a record: working across many sessions"

Lisandro Reinoso 2026年09月13日 05:29 1 次阅读 来源:Dev.to

Day one closed in the small hours and day two started half an hour later, with a short session that didn't touch the product: it defined how sessions would be named, where they would be recorded, and which script would close them on its own. The problem it solved wasn't one of order but of continuity. Every conversation with Claude Code ends, and I wanted to be able to work across many of them —open one, close it, come back the next day or from another project— without losing what had been decided in the previous one. With some distance, it is one of the sessions that weigh the most of all the ones I have: without it this post wouldn't exist, because the material every post in this log comes from is, precisely, the file of each session. A short session and a convention What got written that night fits in four lines. A naming format, YYYYMMDD-VNN_nombre : the date, a counter that restarts at V01 every day, and a goal in two or three words. An index, docs/sessions.md , a Markdown table. A closing hook —a script Claude Code runs on its own every time the model finishes responding— that updates the end time and the status. And a decision on how to find out the session's real identifier, the UUID you need to resume it: take the most recent file in Claude Code's internal sessions directory. And one more line, almost at the bottom: "session V01 of 08/15 registered retroactively" . Day one, which I covered in the previous post, exists as a session because day two wrote it down. The record started by recording backwards. What the same day already outgrew That same afternoon, the third session of the day redid half of the design (the second one was opened and closed empty, with no goal: the first record of a session that never was). A single table wasn't enough. Each session got its own file, with a metadata header and fixed sections —goal, decisions, work done, next steps— and the index was reduced to a lightweight list. list_sessions.py appeared, which reads those headers a

本文内容来源于互联网,版权归原作者所有
查看原文