Opens the Nanobot Agent web interface in the browser's sidebar.

[edualbercas]

https://addons.mozilla.org/es-AR/firefox/addon/nanobot-panel/

In addition, this Firefox extension opens the Nanobot panel in the browser's sidebar. Nanobot runs on your own computer at http://127.0.0.1:8765/ and this extension lets you keep it always visible without taking up a separate tab.

What it's for

• See the Nanobot panel in the Firefox sidebar 📌
• Open it automatically when the extension is installed 🚀
• Reopen it with a keyboard shortcut: Ctrl+Shift+N ⌨
• Automatically retry loading if the local server is not ready yet 🔄

How it works
When you click the sidebar icon, Firefox shows a page bundled with the extension that loads the content of http://127.0.0.1:8765/ fullscreen inside the panel.

Requirements

• Firefox 140 or later 🦊
• Nanobot running at http://127.0.0.1:8765/ 💻

[edualbercas]

@Re-bin @chengyongru

[chengyongru]

I made a browser extension called nanopilot , initially just to test nanobot’s WebSocket channel. Sidebar is definitely a very important capability, but I honestly don’t have time to build something like that right now. If I do build it, I’d want to do it properly rather than make a split-screen interface like this

browsers already have native split-screen support. I’d like it to work more like an agent inside the browser, but I haven’t fully figured it out yet.

[edualbercas]

I think this could be implemented without modifying Nanobot's core code.

My idea is to extend the existing Firefox extension and use Nanobot's existing WebSocket channel as the communication bridge.

The architecture could work like this:

• Firefox Extension: Provides browser capabilities using Firefox's native APIs, including reading the active tab, accessing open tabs, extracting page content, navigating, clicking elements, and interacting with forms.
• WebSocket: Communicates with Nanobot through its existing WebSocket channel.
• External Nanobot Skill: Exposes browser operations as tools that the agent can invoke, without changing Nanobot's source code.
• Local communication: Keeps everything running locally, without requiring an external browser automation service.

I could develop this as an independent open-source GitHub project, extending my existing Nanobot Panel extension.

Once the implementation is tested and stable, I could publish it on the Firefox Add-ons marketplace.

This would allow Nanobot to act as a real browser agent while keeping its core completely untouched.

I'd be happy to work on this and share the project with the community.

[chengyongru]

sounds very attractive! happy to see that!

[edualbercas]

If you think this is a good approach, I'd be happy to take care of the extension development myself.

I know you already have a lot of work maintaining and developing Nanobot, so I don't think you need to spend additional time working on the browser extension.

I'd gladly take this on as an independent community project, develop it, test it, and eventually publish it on Firefox Add-ons.

Of course, I'd be happy to coordinate with you and make sure it follows Nanobot's architecture and vision.

[edualbercas]

nanofirefox.mp4

@chengyongru

[edualbercas]

https://github.com/edualbercas/nanobot-fox

[Sadrak2017]

For the README’s “type wrote on another page” case, could mutating commands carry the tab ID and observed URL, with the extension refusing a mismatch at dispatch? A separate get_active_tab call can go stale before type runs. That’s a relevant boundary for our agent-governance work on Sinaps Studio at SinapsData: permission to control Firefox should not silently become permission to write into whichever tab is active.