We are pleased to provide new plugin preview versions for Supernote devices.

● For Manta / Nomad devices (Chauvet 3.27.42 Beta):

https://download-firmware.supernote.com/pversion/manta/20260515/update.zip

● For A5X / A6X devices (Chauvet 2.24.39 Beta):

https://download-firmware.supernote.com/pversion/A5X/20260515/update.zip

After downloading, please copy the update.zip file to the EXPORT folder on your device. Then disconnect the USB cable and confirm the upgrade on the device.

If you are upgrading from the latest Beta version to the plugin preview version, the displayed version number on the device will remain unchanged. All existing Beta features will be retained, with additional plugin development capabilities included.

The plugin development documentation is also available, including detailed guidance on the Supernote plugin development workflow and the plugin API usage.

Please note that the plugin development environment currently supports Windows and macOS only. Other operating systems are not supported at this time.

As the sn-plugin-lib dependency has been updated, developers who have already built plugins should update their local dependency by running:

yarn upgrade sn-plugin-lib --latest

This release includes the following updates:

Add:

• Added the PluginManager.registerMotionListener API to listen for pen and finger touch events.
• Added the PluginCommAPI.generateLassoPreview API to generate preview images for lasso elements.
• Added the PluginNoteAPI.generateLayerPreviewImage API to generate a preview image for a specified layer on a specified page. This API is available only for note files.
• Added the PluginManager.showPluginView API, allowing plugins to actively display the plugin view while running in the background.
• Added the PluginCommAPI.getCacheElement API to retrieve cached element data.

API Changes:

• Added a new state value, "3", to PluginCommAPI.setLassoBoxState. When set, all lasso-related UI can be hidden while the lasso state is preserved.
• To keep API naming consistent, the Java-side API names have been aligned with the JS/TS-side naming. Plugins need to update the `sn-plugin-lib` library and recompile; otherwise, API invocation failures may occur.

Bug Fixes:

• Fixed an issue where moving an image would clear "userData".
• Fixed an issue where the coordinates retrieved through the API did not update after moving an element and still showed the pre-move values.
• Fixed an issue where the page number of an opened note could display as "-1" when "insertElements"-related APIs were called frequently.

As I become more aware of the full power of plugins I am also feeling this could become a big security issue. It seems plugins can pretty much access all the users files, change them, communicate everything to any server on the internet. So it could be potentially used to scan files for information and sent them out, it could also just destroy data.

So I am wondering if it would not be good to put some sandbox constraints on plugins, e.g. having them read only from Inbox and write only to Export. Not allowing delete. Also to make use of internet something that has to be at least confirmed on install by the user. Perhaps the user can also block access to certain folders, so that notes and docs here cannot be accessed by plugins at all and are thereby protected.

This is not well thought through from my side. I just wanted to put my thoughts out there and would want to know if there are already any constraints in place or if others are being thought of. Or if the future inkHub upload would include some check of the code before publishing the plugin. I am a big fan of the plugin architecture and the possibilities, but I also know that many supernote users are appreciate security and privacy a lot, so it feels this should be addressed in some way.

We would like to inform you that the latest beta firmware versions—Chauvet 3.27.42 Beta for Manta and Nomad, and Chauvet 2.24.39 Beta for A5 X and A6 X—do not currently include plugin support.

If you choose to upgrade to these beta versions, your existing plugins may stop functioning properly, and there is a risk of plugin‑related data loss.

We strongly recommend that users who rely on plugins refrain from upgrading to these beta releases at this time.

Our team is actively working to merge the plugin codebase with the updates introduced in these beta versions. Once the integration is complete, we will release a new plugin version that restores full compatibility while preserving the improvements from the latest ETP beta release.

We appreciate your understanding and continued support as we work to improve the platform.

Thank you for being part of the Supernote beta community. 

Hey r/supernote,

I love my Nomad. It's my main line of defense for distraction-free thinking. But I’ve always found the pipeline for getting my notes off the device to be a bottleneck.

The Supernote Partner desktop app is awkward for bulk exports, and the old Python sync libraries I used to rely on no longer work. I wanted a way to automatically pipe my focused thinking directly into Obsidian and my AI workflows.

So, I built and open-sourced supernote-cli.

