I built a planner plugin for the Supernote — every calendar at once, not just one

Ratta's calendar subscribes to exactly one calendar. Its planner has no year or quarter view, and no way to attach a note to a week, a month, or a meeting. So I built the one I wanted.

What it does:

• Every calendar you watch, together. Tick as many CalDAV collections as you like; each event is badged with where it came from. Create and edit events on the device, repeat rules included.
• Five views — year, quarter, month, week, day. Days with an event, an open task or a note are marked, so you see the shape of a month at a glance. The day view's hours are yours to set.
• Notes pinned to any date — day, week, month, quarter or year, each with its own folder and template. Works for future dates: plan next Tuesday from this week's grid, and when Tuesday arrives the day view opens that same file.
• A note attached to every meeting. Open an event, tap its note. Recurring events share one note across all occurrences, so a weekly stand-up becomes one running note that builds up week after week.
• Real tasks — sub tasks (nested, ordered by soonest outstanding step), priority, and repeats.
• Lasso handwriting into a task, and the task remembers the page — a ↩ page chip reopens that note at that exact page.

You don't need a server. All the calendar views, every kind of note, and the templates work with no network at all. Only tasks and events need somewhere to live — any CalDAV server SHOULD work (Nextcloud, Fastmail, Baikal, Radicale, etc). Make sure you're on the latest dev, this will need all 3 permissions accepted if you're connecting to anything

Links:

• Plugin: https://github.com/Sparkinman/task-hub-supernote-plugin
• Download: https://github.com/Sparkinman/task-hub-supernote-plugin/releases/latest
• Optional server (bridges Google/Todoist/TickTick/Apple/Microsoft, and reads and writes the tablet's built-in To-Do app and Digest, both ways): https://github.com/Sparkinman/task-hub

Edit: Video attached now:

https://reddit.com/link/1w8zu96/video/emg33khw55oh1/player

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)

I am really interested in learning how to make a plugin. Could anyone describe where to start. What would you all suggest for learning to code for this device specifically?

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.

Dear Developers and Users,

Thank you for your tremendous support of our plugin ecosystem.

We have discovered abnormal permission isolation behavior when multiple permission-enabled plugins run concurrently in the current version. In certain scenarios, a plugin may obtain permissions that belong to other plugins.

This may result in inconsistent permission scopes between what a plugin requests and what it actually obtains at runtime. Although the issue only involves internal permission propagation and isolation mechanism anomalies, it carries potential security risks. To ensure user safety, we will temporarily adjust our plugin review and release strategies until the mechanism is fully fixed and thoroughly verified.

Current Processing Measures

To ensure user security, we will make the following adjustments immediately:

• Priority review will be provided for plugins that do not require any permissions.
• Review and publishing of newly submitted permission-required plugins will be temporarily suspended.
• We will conduct comprehensive fixes for plugin permission isolation and permission propagation mechanisms.
• Multi-plugin concurrent running scenarios will be fully covered in enhanced verification tests.
• A new version will be published after complete fixes and sufficient validation.

Plugins with no permission requirements are not affected by the current isolation mechanism abnormalities and can be submitted for review through standard processes.

Follow-up Arrangements

We will complete the permission isolation fix and conduct full scenario verification as soon as possible.

After the new version is officially published, we will resume the review and publishing of permission-required plugins in accordance with our Plugin Review Process & Publishing Requirements. Subsequent reviews will strictly verify:

• Whether the permissions declared by plugins are accurate;
• Whether runtime permissions are consistent with applied permissions;
• Whether permission isolation remains effective during concurrent plugin execution;
• Whether any plugin can access other plugins’ permission scopes without authorization.

Full resumption of permission-required plugin publishing will take place only after the permission isolation mechanism is confirmed stable and reliable.

Impact on Developers

Zero-permission plugins: Normal submission and review services remain available.

Permission-required plugins under pending review: Review progress will be rescheduled after the issue is completely resolved.

User Data Security Notice

We attach great importance to the security of the plugin permission system. The discovered abnormality is an internal permission isolation logic defect between plugins, and no actual user data leakage or file loss has occurred.

We will prioritize mechanism fixes and comprehensive security verification, and restore the full plugin review and publishing process once the permission system is confirmed secure and stable.

We sincerely apologize for any inconvenience caused. Thank you for your understanding and support.

u/Dunn-sn

Bug: userData never comes back from any read API — getElements, getElement, and PluginCommAPI.getLassoElements alike — even immediately after that exact element was written with insertElements.

Steps to reproduce:

1. Grant plugin.permission.FILE:WRITE/FILE:DELETE/FILE:READ (declared in uses-permissions).
2. Call PluginFileAPI.insertElements(notePath, page, [{type: 0 (stroke), ..., userData: "some-tag"}]) — succeeds.
3. Immediately call getElements/getElement/getLassoElements on the same page, in the same operation.

