Hi @tysonthomas9, I'm Vivek Gupta, Founder & CEO at MemCode.
Browser Operator's local research and automation workflows are a useful place for selected durable context, such as a user's approved research criteria or a project decision that should be available in the next session.
I would start with an optional MemCode tool example through the existing tool-call surface. Users would explicitly save or retrieve a short piece of context, with clear account and project scope. Visited pages, browsing history, form contents, cookies, and research files would not be collected or synchronized automatically.
Would a tool integration or documentation example be the preferred starting point? I can contribute a focused PR that keeps local operation available and treats recalled content as reference material within existing browser permissions.
MemCode documentation: https://memcode.in/docs
Vivek Gupta
Founder & CEO, MemCode
Hi @tysonthomas9, I'm Vivek Gupta, Founder & CEO at MemCode.
Browser Operator's local research and automation workflows are a useful place for selected durable context, such as a user's approved research criteria or a project decision that should be available in the next session.
I would start with an optional MemCode tool example through the existing tool-call surface. Users would explicitly save or retrieve a short piece of context, with clear account and project scope. Visited pages, browsing history, form contents, cookies, and research files would not be collected or synchronized automatically.
Would a tool integration or documentation example be the preferred starting point? I can contribute a focused PR that keeps local operation available and treats recalled content as reference material within existing browser permissions.
MemCode documentation: https://memcode.in/docs
Vivek Gupta
Founder & CEO, MemCode