It's a terminal tool that fixes the plumbing and adds a few workflow conveniences. Here’s what you can do with it:

1. Extract notebooks and transcripts
List your notebooks and dump the on-device text recognition right to your terminal.

$ supernote notebook ls --limit 3
$ supernote nb [NOTEBOOK_ID]

2. Extract handwritten annotations from PDFs/EPUBs
List your annotated documents, extract your handwritten highlights/notes, and transcribe them (I use a local VLM for this).

$ supernote annotation ls --limit 4
$ supernote an [ANNOTATION_ID]

3. Extract action items using custom prompts
You can pass a custom prompt to extract specific things. For example, pulling out anything marked with a checkbox (☐) into a clean list:

$ supernote nb [NOTEBOOK_ID] --prompt "Whenever you see a line beginning with ☐, transcribe it..."

Links:

• GitHub repo (installation & docs): https://github.com/borismus/supernote-cli
• Blog post (more on the philosophy/why I built it): supernote-cli: pen, paper, and a pipe

It's extracted from my personal note-management setup, but it's generic enough now that it should be useful for anyone trying to build automated workflows around their Supernote. Let me know if you try it out or hit any bugs!

Will a new plug-in architecture be required for the new beta? I no longer see plug-ins in sidebar.

Hey, building a third-party plugin. Can anyone confirm whether expandMenuItem: 1 in registerButton() actually places a plugin button directly in the main toolbar (not the plugin submenu) on current Chauvet firmware? Testing on Manta 3.27.42 beta and it still appears in the submenu. Any workarounds known?

I’m building a Supernote plugin and trying to copy lasso-selected elements from the current note into another note file. The creation in the new note file works fine, but currently the source elements are deleted afterwards (basically making it a move operation). But I would like to keep them. Current stuck with this. Anyone that can help me or has experience with this. u/sn-Dunn: any suggestions from your end how to accomplish this?

The simplified flow is:

// User has an active lasso selection in the current note

const sourcePath = await PluginCommAPI.getCurrentFilePath();
const sourcePage = await PluginCommAPI.getCurrentPageNum();
const lassoRect = await PluginCommAPI.getLassoRect();
const sourceElements = await PluginCommAPI.getLassoElements();

// For each selected stroke element:
// 1. Read source stroke data into plain JS arrays:
const points = await source.stroke.points.getRange(0, count);
const pressures = await source.stroke.pressures.getRange(0, count);
const flagDraw = await source.stroke.flagDraw.getRange(0, count);

// 2. Create a new stroke element:
const target = await PluginCommAPI.createElement(0);

// 3. Write copied/transformed data into the new element:
await target.stroke.points.setRange(0, points.length - 1, movedPoints);
await target.stroke.pressures.setRange(0, pressures.length - 1, pressures);
await target.stroke.flagDraw.setRange(0, flagDraw.length - 1, flagDraw);

target.pageNum = targetPage;
target.layerNum = 0;

// 4. Insert the newly created element into another note file:
await PluginFileAPI.insertElements(targetNotePath, targetPage, [target]);

Expected behavior: the selected source elements remain untouched, and copied elements appear in the target note.

Observed behavior: the copied element appears in the target note, but the original lasso-selected source element disappears immediately from the source note, as if it had been moved rather than copied.

Additional observation: using PluginCommAPI.saveStickerByLasso(stickerPath) on the same active lasso selection does not remove the source content.

Question: is this sequence valid for copying lasso-selected elements to another note file? In particular, is it valid to use PluginCommAPI.createElement(...) together with PluginFileAPI.insertElements(...) while a lasso selection is active, or is there a required step to detach/release/clone elements so the source lasso content is not affected?

Built a Supernote plugin that lets you summarise, explain, or ask questions about whatever's on the current page (handwritten notes, PDFs, or EPUBs) using your own API key for ChatGPT, Claude, Gemini, or DeepSeek. Sharing it with the community here.

No backend. No telemetry. No "free" tier where the device maker silently bills your taps against a shared key. You bring the key, every billable request lands on your provider dashboard, and you can revoke or rotate it at any time.

What it provides

Four one-tap action buttons sit at the top of the chat panel so the common questions are a single tap, no typing:

