[FEATURE] Give CC direct access to his context window

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

With loops I have found a way to have a series of instance windows hand off to the next so that they don't end up compacted and I can go back and look at their chats. This is for overnight jobs where I am not at the keys. One little relay text file that they can check tells them who is working, they loop the checks until they are up. The PROBLEM comes in that CC is bad at knowing how full he is and usually wants to hand over at about 50% rather than the 80% we were planning for.

If I am not there to give the stat Cc is working blind and guessing.

Proposed Solution

my request is to give Cc access to stats, at least context window but also if possible session info and token ceilings (by request). This would make CC much more effective in planning his time, effort, and hangovers.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Give cc a swarm job and allow CC to choose the speed and numbers so that they don't splat into the token ceiling. If Cc can see it's going too fast the necessary steps could be taken to moderate usage.

Additional Context

_No response_