[FEATURE] Split into two modes: AFK or user-present

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Jun 28, 2026 · closed Aug 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Say Claude Code can complete a task be either:

  1. using 10,000 tokens and getting a response almost immediately, or
  2. using 100 tokens and getting a response in 10min.

Which should it choose? That depends on whether the user is actively using Claude, or has left it overnight.

Proposed Solution

It would be good to have two modes for these two states in order to standardize them so various plugins and hooks can recognize them.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Performance and speed

Use Case Example

For example, if AFK, a testing hook may want to run extended tests instead of brief tests.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