Use case
A developer running a long Codex session and repeatedly pasting screenshots to debug needs to decide, before sending the next message, which past images still go to the model, so the task can continue without restarting the session.
The old behaviour is manually restarting the session, saving images locally and re-pasting them, or simply ignoring the cost and continuing.
Past images stay in context, so later requests keep growing in size and cost; the user either absorbs the heavier requests or restarts the session and loses earlier debugging threads.
xOcto's call
Demand is evidenced
The trend is that coding-agent sessions grow long, and screenshots and attachments piling up in context turn directly into cost and latency. A wedge is cost-sensitive long sessions, such as token-billed teams or mobile development that keeps many design mockups, selling context cleanup and billing visibility rather than another agent shell.
Reason to use it
Why users would choose it
Inference: the plugin replaces 'restart the session or manually tidy attachments' with a pre-send checkbox, turning unchecked images into placeholders so the task is not interrupted; developers who debug with screenshots and care about request size would choose it in long sessions. 90 stars indicate attention only, with no retention or usage-frequency evidence.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: the plugin replaces 'restart the session or manually tidy attachments' with a pre-send checkbox, turning unchecked images into placeholders so the task is not interrupted; developers who debug with screenshots and care about request size would choose it in long sessions. 90 stars indicate attention only, with no retention or usage-frequency evidence.
Entry and what to borrow
The trend is that coding-agent sessions grow long, and screenshots and attachments piling up in context turn directly into cost and latency. A wedge is cost-sensitive long sessions, such as token-billed teams or mobile development that keeps many design mockups, selling context cleanup and billing visibility rather than another agent shell.