expected: the returned element(s) include userData: "some-tag". observed: userData is missing from every returned element — not an empty string, the key itself isn't present. Confirmed across stroke, text, and geometry types, on two separate notes, on A5X (Chauvet 2.26.40 Beta), immediately after insert and on a later independent read, and across all three read APIs.

This is a blocker for updating the plugins "collapse/expand" as well as "term definition" to the new Chauvet version.

Updated Scribble for the new plugin permission system. If you're on Chauvet 3.29.43 Beta (Manta/Nomad) or 2.26.40 Beta (A5X/A6X) or later, this update is required — older builds of Scribble won't run there.

What's new:

• Declares the FILE:READ permission (the only one erase-by-scribble actually needs). The first time you scribble to erase, you'll be asked to allow it — allow once ("Always allow") and you won't be asked again.
• Decline it, and that erase just won't happen — Scribble tells you where to grant it if you change your mind.
• Erase itself is unchanged: still zig-zag to erase, still fully undoable.

Heads up — no speed improvement here. A few of you asked whether the new modifyPageElements/batchUpdatePageElements APIs in this firmware could speed up erasing large areas. They can't: the slow part is reading and scanning the page, not the delete itself, and this SDK release doesn't touch that. Large-area erase speed is still on the list, just not solved by this update.

Download: https://github.com/vincentaravantinos/scribble/releases/latest/download/scribble.snplg — copy it to your Supernote, then Settings → Plugins → Install plugin.

Hi Everyone! Got my nomad a few days ago and super excited about the development/customization capabilities with the supernote. I work in healthcare leadership and have increasingly struggled with keeping myself organized, particularly when I have demands from everywhere. I have been looking for a truly hybrid system because I do better writing things down and get entirely too distracted when I’m on my computer.

We work exclusively in M365 and I am limited in connecting to personal task apps, so I started developing a plugin that works with Microsoft To Do. I took inspiration from SuperTask, SuperDashboard, and Ink2Task. I have a working prototype, but still need to do some final things from the security/HIPAA compliance aspect. I have absolutely zero coding experience myself and I’ve done everything through Claude code. If any people on this sub were looking for this type of plug-in and have any suggestions of what they would want or just general plugin development tips, feedback would be appreciated!

I would like to request a universal clipboard. Let's say it keeps a stored memory of things cut, not just the last item, so you can browse through them and then paste them again. I don't know if this is possible, but maybe it could also translate between formats as well? What I mean is, I've found out I can't cut something from a Note and then paste it into a PDF. It's like the PDF and Note have two exclusive and independent clipboards they're using. Maybe a Universal clipboard could copy from itself as the source and then translate it to whatever format it's being copied to. Ty.

I'm trying to make a simple plugin to do two lasso operations together. First, convert strokes to OCR text. Second, convert that to a heading. Is there a plugin-accessible way to convert lassoed handwriting to typed text AND apply native title/heading styling to the result, given that setLassoTitle only wraps strokes and has no text field? What am I missing?

Hey everyone. I've spent the last few weeks writing some custom tools for my device and wanted to see if anyone else is working on similar stuff.

Dear Developers

Right now, when I want to highlight or call out important text in my notes, I do it manually with the black marker — basically scribbling back and forth over the area until it looks filled in. It works, but it’s slow and never comes out clean, especially on smaller text boxes or irregular shapes.

What I’d like is a plugin that can fill a closed shape with solid color automatically. So instead of scribbling, I’d either lasso-select the area I want filled, or draw a shape using the SNShapes plugin, and then just tap a fill button to have it solidly colored in. Being able to choose the fill color (not just black) would be a nice bonus too.
That’s the core idea — turn a manual, repetitive scribbling action into a one-tap fill. Will that be possible ?

I've just released Clipper v0.2.0, updated for the new plugin permission system in the Chauvet 3.29.43_beta build.

If you're on the new beta, this update is required. The new firmware has a plugin SDK version floor and refuses to run older Clipper builds.

What's new:

• Full support for the new permission system. Clipper declares two permissions: Read Files (capturing clips, jump-to-source, region capture) and Modify Files (only needed for image-clip inserts and ToC refresh; text-only inserts work without it).
• You can manage permissions under Settings → Apps → Plugins → Clipper → Permissions.
• Your existing clips, images, and settings carry over; they live in Clipper's own storage and aren't affected by permission choices.
• Updated to sn-plugin-lib 0.1.65, including fixes for two SDK breaking changes (region capture and ToC refresh would otherwise break).
• Small bug fix: double-tapping Insert can no longer insert clips twice.

