@techinevolution@realchartchamp@thsottiaux I think the resets are the true point of these 28 days. Feels like a secret way of forcing tests of spiked and higher loads.
Fingers crossed the actual goal of the 28 days is a modestly affordable “unlimited usage” tier.
@_simonsmith Oof. Mine did that once, but then I told it that it’s literally supposed to have access to the sites plugin capabilities and can inspect , add to, and interact without being in a browser session. It complied. Really strange to have to constantly reteach it its own skills.
@hulibrands@CaliberPSC@thsottiaux My guess is global resets make demand easier for OpenAI to forecast and capacity easier to manage by synchronizing everyone’s allocations to the same date.
They also prevent unused allowances from accumulating, giving OpenAI more control over consumption than banked resets would.
@ForwardEditor@moinulmoin It seems very situational. On sol 6.1 I had one thread run for 4 days and use 10% total. Then another running for 8hrs eating 40%.
@thsottiaux Is really move if one of those things was allowing the dot to orchestrate and instruct local codex threads. Have tons of projects that I want dot to be in on , and he can’t really contribute organically right now.
@nmPraveen@ForwardEditor PowerShell works
Local file access works. created, read back, & removed a test file
Browser control not available: no browsers listed, opening a test tab returns “Browser is not available: iab.”
Screen viewing/ mouse/keyboard control not available.
runs through a local task;
@mattlam_ My dot’s local computer use is severely crippled. It can’t access browser use and it can’t access mouse/keyboard screen share. That makes computer use crippling for tasks that need visual verification or mouse actions.