A proper sandbox account environment is needed when working in the paradigm of AI_Agentic_Compute, in that, you’d be well to have:
Prod account - Primary full_power Dev/DevOps account one uses - but then a separate account that is the sandbox accoutn and it has a COPY of the codebase and a MIRROR of context - and you can run sandbox what_if against the same code, with the same CONTEXT - yet in sandbox mode where its nerf’d and cant upstream anything.
This would keep the request budget separate, and more interstingly, trackable and quantifiable/vlauation on certain aspects of interaction with Agent, outcomes of Curious_Ponderance “wouldnt it be cool if…” and “ooh - now add ALL THE THINGS!”
I’ve personally tested opening two separate Cursor Sessions, to the same folder, then had the Cursor_Session_02 read the .vscdb tables that Cursoe_Session_01 is putting into the vscdb, hence being technically able to MIRROR context straight from the SQLite vscdb – you can ask specstory’s implementation on how its accessing the vscdb…
But this type of setup needs some thought and needs to be bullet_proof’d…
I was looking at how to do Agentic_File_Locking originally - but never went ot bottom of that rabbit hole yet…
Also, .cursorignore has been seen to not be 100% trustworthy…
So the combination of all these Cursor Attention Focus Rules Projects in the next few months will be needed…