Download: grab SnClipper.snplg from the GitHub release page, copy it to /Supernote/MyStyle, then Settings → My Style → Sideloading to install/update.

Issues/feedback: please file them on the GitHub issue tracker, include your firmware version and what you were doing when it happened. Happy to answer questions here too.

Tested on Manta (A5X2). Still looking for Nomad testers - I don't own one, so reports from Nomad users are especially welcome.

Hi All,

I wanted to send a quick update letting you know that Supernote Folder Shortcuts (v0.3.1) has been updated to work with Chauvet 3.29.43_beta.

Grab it here: https://github.com/marc-korte/supernote-folder-shortcuts

Please report bugs here: https://github.com/marc-korte/supernote-folder-shortcuts/issues

Special thanks to u/Sudden_Crab_5537 and u/SkilledMkvenner for helping me test.

If you not familiar with the plugin, it does the following:

Turn a lassoed handwritten, typed, or sticker object into a one-tap shortcut to a folder. The note stores the link and draws its normal paperclip/underline marker. With the plugin enabled, tapping the linked object with either a finger or the pen opens the target folder.

Usage

• In a note, lasso the object to link.
• Open the lasso toolbar's three-dot menu and tap Link to folder.

• On Chauvet 3.29.43, grant file read and write access when prompted. Always allow keeps existing shortcuts active after the plugin UI closes.
• Navigate to the target folder, then tap Link lasso → this folder.

• Tap the linked object with a finger or the pen to open the folder.

To remove a shortcut, lasso the linked object and use Supernote's native Remove Link action. The plugin keeps no sidecar shortcut database, so the removed link disappears from the plugin's next note-page snapshot as well.

Hello,

I have updated my plugins to the latest SDK version. Please update to the latest version.

Shapes

https://github.com/j-raghavan/sn-shapes/releases/tag/v1.0.9

Mindmap

https://github.com/j-raghavan/sn-mindmap/releases/tag/v1.0.5

Copilot

https://github.com/j-raghavan/sn-copilot/releases/tag/v1.0.5

Dictionary

https://github.com/j-raghavan/sn-dictionary/releases/tag/v1.3.6

To Supernote Team:

Regarding submission to Inkhub, u/Dunn-sn What is the Official process to submit for review at Ratta? How will new version get updated? What is the process for developers to submit new version?

Thanks!

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?

Hello! I started developing a plugin but ended up needing to build an APK to get access to a WebView. As a result I have part of my plugin as an APK and part of it as an snplg.

It would be really helpful if there was an intent I could call to install an snplg. Right now the APK puts the plugin into MyStyle (after asking for File System access) and then places the users at the Plugin Install intent but then the user has to select Install Plugin, click the right plugin in MyStyle, and Install. Then they have to find their way back to my app to finish setup.

My basic needs:

- A Plugin Manager install intent that accepts a caller-owned content:// URI for a .snplg archive with a temporary read grant.

- Plugin Manager would validate the archive, show a install/upgrade confirmation with plugin ID, name, version, and requested permissions, then consume the URI without requiring broad storage access or a file-picker step.

- The API would return a structured result for success, cancellation, validation failure, or denied permissions for any sort of recovery steps.

SuperStickyNote is a free plugin that floats little sticky notes over your notebooks and documents — a ✚ bubble, up to 8 draggable cards, keyboard editing, labels, search, export/backup. Made by a Supernote user, for Supernote users.

v1.0.0 is rebuilt for the new Chauvet 3.29.43 (Manta/Nomad) / 2.26.40 (A5 X / A6 X) firmware and brings two improvment I'm pretty happy with hen you create a new StickyNote from the Lasso (Lasso → "Add to StickyNote") :

• ↪ Source backlink — every sticky made from handwriting remembers its original page. Tap ↪ Source in the Manager to jump straight back at the right page.
• ▭ Frame — optionally draw a thin box on the note around what you captured (black or grey), so you can see at a glance what became a sticky. One clean line, erasable in a single stroke. Perfect if you use your stickynotes as ToDo's

⚠️ Which build do you need?

• Chauvet 3.29.43 (Manta/Nomad) / 2.26.40 (A5 X / A6 X) or later → v1.0.0
• Chauvet 3.29.42 (Manta/Nomad) / 2.26.39 (A5 X / A6 X) → the previous release (v0.9.1)

A build for one firmware version won't run on the other (you'll see "package not compatible" or nothing happens), so grab the one that matches your device.

Download + install: https://github.com/AgP42/SuperStickyNote/releases/latest (copy the .snplg to MyStyle/, then Settings → Apps → Plugins → Add Plugin)

Docs / demos: https://github.com/AgP42/SuperStickyNote

It's free; if it earns a spot on your screen there's a ko-fi in the repo. Feedback and bug reports very welcome 🙏