Page context vs conversation context: two scopes, one panel
Maho’s AI panel has two scopes: the page in front of you, and the conversation you have been having. They are not flavors. They are different inputs with different failure modes.
Maho’s AI panel has two scopes: the page in front of you, and the conversation you have been having. They are not flavors. They are different inputs with different failure modes.
Google ships Gemini inside Chrome. Maho ships an agentic side panel with BYOK. Two AIs, two invocation models, two views of what is happening on your screen.
A working tutorial. Install LM Studio, load a model, start the OpenAI-compatible server, wire it into Maho, and confirm with a quick round trip that no prompts leave the machine.
Tool calling is not a feature. It is a contract. This is the long version of how we honor that contract inside Maho’s side panel.
Microsoft Edge ships Copilot bundled. Maho ships BYOK. The two architectures answer a different question about who runs your AI.