[ikari_pl]

We do.

I work with 3-5 parallel sessions most of the time. Some of the projects are related, some are not, some sessions are just managing and tuning my system configuration, whatever it means at a given time.

It doesn't feel weird to me.

[saulpw]

3-5 parallel sessions for 8 hours a workday, fine. 5x8x20 = 800. How do we get to thousands?!

[Syntaf]

In my OP I mention this is aggregated across both work + personal, so the comparison of just 8 hour workdays 5 days a week isn't accurate.

Running some `/stats` on my work computer shows for the last 30 days:

* Sessions: 341

* Active days: 21/30

* Longest session: 3d 20h 33m (Some large scale refactoring of types)

So I'm running a little over 10 sessions a day, each session varies from something like 1-2 hours to sometimes multiple days if it's a larger project. Running `/clear` actually doesn't start a new session fwiw, it will maintain the session but clear context, which explains why I can have a 3 day long session but I'm not actually using a single context window.

On the personal side I have activity in 30/30 of the last days (:yay); I've been learning game dev recently and use Claude a lot for helping digest documentation and learn about certain concepts as I try to build them in Unity. One of my more interesting use-cases is I have three skills I use during play tests:

* QA-Feedback: Takes random thoughts / feedback from me and writes to feedback markdown files

* Spec-Feedback: Loops every minute to grab a feedback item and spec out the intention / open questions

* Impl-Feedback: Loops every minute to grab a spec, clarify open questions with the user (me) first, then create an implementation plan

So I might have a friend play my game and I'll generate 20-30 items of feedback as I watch them play the game, things like minor bugs or mechanics in general. Over the course of the day my Claude will spec and plan out the feedback for me. I have remote sessions always on so I can use my phone to check in on the implementor job and answer open ended questions as they come up.

By the following day I'll usually have a bunch of plans ready for Claude to work on. I'll send agents off to do the simple ones throughout the day (bugs) and work with Claude on the bigger items.

Sorry for the long winded explanation but trying to convey the level of usage I have w/ Claude code. I do admit "thousands" is hyperbolic, as I'm probably only nearing 2k session hours in the most extreme months but I would say I on average use Claude every day to some capacity, often times both during work and after work (for my hobbies).

[saulpw]

Great, thank you for the detailed response! The biggest difference in our use is your "loops every minute", which I've not been willing to try yet (even with me at the helm, Claude might try to make a fairly straightforward bugfix in a cracked-out way and I have to steer it in the right direction).

[Syntaf]

Np!

I also love using `/loop` at work on combination with a PR maintenance skill, helps me push up changes initially and have a session automatically monitor + fixup a branch to get it passing before I review it myself and then later send off for a human review.