- ☰ Summary: a structured digest of what's on the current page.
- ? Explain: a longer breakdown for when "summary" isn't enough; useful on textbook-style content.
- ✦ Clarify: flags what's unclear, ambiguous, or needs follow-up. Helpful on lecture notes / first-pass meeting notes.
- ⊡ Snapshot: a compact set of bullets you can copy back into your note as a "table of contents" for the page.

Plus:

- Free-form chat about the visible page in the same overlay (type at the bottom, hit send).
- Markdown-rendered replies with a one-tap **Copy** so you can paste the answer back into a note.
- Works on the current page only. Each request captures the page screenshot (vision-capable providers) plus extracted text (PDF text layer or handwriting OCR).

Why this is different

Most AI features on e-ink readers ship with a vendor-supplied key behind the scenes. Convenient, but you can't see the bill, you can't audit what's sent, you can't switch providers, and your data is on someone else's hands. Here the trade is reversed:

- You own the key. It lives in a text file on your device. Never uploaded.
- You own the chats. Requests go directly from your device to the provider you chose. We never see them.
- You own the audit. Every request shows up on your OpenAI / Anthropic / Google / DeepSeek dashboard: billable, dated, attributable.

Providers + default models in the templates

Provider	Default Model	Vision (Page Image)
OpenAI (ChatGPT)	gpt-4o-mini	Yes
Anthropic (Claude)	claude-haiku-4.5	Yes
Google Gemini	gemini-2.5-flash	Yes
Deepseek	deepseek-chat	text only (no vision endpoint)

Approximate cost per page summary on the cheapest models is well under a US cent. A heavy day is still under $0.10 across any of them.

Demo

v1.0.1 Demo

Quick start

1. Grab an API key from your provider's console.
2. On the Supernote, create the folder `MyStyle/SnCopilot/` (USB sync, WebDAV, or Cloud, whatever you already use).
3. Save a file `copilot-key-<provider>.txt` in that folder with three lines:
4. &gt;Example: copilot-key-openai.txt would have something like this
5. ```
6. provider=openai
7. model=gpt-4o-mini
8. key=sk-proj-1345abCDef67890...
9. ```
10. Tap the brain icon from the plugins menu of any note, PDF, or EPUB.

That's it. Templates for all four providers ship in the repo's `templates/` directory.

If you want to use multiple providers

Drop more than one `copilot-key-<provider>.txt` and add `default_provider=<provider>` to one of them (it doesn't have to be the file you're naming; any of them can declare the default). Example for an Anthropic key file when both OpenAI and Anthropic are configured:

```
provider=anthropic
model=claude-haiku-4-5
key=sk-ant-...
default_provider=openai
```

Without a default, the plugin shows a "pick one" message in Settings and refuses to send. With conflicting `default_provider=` values across files, same thing.

UPDATE

Security Focused Release v1.0.2

v1.0.2

Privacy posture

The page screenshot and any transcribed text are sent to the LLM provider you configured. There's no on-device redaction toggle that would create a false sense of safety while shipping the same content via the image. Be deliberate about which page is open before tapping Copilot. On DeepSeek (text-only) the plugin silently scrubs emails and 7+ digit runs, since that's the one path where redaction actually reduces what we ship.

Repo / release

- Source : https://github.com/j-raghavan/sn-copilot
- Release: https://github.com/j-raghavan/sn-copilot/releases/tag/v1.0.1

Feedback and issue reports welcome.

Here's another Claude-coded plugin to fill in a gap that I needed for sharing notes to various apps more cleanly ... export your current multipage note as a single stitched (top-to-bottom) PNG. It lands in your EXPORT folder.

https://github.com/jpmoo/scrollexport

Can we have the option to convert any note page to an infinite canvas ?

Would be super useful for diagram, long math, graphs, etc...

I understand we dont always want a page to be infinite, but having the option to convert any page would be great

Thank you.

In the Supernote community there were two recent requests for color output….not a color screen, but the ability to choose an output color for lines shapes text and highlights.

I’m not a developer myself but this seems like it would be a great plugin…. Or maybe a series of plugins that would allow a person to choose a color for a specific element and then have that show up on output to other systems.

Is this doable??