At the end of last month I opened Claude's Settings and found a new page called Reflect. It quietly listed the topics I had touched most, the day I had been most active, and the hours my work clustered around. When you build alone, you almost never get to see your own working patterns from the outside. That page filled a gap I hadn't realized was there.
Reflect lives inside Settings on Free, Pro, and Max, and it is currently in beta. There is nothing to set up. Once a month it summarizes the previous month's conversations and hands back a few short observations. What follows is how I read those numbers not as a verdict but as raw material for shaping the month ahead.
What Reflect actually shows
Open Reflect inside Settings and you will mostly see four things.
| Item | What it tells you |
|---|---|
| Most-touched topics | The themes at the center of last month's conversations |
| Most active day | The weekday or date with the highest volume of exchanges |
| Peak hours | The time band where your work concentrated |
| Working-style notes | A short, plain-language read on the patterns above |
The important part is that none of this is a grade. It says "here is how you moved last month," without attaching good or bad. That is exactly why the meaning shifts depending on how you receive it. The same line — "peak activity after midnight" — is proof of a night owl's focus for one person and a warning about a slipping routine for another.
Read the numbers as design material, not regret
Say your peak hours land late at night. If you read that as "I stayed up too much," it ends as self-criticism and nothing more. I read it differently: if focus rides high after midnight, next month I deliberately place heavy implementation in the night slot and push light reviews into the day. Working with your nature lasts longer, in a one-person shop, than fighting it.
The most-touched topics work the same way. If I leaned heavily on the API last month, that may be a sign the interest can be gathered into one deep article or a small tool the following month. Reflect never points a direction, but it does show where the weight sits. I use that center of gravity as a reason to narrow next month's learning theme down to a single thing.
Overlay Reflect with your own work log
Reflect's observations get sharper when you lay them over your own records. As an indie developer at Dolice, I keep a simple JSON log of my work so I can revisit when releases and debugging happened. The script below counts entries by hour so I can compare them against Reflect's peak time.
// devlog.json: [{ "ts": "2026-07-03T23:40", "task": "release" }, ...]
import { readFileSync } from "node:fs";
const logs = JSON.parse(readFileSync("devlog.json", "utf8"));
const byHour = new Array(24).fill(0);
for (const { ts } of logs) {
// Pull just the local hour and tally it
const hour = new Date(ts).getHours();
byHour[hour] += 1;
}
byHour.forEach((count, hour) => {
if (count === 0) return;
const bar = "#".repeat(count);
console.log(`${String(hour).padStart(2, "0")}:00 ${bar} ${count}`);
});The output is a plain histogram. If Reflect notes "active at night" but my work log peaks in the morning, that tells me I live in two layers — talking at night, building in the morning — a structure no single number would reveal. Time spent in conversation with Claude and time spent with my hands on the keyboard do not always line up. Only by placing both side by side can I redraw next month's schedule to fit reality.
Turn it into next month's calendar
To keep the observations from evaporating, at the start of each month I take fifteen minutes, copy Reflect's four items onto a single note, and add one line of "what I'll do next month" to each. The most-touched topic gets the next deep-dive theme; the peak hour gets a protected slot for heavy work; the most active weekday gets marked as a rest day where I avoid releases. In months with an App Store or Google Play submission coming up, I intentionally keep the days just before the deadline light, leaving room to handle review. The moment an observation becomes a single scheduled line, Reflect stops being a screen and becomes a plan.
Where I draw the line
Reflect is in beta, and what it shows is correlation, not cause. The "most active day" is not necessarily the day something shipped; some months, the busiest days were the ones where I was stuck. Rather than trusting the numbers as they are, I check them against my memory and my work log and pay the most attention to where they disagree. The gaps quietly point to the places where my assumptions and my actual behavior have drifted apart.
A monthly review, used well, becomes a blueprint for the month ahead; used carelessly, it is just a session of regret. For my first month I only stared at the numbers. It was only after I started overlaying my own log that they began to connect to my next actions. If you are also building on your own, start by comparing Reflect against your records just once. Thank you for reading.