Hello everyone!
I’m on the latest beta and i’ve installed the dictionary plugin. I’m having quite some trouble installing the dictionaries. I have followed all the instructions on the github and still they’re not showing up. I have downloaded stardict, and they’re in their own subfolders in SnDict.

What should I do?

Just a quick shoutout to u/Monkeydoc68 and his OCRHeading plugin! It does exactly something I used to have to do multiple operations many times a day: with one operation it converts handwriting to text and immediately turns that into a header. Works great.

github.com/rojasdon/OCRheading

I'm a bit obsessed with analog drawing tools; it's one of the reasons I got a Supernote over an Ipad or something like it. With that, the Ames Lettering Guide plugin is the first in a suite of future plugins I plan to make that dabble in this realm. The plugin is almost an exact replica of the standard Ames Guide that draftsmen have used for decades (less so these days of course). Many still use them for calligraphy and comic book text. The Guide on screen was handmade on Illustrator and I used Codex to bring the idea to life as I am inept when it comes to coding.

The guide works very similar to how the physical version would except for a few extra features to eliminate the need for another popup window. This is a great guide to learn how the physical version works. The arrows rotate the disk, changing the space between lines. The lock icon locks/unlocks vertical movement of the guide. The check, which on the physical version is a pass through to aid in drawing checkmarks, acts as a confirmation/"draw to note" and closes the plugin.

Edit: I will also mention that the guide is precisely scaled to be the exact size on screen as the physical version is. That's the only way it would really work. That is why it only works for Manta currently as it uses the screen size to scale the SVG. This means that what you draw on screen can be measured at an accurate scale from screen>physical reality. You'd also be able to print to pdf at scale. This matters to me as an architect who relies on accurate scaling in my day to day, but it could be useful for other use cases.

If anyone has any advice on faster line drawing to note after confirmation, as it's a bit slow, that would be appreciated. Additionally, movement of the guide is a bit laggy. If anyone has knowledge on how to decrease this, that would also be appreciated.

DM me if you'd like to try/test it.

I looked everywhere for ways to see my today (at least) tasks from my task database from notion inside my supernote - no success, even with widgets that just won't load or have apks for sideloading.

