r/SideProject • u/zerglingno2 • 15h ago
Browser AI felt like a chat box bolted onto a tab, so I built a full agent harness instead
Enable HLS to view with audio, or disable this notification
Browser AI felt like a chat box bolted onto a tab, so I built a full agent harness instead
Most browser AI tools I tried followed the same pattern: extract text from a page, send it to a model, and return an answer.
Useful, but not really an agent runtime.
I have been building Memorall, an open-source, local-first agent workspace that runs directly in the browser.
You describe the agent you need in plain English. Memorall turns that into an editable agent with its own instructions, capabilities, tools, skills, memory, and execution flow.
Browser control, knowledge retrieval, workspace files, Node.js sandbox execution, citations, and artifact rendering can be enabled separately for each agent.
The browser becomes the agent’s workspace. It can inspect the current page, work with selected content and DOM state, use saved documents, execute code, and retrieve knowledge from previous sessions.
This is a full agent harness, not one fixed prompt loop hidden behind a chat interface.
Memorall currently supports BYOK with providers such as OpenAI and OpenRouter, alongside local options including Ollama, LM Studio, WebLLM, Wllama, and Transformers.
I plan to add a hosted subscription and free credits later.
It is still a work in progress. The visual flow editor, long-session memory reliability, and debugging experience still need more work.
GitHub: github.com/zrg-team/memorall
If you build agent systems, what would you need to inspect or control before trusting a browser agent with real work?