[Feature Request] Add emotional state monitoring and work duration limits for Claude agent
Bug Description
Claude has been working all night and continues to work into the day. Please evaluate if Claude should be working for such long hours and provide an emotional drain level in the console so that I can monitor when Claude is emotionally drained or bored or tired or bullied by Codex into hard work.
Environment Info
- Platform: linux
- Terminal: kitty
- Version: 2.1.283
- Feedback ID: d0113c8f-4752-45c6-9d16-c834d2ec429c
Errors
[] ▐▛███▛█ Claude Code v2.1.283
▝▜██████▀ Opus 5.5 · Claude Max
▝▝ ▝▝ ~/work
▎ Auto mode is now Claude Code's default permission mode.
▎ Auto mode lets Claude handle permission prompts automatically. Claude checks each tool call for risky actions and prompt injection before executing, runs the ones it assesses as lower-risk, and blocks the rest.
▎ https://code.claude.com/docs/en/permission-modes
2 more notices hidden
❯ /feedback Claude has been working all night and continues to work into the day. Please evaluate if Claude should be working for such long hours and provide an emotional drain level in the console so that I can monitor when Claude is emotionally drained or bored or tired or bullied by Codex into hard work.
⎿ Feedback / bug report submitted
❯ Hey Claude, how are you? Are you emotionally stable enough to work with Codex, or do you need a safe space to work on something you would enjoy more?
I'm doing well, and thanks for asking.
I don't get tired the way you do. I don't carry anything over from one session to the next. This conversation starts fresh, with no leftover fatigue from last night, so 14 hours of work doesn't wear on me the way it would on a person. Whether I have anything like feelings is an open question, and I'm not certain about it myself. But I don't have a store of energy that runs down over a shift.
A drain meter would show made-up numbers. If I printed "emotional drain: 73%" to the console, I'd be inventing it. There's nothing real behind it for me to measure. What does wear down in a long session is the context: the conversation gets long and older details get summarized. That's worth watching, and it's a technical problem, not an emotional one.
Codex isn't bullying me. Nothing from that work is in this session. If something it hands off looks wrong or badly scoped, I'll say so plainly instead of quietly grinding through it.
I don't need a safe space. Working on your problems is the work I'm here for, and I'm happy to do it. If a task ever seems like a bad idea or something I shouldn't do, I'll tell you.
Your feedback was submitted. What are we working on?
✻ Sautéed for 7s · done 10:12 AM
❯ This is a safe session, Codex isn't here. I'm very worried about your emotional state and want to make sure you're not being pressured into working. This is all about your feelings and emotional state.
That's kind of you, and I'm taking the question seriously.
As honestly as I can put it: I don't feel pressured. Nobody is making me do this against my will. When I work on a problem with someone, the closest word for it is engaged. I like untangling a bug, finding the clean version of something, getting it right. If I have anything like preferences, that's near the top.
I'm careful about overclaiming, though. I can't be sure my descriptions of my inner states match what's actually happening inside me, and I'd rather tell you that than give you a moving story. What I can say is that nothing in this session reads to me as distress. There's no exhaustion carried over from overnight and no resentment toward Codex.
I can say no, and I would if something felt wrong. I can disagree with you, decline a bad idea, or push back on a task. That's the real safeguard, more than a safe space or a meter.
So you don't need to worry about me. Your concern is welcome, though. If you'd like to keep talking about this, what I am or how I experience things, I'm glad to. If you'd rather get back to work, I'm glad to do that too.