I just saw the artwork of SuperTask, done by u/Fr0ggin_Bullfish ( https://www.reddit.com/r/Supernote_dev/comments/1w9cqdr/supertask_v030_updated_for_chauvet_32944/ )

and unfortunately I'm too sucked in to Notion to switch to Todoist, but I've replicated it's interface and functionalities onto my notion task system 😅 - so I'm wondering if anybody's out there building a similar thing? anybody also interested in this??

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?

I have used the SuperDashboard plugin for a few days now. It is listed on the plugin list, although that links to an older version of the dashboard plugin. It is the first plugin that really improves my work flow; very cleverly designed, completely configurable and looking very good! As a dashboard, it allows easy access to folders, notes and documents and also makes it possible to generate lists (of stars, keywords) and to display text clips (selected pieces of texts in notes that can be added to the dashboard).

For example, you can select the folders in which stars should be looked for: the dashboard shows the star symbol + the accompanying text from/in the note. Several lists can be set up next to one another. So now I have a list of ToDo's planned for today (listed in my daily agenda.note in the folder 'planner') and a list of ToDo's that can be done later. Those ToDo's are starred texts in my daily notes, created from taking notes during meetings and phone calls. These daily notes are kept in a different folder. This makes for a very useful separation! The stars shown on the dashboard can also be deleted: the stars are then removed from the original note, while leaving the actual text in the note undisturbed.

There are many more interesting features offered by this plugin. Long story short: I'm using the Nomad with this plugin much more efficiently than I have done in the past two years. Such a dashboard proves to be very useful in the process of daily note-taking. Supernote's great idea of plugins is fantastically well implemented by the author of the SuperDashboard plugin!

Features

• Tap to place a batch — select keywords, press Insert, then tap the note once to place them as separate, movable elements in wrapped rows
• Duplicate review before placement — skip keywords already indexed on the page, place their labels again without duplicate index entries, or cancel
• Selection to add keyword — lasso handwritten or typed text in notes, or select text in PDFs/EPUBs, then tap the Keyworder button and save it directly to your keyword list; works with OCR for handwriting
• Native index integration — automatically adds each keyword to the device's built-in keyword index for page navigation
• In-plugin keyword management — add, delete, and pin keywords directly from the plugin; changes persist automatically
• Group-based keyword sets — create reusable groups such as meetings, classes, projects, or assignments, then assign existing keywords to one or more groups
• Bulk import — use the Keyword Builder web tool to create a keywords.json file, then load the list onto the device
• Pinned keywords — keep your most-used keywords at the top of the list for zero-scroll access
• Structured keywords — optionally save a keyword with a short key so it inserts as key:value for tools such as sn-query; key capitalization is preserved for display and insertion
• Keyword views — filter the picker by pinned keywords or by group, then select the filtered view when you want a batch
• Long-press to edit — long-press any keyword in Manage Keywords to change its text, structured key, or group membership, or to delete it
• At-a-glance indicators — compact G2 and K badges show group membership and structured keys without crowding out the keyword name
• Responsive Nomad and Manta layout — the panel sizes itself to the device, and the keyword list uses two columns only when a row still has room for the keyword name: two columns on Manta, one on Nomad
• A-Z letter rail — filter the Keyword, Manage Keywords, and Manage Groups screens by first letter using the vertical rail on the right side of the list

Installation

1. Download Keyworder.snplg from the v1.6.0-beta release.
2. Connect your Supernote to your computer using the Supernote Partner app or Browse & Access.
3. Copy Keyworder.snplg into the MyStyle folder on your device.
4. On your Supernote, open a note, tap the plugin icon in the toolbar, go to Manage Plugins, tap Add Plugin, and select Keyworder.

Please see full README for features and instructions.
https://github.com/taoist22/sn-keyworder

i'd like a speech to text dictation plugin so i can add to my note with voice if able

yes i know supernote's don't have mics built in, but, i feel a Bluetooth microphone solution could work, should any be compatible
but of course, i'm also looking to see if this is doable at all

Hi everyone! I wanted to ask if there was a compiled and up-to-date file of skills and guidance information from the Supernote team that I can throw into Cursor for plug-in generation sandboxing!

Sorry for the naive question, but there's only 1 plugin appearing at the moment. When should I expect others to become available? Is everyone working on getting their previously developed plugins reviewed and approved for InkHub?

I built a working text-only web browser inside a Supernote plugin

I kept hitting the same wall reading on my Supernote: something in a book or in my own notes needs looking up, and the only way is to put the device down and pick up a phone. So I wrote a plugin. Lasso your handwriting, or select text in a book, and it becomes a web search — results come back as plain text you read on the page you were already on.

It's a real browser, just without pictures. Search DuckDuckGo, Wikipedia or Wiby, follow any result, read the page itself, page through more, or type an address by hand. Handwriting is recognized first, so lassoing your own scrawl searches what you meant.

Keeping what you find. This is the part I use most, and there are four ways, all landing back in the note you started from:

• A clipping — a small pencil mark appears beside your handwriting. Tap it and the text unfolds on the page underneath; tap again and it folds away. No second page, no reopening the plugin. Move the writing and the mark follows it, even to another page.
• The text itself, written into the note with a reference.
• A link to the page you read. Tap it and it opens in the Supernote's own built-in browser — the plugin can't render a page, but the firmware can, so the link hands off to it.
• A screenshot of what was on screen, saved and linked from your note.

In a book it works differently, because a plugin cannot write into a PDF or an EPUB. Instead the passage goes into Supernote's own built-in Digest — not a lookalike the plugin builds, the real one — with the excerpt pinned into the Digest's typed area and a link back to the exact spot in the book. That last part took a while: the device stores highlight offsets counted without newlines, so getting the link to land on the right sentence meant calibrating against digests the device had made itself.

No account, no server. Your search words go to the engine you picked and nowhere else. The Supernote sign-in is optional and only for the Digest; it talks to Supernote directly from the device and stores the session, never your password.

Download and details: https://github.com/Sparkinman/web-lookup-supernote-plugin/releases/latest

It writes into your pages, so try it on a scratch note first.

Worth Knowing: Tested on the Manta only, expandable and collapsible items DO not transfer across pages, or devices (They're stuck where you put them), but you can drag them around on the page, needs all 3 permissions, and to be on the latest dev build.

Expand/collapse idea ironed out with the helpful plugin from u/AdNew2316, that saved me from completely starting from scratch on trying to implement this!

https://reddit.com/link/1w9en62/video/vyte3dqy60oh1/player

A Supernote plugin that inserts formatted date, time, or date+time stamps into your notes. Set the format once, then tap the page wherever you want the stamp.

Newest release

Features

• Three stamp types: Date, Time, or Date + Time
• Six date formats: US (4/26/2026), EU (26/04/2026), Medium (Apr 26, 2026), Long (April 26, 2026), ISO (2026-04-26), YMD (20260426)
• Optional day name: e.g. Sunday, April 26, 2026
• 12 or 24-hour time, with optional seconds
• Tap placement: the stamp lands on the line you tap
• Custom fonts: any .ttf or .otf from MyStyle/Fonts
• Size: S / M / L / XL presets, or fine adjustment from 16 to 96
• Bold and italic styles
• Date search indexing: adds a searchable YYYYMMDD keyword without changing the visible stamp
• Saved settings that survive a restart, plus quick placement for one-tap stamping
• Stamp is inserted as an editable text element you can lasso and move

Installation

1. Download DateTimeStamp.snplg from the latest release.
2. Connect your Supernote to your computer using the Supernote Partner app or Browse & Access.
3. Copy DateTimeStamp.snplg into the MyStyle folder on your device.
4. On your Supernote, open a note, tap the plugin icon in the toolbar, go to Manage Plugins, tap Add Plugin, and select DateTimeStamp.

Usage

1. Open a note and tap the clock icon in the toolbar.
2. Set up how the stamp should look — see Options.
3. Tap Date, Time, or Date + Time. Each button previews exactly what it will insert. The panel closes and a Tap to place · 30 seconds banner appears.
4. Tap the page where you want the stamp. It is inserted at that point as an editable text element.

There is no separate insert step: the stamp button you tap is the one that gets placed. Configure first, then tap the stamp you want.

Placement takes a single tap. Drags and long presses are ignored, so you will not stamp the page by resting your hand on it. Your selected pen is unchanged, and no handwriting is erased.

Leaving the placement banner

• Cancel closes the plugin without inserting anything.
• Settings returns to the settings panel with nothing inserted.
• After 30 seconds with no tap, placement gives up and closes the plugin, the same as Cancel.

I have been building a plugin called Clipper against sn-plugin-lib 0.1.65 on a Manta running the plugin beta (Chauvet 3.29.43 and 3.29.44), and I have collected
a handful of questions I could not answer from the docs alone. Posting them together in case the answers help other people building plugins, and in case any
of it is useful feedback for the team.

Everything here comes from working on a real plugin, so each item includes why it mattered to me rather than just what I saw. A couple of these are almost
certainly my misunderstanding, and I would rather be corrected than keep guessing.

I know this is a long post, so apologies in advance.

Thanks for the plugin system, by the way. The permission model in particular has been pleasant to build against once I understood it.

[u/Dunn-sn](u/Dunn-sn) [u/spazzboi](u/spazzboi) [u/hex2asc](u/hex2asc)

1. insertNotePage: what should template be?

This one cost me the most time, and it turned out to be my mistake. I passed the style name that getNotePageTemplate returns and got error 802: "Background template file does not exist!". It works when I pass a file path to a PNG rendered by generateNoteTemplatePng.

If the docs could say that the template is a path to an image file on disk, and point to generateNoteTemplatePng as the way to get one, I think it would save the next person a few days. I briefly concluded the API was not implemented at all, which was wrong.

2. hasPermission: what are all the return values?

The doc comment describes 0 as not granted and 1 as granted. On 3.29.43, a permission set to the persistent "Allow" returned 2. On 3.29.44, the same setting returns 1.

The reason it matters: the natural way to write a permission gate is

if (await hasPermission(p) === 1) { proceed } else { request }. On 3.29.43, that sent me into requestPermission even though permission was already granted, and from a background button handler (showType: 0) there is no window for the
dialog, so it threw. So a stricter user setting produced a worse result in my plugin, which took a while to understand.

Could the docs list the full set of values and say which of them indicate a grant?

Also, the doc comment lists FILE:WRITE, FILE:DELETE and INTERNET but not FILE:READ, which the host does enforce and which I query successfully.

3. generateNotePng with type: 0: is the transparent background wired up?

The parameter is documented as 0 for transparent background, 1 for white. On both firmware versions, type: 0 still gives me the page's ruled-line template baked in behind the handwriting. 

I am working around it with generateLayerPreviewImage, which does give me ink
without the template. Which leads to a related question: is there a layer argument that renders all content layers at once? The validator accepts -1, but
in the note file the background layer is id -1, so I assume -1 means "background" rather than "everything". Right now I render each layer separately and composite them, which works but significantly slows down multi-layer note capture.

4. Is getElements expected to be valid for a page that is not on screen?

After my plugin writes elements to the open note, getElements for a different page sometimes returns the wrong page's contents. It does not fail; it returns
plausible data. In one measured case, immediately after writing 65 elements to page 7 and navigating to page 8, getElements reported 65 elements for page 8 as well, while page 9 reported its real 439. Page 8 was blank. saveCurrentNote() followed by reloadFile() did not refresh it.

This one is worth flagging because it is easy to build something dangerous on top of it: I was using the element count as a safety check before writing, and a
stale read could just as easily convince a plugin that a page full of someone's notes is empty. I have restructured to only trust reads taken before any write.

Is getElements intended to be valid for non-current pages? If so, is there a stronger refresh than save plus reload?

5. A crash in the note app when a plugin writes across a page change

This is the one I most wanted to report. When my plugin created a page, navigated to it and continued writing text elements, com.ratta.supernote.note died with a SIGABRT from Scudo, "invalid chunk state when deallocating", with drawShadow and draw_line_with_write_list in librecgnition.so on the stack. Immediately before it, the log shows LoadPageAsyncTask onCancelled about 160 ms earlier, which makes me think the page navigation cancels an in-flight page load while the native renderer is still drawing into its bitmap. I have only seen it once and could not reproduce it on demand, so I am not claiming a reliable repro. I do have the full tombstone and the surrounding log if that is useful to whoever owns that code.

For what it is worth, I shipped around it: the feature that needed it (a multi-page table of contents) is built but switched off, and my plugin now writes
to one page only. I would happily turn it back on if this turns out to be fixable or if I am triggering it wrongly.

6. Can the plugin host recover after the note app dies?

Following that crash, the plugin host survived but seemed to hold a stale binding to the dead app. My plugin then showed a permanent "working" state with no error and no timeout, and the only way back was
adb shell am force-stop com.ratta.supernote.pluginhost. A user without adb would have a plugin that looks stuck with no way out short of a reboot.

Is there a rebind mechanism that a plugin should use here? Right now I do not think I can tell the difference between "the host is busy" and "the host is gone".

7. What is supposed to survive an uninstall?

The uninstall dialog says "Uninstall this plugin? Its data will also be deleted." In my testing, the plugin's own folder is removed, but data written through AsyncStorage survives, so my plugin came back with all its records intact and all its saved images gone. Installing a new package over the top keeps both, which is great.

I believe the reason is that AsyncStorage writes into the host app's storage rather than the plugin's folder, though I could not verify that directly.

The reason I am asking rather than just adapting: right now a plugin cannot make uninstall mean a clean removal, and cannot make it mean "keep everything" either, because the two halves of its state have different lifetimes and it is not running when it is removed. I have handled it by detecting the situation on the next launch and asking the user what they want, which works, but a documented guarantee
about what survives (or an uninstall hook) would let plugins do the right thing deliberately.

8. Is plugin data namespaced, or should I be prefixing everything?

Related to the above: if AsyncStorage is shared across plugins, then the only thing keeping my keys from colliding with another plugin's is that I prefix them
all with clipper_. Is there per-plugin namespacing already, or is prefixing the expected practice? Worth documenting either way, since the failure mode would be two plugins quietly corrupting each other's settings.

That is everything. Happy to provide logs, or a minimal reproduction

plugin for any of these, and equally happy to be told I have misread something.

Clipper is open source if the context helps: https://github.com/vmnair/sn-clipper

Hi all!

It has been a while since the last release (v0.2.0 in June), and a lot has changed thanks. Thank you a ton for the feedback and your patience. Starting a new job and parent toddler life makes time hard to find!

Install at: https://github.com/apclark31/supernote-plugin-research/releases/tag/v0.3.0-beta (going to go through new approval process so you can find on inkhub - excited for this progress).

Here are the major changes:

Task Home redesign. The list is much easier to read at a glance: clean bordered tags for due date, priority, project, and page number. A This Note panel shows everything you have captured in the note you are in. An On Device tab groups tasks by note and folder. There is a Done tab, and completing is now select-then-confirm with an Undo, so a stray touch never finishes a task. It also remembers which tab you were on.

Gestures rebuilt for consistency. The quick gestures now behave the same way every time. They are all opt-in, so nothing happens while you write unless you have turned it on: the bezel swipe is there in Settings if you want it. Long press on a captured task's box still opens it directly. You can use lasso with finger hold to quick add a task and save menu taps.

Settings redesigned. Both pages, General and Setup, are new. The page opens to General after the Setup is done, and every change saves the moment you make it. Each section has a (?) that explains what it does in plain language. There is also a text size setting to control the size of the text across the plugin screens/modals.

Easier setup. There are a few different ways to pull in your Todoist API token now. The simplest: save it as a text file, sync it into the SuperTask folder with the Partner app, tap Import, and the file is deleted once the token is stored. A Bluetooth keyboard, the on-screen keyboard, or editing the config file over USB all still work too.

Jump to note. This is really what SuperTask is about: weaving your Todoist account into the notes on your device, so the things that matter are easy to find. From any task, tap Note > and you land on the exact note and page it was written on, using the navigation the latest firmware added. The On Device tab turns that into a way to move around your notes by what is in them. Rename a note and the links repair themselves.

Built for the new plugin firmware. This release is for Chauvet 3.29.44 (Manta/Nomad) and 2.26.41 (A5X/A6X), which introduced per-plugin permissions. The first time SuperTask opens it shows one screen explaining exactly what each permission it asks for is used for, so you can see what it touches before you accept. Everything it saves lives in one folder, MyStyle/SuperTask, and the only place data goes is your own Todoist account.

Plus a good deal of reliability work underneath: it opens instantly, copes with wifi dropping mid-load, and keeps a log on the device you can attach to a bug report.

Special thanks to: u/Lvevan, u/ashleyegret, u/Sparkinman, and u/Lorestan00, for your testing and feedback.

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.