[ENHANCEMENT] Configure time and cost context

[jaxnb]

Problem (one or two sentences)

Occasionally, models will stop working, claiming that the task is taking too long or costing too much. In most cases, current time and cost are irrelevant to the work that Roo needs to complete.

Context (who is affected and when)

Long-running tasks, especially with GPT-5-codex

Desired behavior (conceptual, not technical)

On/Off options to disable "Current Time" and "Current Cost" sections of the system prompt.

Constraints / preferences (optional)

Context section of the options seems appropriate.

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I'm exploring a potential fix for adding configuration options to control the Current Time and Current Cost sections in the system prompt. I'll open a PR to share progress.

[hannesrudolph]

@jaxnb are you only seeing this with codex? I use ALOT of Roo and have not seen this.

[jaxnb]

@hannesrudolph Thanks for the quick reply! I've only seen it in Roo with codex. One of my teammates has seen sonnet 4.5 do it in claude code, but overall we suspect that the newer models are being fine-tuned on data with time limits (eg, codex web's task time limit)

[hannesrudolph]

I think it might make sense to permanently remove the cost from the context. I don't think it even makes sense to keep the time in there. It does make sense to have the time and date initially in the context. But not repeatedly thoughts?

[roomote]

I've opened PR #8451 to address this issue: #8451

The implementation adds two new boolean settings:

• includeCurrentTime: Controls whether the current time section is included in environment details
• includeCurrentCost: Controls whether the current cost section is included in environment details

Both settings default to true to maintain backward compatibility.

Note: There are currently two CI checks failing:

1. Translation check - only English translations were added in this PR
2. Integration test - this appears to be unrelated to the changes

The core functionality has been implemented and tested locally. Feedback welcome!

[jaxnb]

That sounds reasonable and simpler.

[Alek2077]

Definitely not on every single request.

Might make sense to give the option to remove VSCode Visible Files and VSCode Open Tabs as well. Even turning this down to zero doesn't seem to remove the subheadings for these two which get sent on every single request.

Might also make sense to give the option to completely remove <environment_details> from context. These things get added on every single reply. That's a lot of noise and clutter. While they do have 'current mode' and 'working directory' even these can sometimes be omitted, if not the 'current mode' then 'working directory' for sure. AI can remember this. At least it doesn't need to have the 'model' in there. AI doesn't need this info about which model it is.