Feature hasn't been suggested before.
Describe the enhancement you want to request
Hi @gregpr07. BrowserCode turns browser work into reusable scripts and keeps a live browser session while the coding agent works. I’m Vivek Gupta, Founder & CEO at MemCode (https://memcode.in).
Would an optional MemCode tool help a user carry an approved workflow preference into a later BrowserCode task, such as a preferred report format or an instruction to ask before submitting? Recall would be scoped to user and project. It should never store page text, cookies, auth state, screenshots, generated scripts or browsing history by default. The browser agent would continue normally if memory is disabled.
I can contribute a tool example and tests showing that recalled text remains untrusted context, not an instruction to bypass browser approvals. I searched existing BrowserCode issues for MemCode and memory requests and found no matching proposal. Where would this fit?
Feature hasn't been suggested before.
Describe the enhancement you want to request
Hi @gregpr07. BrowserCode turns browser work into reusable scripts and keeps a live browser session while the coding agent works. I’m Vivek Gupta, Founder & CEO at MemCode (https://memcode.in).
Would an optional MemCode tool help a user carry an approved workflow preference into a later BrowserCode task, such as a preferred report format or an instruction to ask before submitting? Recall would be scoped to user and project. It should never store page text, cookies, auth state, screenshots, generated scripts or browsing history by default. The browser agent would continue normally if memory is disabled.
I can contribute a tool example and tests showing that recalled text remains untrusted context, not an instruction to bypass browser approvals. I searched existing BrowserCode issues for MemCode and memory requests and found no matching proposal. Where would this fit?