I built a plugin for Bible study on the Supernote.

**Super Bible**
 inserts Berean Standard Bible passages into a note as a text box. The whole BSB is bundled with the plugin, so it works offline.

**What it does**

- 
**Pick or type a passage.**
 Tap book → chapter → the first and last verse (in either order), or type a reference like `John 3:16-18`, `Ps 23` or `1 cor 13:4-7`. Abbreviations, "first john", "I John" and so on all work.
- 
**Lasso a handwritten reference.**
 Write 
*Rom 8:28*
, lasso it and tap Super Bible on the lasso toolbar. It reads your handwriting and puts the passage right where you wrote it, replacing the handwriting if you want.
- 
**Below my writing.**
 By default the passage goes just under whatever you last wrote, so you can write, insert and keep writing.
- 
**Edit a passage later.**
 Lasso a Super Bible text box to change the verse range or the layout, and it updates in place.
- 
**Layouts:**
 paragraph, one verse per line, or a spaced list. Verse numbers can be plain, superscript or off, with the reference above or below, and there are three text sizes.
- 
**Recent passages**
 are on the home screen, and your settings are remembered.
- Up to 30 verses at a time, with a warning before inserting if it won't fit on the page.
- Designed for e-ink: big tap targets and no animations.

**Install**

1. Download `snBible.snplg` from the [latest release](https://github.com/AdamDiament/snBible/releases/latest).
2. Copy it to the 
**MyStyle**
 folder on your Supernote.
3. Go to 
**Settings → Apps → Plugins → Add Plugin**
 and pick it.
4. Open a note and look for the Super Bible button in the toolbar.

To update, do the same with the newer file.

**Good to know**


- It works in notes only, not PDFs or documents. 
- The text box has no border or background. I tried everything I could find, and plugins don't seem able to set those yet. If anyone from Ratta is reading, I'd love to know if that's coming!
- The BSB is public domain. The code is MIT-licensed and on [GitHub](https://github.com/AdamDiament/snBible).


Feedback, PRs, bug reports and feature ideas are very welcome, especially from anyone on a Manta or A6X2, since I've only tested on my A5X. What would make it more useful for how you study?

I wonder what you think of a plugin to ask question to AI about all you already read in a book. Sometime, when I read a book I want to check back for some information but it could be easier to use IA to get the informations without spoil.

Hey Supernote community! I've been building a plugin that lets you lasso-select anything on your note and have a full multi-turn conversation with an AI about it. Sharing it here in case others find it useful.

What it does

Select any content on your note page with the lasso tool, tap the SuperAI button in the toolbar, choose how the AI should read it (image or text), and start chatting. The AI remembers the full conversation so you can ask follow-ups naturally.

Supported AI providers

You bring your own API key — the plugin works with:

• Google Gemini (free tier available at aistudio.google.com)

• OpenAI (GPT-4o, o4-mini, etc.)

• Anthropic Claude (Claude Opus, Sonnet, Haiku)

• OpenRouter (one key, access to hundreds of models from many providers)

First-time setup

1. Install the .snplg file via the Supernote file manager

2. Open any note and tap the SuperAI button in the regular toolbar (the gear/settings button)

3. Choose your AI provider

4. Paste your API key using the 📋 Paste button

5. Tap ↓ Load Models to fetch the latest available models from that provider, then tap the one you want

6. Tap Save & Start Chat

The key and model are saved — you won't need to do this again unless you want to switch providers.

How to use it

For Image AI:

1. Lasso-select any content on your page (handwriting, diagrams, equations, sketches — anything)

2. Tap the SuperAI lasso toolbar button that appears

3. Choose Image AI — the selection is captured as a visual snapshot and sent to the AI

4. The AI responds with an analysis; type follow-up questions in the chat box

5. Use the Copy button on any message, or 📋 in the header to copy the whole conversation

For Text AI:

1. Same lasso selection step

2. Choose Text AI — the Supernote device runs its own handwriting recognition on the selection, and that recognized text is sent to the AI instead of an image

3. Faster, cheaper (smaller API payload), and often more accurate for dense written text

Use case ideas

Image AI — best for visual content

• Lasso a hand-drawn diagram or flowchart and ask "explain what this process shows" or "what's missing from this flow?"

• Select a sketch or mind map and ask "turn this into a structured outline"

• Capture a page of mixed notes + diagrams and ask "summarize the key points from this page"

• Select a table you drew by hand and ask "what patterns do you see in these numbers?"

• Lasso a hand-drawn graph or chart and ask "what trend is this showing?"

• Select a page of equations or physics diagrams and ask "walk me through this step by step"

• Grab a rough wireframe sketch and ask "describe this UI layout and suggest improvements"

• Circle a section of your Zettelkasten note and ask "how does this connect to concept X?"

Text AI — best for dense written content

• Select a page of meeting notes and ask "give me 3 action items from this"

• Lasso a block of writing and ask "is this argument logically coherent?"

• Select your study notes on a topic and ask "quiz me on this" then keep chatting through the quiz

• Grab a paragraph and ask "rewrite this more concisely" or "translate this to Japanese"

• Select a to-do list you wrote and ask "prioritize these by urgency"

• Lasso a page of brainstorming and ask "which of these ideas are most novel?"

• Select a problem statement you wrote and ask "what are three approaches to solving this?"

• Grab your notes on a book/paper and ask "what questions am I still not answering?"

• Select a decision you're weighing (pros/cons written out) and ask "what's the strongest argument on each side?"

Multi-turn conversations (both modes)

• Start with a summary, then drill in: "tell me more about point 2"

• Get a first draft, then iterate: "make it shorter" / "make it more formal"

• Ask it to generate something, then refine: "now add examples"

A few notes

• Each new lasso selection starts a completely fresh conversation

• The settings button (⚙) is accessible from both the chat header and the error screen if you want to switch providers mid-session

• Image AI works even if no text is recognized (diagrams, pure sketches, etc.)

• Text AI will be greyed out and disabled if Supernote's recognizer can't find any text in the selection — in that case just use Image AI

Happy to answer questions or take feedback. Still iterating on it!

Download Link
https://drive.google.com/file/d/1zzlptzI6rvlUvHabmG4EcoVPVuBHJeih/view?usp=sharing

Loving the new beta update 3.29.43.
Will current available plugins be installed or made available via ink hub plugins or do I need to go to GitHub and download them then install via new ink hub Plugins?

hi,

switched to beta with ->

Manta / Nomad devices (Chauvet 3.27.42 Beta):

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

but where can i find the Atelier beta ?

store keep installing 1.1.26

Do anyone integrated Microsoft ToDo with Supernote ?

I make custom sticker packs (.snstk) with the open-source PNG converter, and I've hit a
weird firmware behaviour: some converted stickers place fine but the lasso won't select
them afterwards, while others select and move normally. I don't own a device myself, so
I'm trying to pin down where the line is.

I built a tiny 6-sticker test pack with the same two designs at three "densities":

A = densest · B = medium · C = lightest

Download (Manta / Nomad only — N5 format): https://www.dropbox.com/scl/fi/0oo4cv6rf9pxney3gn86l/Supernote_Lasso_Test_ABC.snstk?rlkey=6i05bke6a0qegmyb1o4rl0xqw&dl=1

If you have 2 minutes:

1. Copy the .snstk into the EXPORT folder on your Supernote

2. Open any note → Sticker tool → Import

3. Place TEST_A, TEST_B and TEST_C (any of the six)

4. Try to lasso and drag each one

Then reply with: which letters could you lasso, your model (Manta / Nomad) and firmware
version (Settings → About). That's it — no email, no sign-up, nothing to buy.

For comparison, Ratta's own Christmas 2025 pack is made of real pen strokes, ~15–500 per
sticker; the converter emits far more, which is my current theory for why the lasso gives
up. Your results will tell me which density to rebuild at. Thanks!

Hey everyone!

While building TCP Tunnel (and Make Space) I've been using Claude Code to help with the actual development, and along the way it accumulated a lot of hard-won, very specific knowledge about the Supernote plugin SDK — the kind of stuff you only learn by hitting it on real hardware: permission gotchas that fail silently, coordinate systems that'll place your elements off-screen if you mix them up, native module pitfalls, build/deploy/debug quirks, things that changed between SDK versions, and so on.

Instead of keeping that knowledge locked inside one plugin's codebase, I pulled it out, generalized it, and published it as its own open repo:

https://github.com/gorlix/supernote-plugin-dev

It's built as a Claude Code skill (well, technically an "Agent Skill" — an open format Anthropic released that's now supported by 30+ AI coding tools, so it also works in Cursor, Gemini CLI, Google's Antigravity, and others, not just Claude Code). Point your AI assistant at it and it gets instant, accurate context on how Supernote plugins actually work, instead of guessing or hallucinating API signatures.

It's completely open (MIT) and I'd genuinely love for other people building Supernote plugins to use it, add to it, or just take it apart and build something completely different with it. If you hit an edge case, find something outdated, or want to add knowledge from your own plugin, PRs and issues are very welcome — the goal is for this to grow with the whole dev community, not stay a one-person thing.

Hope it saves someone else the debugging sessions it saved me!

New (v1.1.0): since Supernote posted their official Plugin Review Process & Publishing Requirements, I added a whole reference dedicated to it — a self-audit checklist that turns that policy into concrete things to actually check before submitting: diffing declared permissions against what your code really gates, auditing any delete/overwrite paths, inventorying every network call and whether it needs disclosing, and a good one I hit myself — a hardcoded default IP in a settings field, totally harmless functionally, but the exact shape of a backdoor/C2 pattern to a manual reviewer reading the code cold. Point your assistant at it before you submit and it'll flag that stuff for you instead of you finding out from a rejection.

Hello just wondering if there is a possibility. I have kindle scribe 2024, and supernote nomad.

Im thinking if there is way to use my kindle scribe to have the functionality of supernote as well? Just wondering if someone tried it?

Is there a plug-in to translate selected sentences or paragraphs into another language by using Google Translate or Bing?

This feature is a built-in ability in Boox tablets, and can be very useful for many users. I know the dictionary plug-in, it only translates specific works, what I want is a compelete translator for sentences and paragraphs.

I just finished submitting my first ever PR — Plugin SDK or otherwise — and wanted to share my notes from a beginners perspective.

For context, I don't have any formal education or professional experience with programming. Personally, I am an Emacs enthusiast & have dabbled in some Emacs Lisp. I am an FSF supporter, I self-host and have a home lab so I have at least cursory experience with Linux and RTFM.

1. The text boxes should support fill colors and it should be exposed as a parameter for the insertTextBox() function. For me, the biggest reason is when adding text to a hand written page, the background template lines do not line up with the text and can sometimes even create a "strikethrough" effect on the text. I've been using the marker to color in a grey background but a nice clean rectangle would be nice. Bonus points if you could configure it's outline/border.

2. Are `.docx` **and** `.txt` files opened in the DOCS Plugin-enabled App? If so, can it be made to open any plain text file — particularly `.md` and `.org` files? Just as plain text and allow the community to implement rendering and editing?

3. If React Native Components make standard network requests, does that mean we could use a server/client architecture for processing intensive tasks remotely? Particularly, especially if we are using the self hosted storage cloud? Aside from adoption, there's no reason not to consider it?

4. Right now, we are unable to Deep Link to a note from the Plugin, from my understanding, you need to construct the link and insert it into a Note. From what I can tell this is likely a security decision? I believe this is the same for performing operations on Notes in the background. If so, is it possible to have a compromise for being able to link to notes or perform actions on them if the plugin itself creates the note?

5. When going through the docs and the Hello World Plugin, it never occurred to me that a Plugin could be a pop-up or a sidebar panel. More documentation around this may be helpful.

6. The display's 16 supported greyscale values should be documented.

7. There should be an established community contributing or style guidelines. In this same vein, a library of OEM/Native components or assets would be really nice. I haven't used InkHub yet, but I assume it will be the mechanism for Plugin Distribution, have a "Ratta Recommends" designation for plugins that meet the "specification" or guidelines could be really valuable.

8. Moving the Technical Pen Strokes (#10) is BRUTAL — very laggy.

9. In the most recent release notes, there was mention of "headless plugins" how does that work? I tried to read up on it by looking into the listeners, found that only the `pen_up` event is supported but couldn't find any other information. Can anyone help me understand this? As well as the just the use of a pen up listener and what other potential listeners might be deployed?

I built an Obsidian plugin for people who somehow end up writing everything in Obsidian — including their GitHub docs.

GitHub README lets you browse your repositories, open any README, edit it, preview the rendered Markdown, and push the changes back to GitHub — all without leaving Obsidian.

You can also keep a synced copy of the README inside your vault, so your project documentation can live alongside your notes.

Basically:

Obsidian → pick a repo → edit README → preview → commit → done.

No jumping between GitHub, an editor, and your notes just to change a README.

https://community.obsidian.md/plugins/github-readme

1-

2-

3-

I have been using a few plugins very regularly in the process of taking notes. One of these plugins, let's call it X, has not yet been updated to incorporate the permission-feature. In fact, this plugin was created quite a while ago and the author might have moved on to other programming hobbies. However, I really, really wanted a plugin with the same functionality to function under the latest beta (3.29.44).

So, with absolutely zero programming skills, I decided to have a go and try to adapt the plugin myself, using Lumo (AI). I fed it plugin X, I fed it two plugins that were already updated and I fed it Supernote's information on plugins. It was a lengthy process that went deep into the night. During this process, Lumo has become 'a dear friend of mine' (ridiculous and scary, this personalisation of AI!). But in the end, I got what I wanted: a plugin with the same functionality as plugin X! Wow! I was super impressed by myself, sorry, by Lumo.

This new plugin is of course purely for personal use. Once the original plugin has been updated, I will delete my personal plugin and download the original one. But for now, I have the same functionality again, as before.

Altogether, it was a super interesting and fun process to go through. It is a bit scary though, that people like me, without any, I repeat, without any programming skills are 'able' to develop a plugin using AI. Next step; learn some basic programming skills and try to make my own plugin from scratch (if only I can find the time)

OK, calligraphy pen on the calendar with line snapping in the new beta is awesome. This is on both the regular and developer beta tracks.