In Phase 1, we aim to make the modcore Extension Manager's code, design, performance, and overall operation more robust and seamless. This includes the following key initiatives:

Core Objectives:

• Completely overhaul the technical foundation to improve scalability and maintainability.

• Reduce loading times by optimizing performance, especially on older devices.

• Enhance the Permission/Security Scanner (located on the "Detail Page" and the "Security Center" page of the modcore Extension Manager) to be more accurate and reliable.

• Refactor the codebase by removing unnecessary legacy code and consolidating duplicated code into independent, reusable modules.

• Minimize resource consumption (e.g., CPU, memory usage).

In Phase 2, our goal is to make the modcore Extension Manager more intuitive, useful, and personalized for you. This will involve the following changes:

Key Improvements:

• Enhance user-friendliness and intuitiveness across the entire extension.

• Grant users more control to customize the modcore Extension Manager's user interface (UI) according to their preferences.

• Introduce a new Theme System:

  • This will allow users to easily switch between Light and Dark Modes (currently, the manager only adapts to your system's preference, e.g., if your PC/browser is in Dark Mode).

  • The new system will also enable users to apply custom CSS code to further manage and personalize the UI. This will facilitate the sharing of custom themes within the community.

• Implement a significant overhaul of the UI and layout design to make it both more user-friendly and visually appealing.

• Develop a "Quick Search" feature (Command Palette):

  • This function will allow users to quickly navigate and search through extensions, modcore Extension Manager features, and more.

  • For instance, pressing a keyboard shortcut (e.g., Shift + S) will open the "Quick Search," displaying all installed extensions with common actions, other features (like the modcore Automations page), and much more.

• Improve the documentation (here and within the modcore Extension Manager itself) to offer more built-in assistance and help.

In Phase 3, we will focus on expanding the modcore Extension Manager's Marketplace and integrating it more closely with the modcore Extension Manager itself.

Expansion Goals:

• Open the modcore Extension Manager's Marketplace to all users and developers, promoting a more inclusive ecosystem.

• Allow users to seamlessly browse, purchase, manage, and download items directly through the Marketplace.

• Implement stricter guidelines for developers to ensure the Marketplace is not filled with opaque, low-quality, or harmful items. We aim to maintain a high standard of quality and safety.

• Integrate the Creator Program more closely into the Marketplace experience.

• Establish more transparent and clearly explained submission processes for items being added to the Marketplace.

• Implement a more transparent revenue-sharing model that includes strict and easily understood guidelines for all participants.

In Phase 4, we aim to make the modcore Extension Manager faster and more useful for all users, reduce user workload, and add deeper insights into your installed extensions. This includes the following changes:

Core Enhancements:

• Provide users with more insights into their installed extensions, such as the extension's category (e.g., Shopping, Productivity).

• Automate common tasks using Automation Rules, and offer recommendations that users can leverage for quicker automation setup.

• Integrate optional AI-powered features within the modcore Extension Manager that users can utilize to:

  • Explain various modcore features, extension permissions, or the extensions themselves.

  • Assist in decision-making regarding extension management.

  • Note: AI features will be optional, completely switchable off at any time, and will only function with the user's own API keys for privacy and control.

• Implement extension usage insights and an improved Permissions Dashboard.

• Introduce smart recommendations for various features. For example:

  • Suggestions to automatically disable an extension because it collects certain data when active.

  • Recommendations to create an automation rule that deactivates all non-essential extensions during work hours.

modcore plans to make the modcore Extension Manager available in various languages ​​in the future. The currently planned languages ​​are English (default), German, French, Spanish, Italian, Russian, and Japanese.

You can find information about the planned Offline Mode here.

nodcore plans to add several filters to the popup page of the modcore Extension Manager. These filters could include, for example, "Filter by Category" or "Filter by Profile".

modcore plans to make modcore Automations even more innovative. In fact, we have many more plans in this area, so we'll be updating this post in the coming days with all the details about the modcore Automations feature. Sorry about that!

modcore is planning to introduce a new filter feature for the Permissions panel on the Details page. A filter icon will appear alongside the existing layout controls (which let users switch between different views). When clicked, a compact dropdown menu will expand beneath the icon, allowing users to refine the displayed permissions—such as filtering by risk level or other relevant criteria.

Good news (since 1.1.2026): In modcore Extension Manager 2.3.9, permission filters will be available on the details page.

modcore plans to expand the information shown in the “Support Developer” panel on the Details page. Instead of displaying only links to external developer resources, the panel will surface richer, more dynamic data when active.

Examples include:

• Expanded developer profile information, offering deeper insight into the creator behind the extension

• Additional context and metrics that help users better understand and support the developer

modcore plans to make the sidebars on different pages of the modcore Extension Manager resizable. This means that users will be able to drag the sidebar left or right to reveal more content.

modcore plans to integrate an archive feature across various pages of the modcore Extension Manager. This means that, for example, users will be able to view older scans in modcore Inspect, access archived logs in the modcore Timeline, or review archived automations in the modcore Automations page.

modcore would reduce the size of archive entries so they consume less storage space. The archive function should also be able to be disabled.

modcore plans to consolidate all settings from the various pages of the modcore Extension Manager into a single, unified settings page.

modcore plans to expand the 'Support the Developer' program. This means that the API will now allow extensions to receive 'Recommended' or 'Verified' badges, giving these extensions greater recognition and making them feel safer for users.

modcore plans to release a free add-on designed to help users diagnose and resolve problems or errors. This optional tool will provide troubleshooting assistance.

modcore plans to replace the documentation links shown in the 'Permissions' section of the details page with an 'Extended Permissions View' icon. This enhanced view will provide more in-depth explanations, optional AI assistance, usage examples, and additional guidance.

Once the Universal Settings Page is fully designed, modcore plans to introduce a range of accessibility options—for example, high-contrast mode, reduced animations, dyslexia-friendly features, and more.

Reduced animations are already partially supported in the modcore Extension Manager, but this currently depends on your system settings.

!! This is not an active plan—just a rough idea that would be extremely difficult to achieve !!

modcore is considering an idea where, during the initial setup of the modcore Extension Manager, users could optionally send data—such as their installed extensions—to modcore’s servers.

modcore would then compile this data anonymously and publish it on a public website, creating a “library” of extension statistics. This could include information such as how many people have a certain extension installed, which features are used most often, and more.

However, we are not planning this at the moment because it would be extremely difficult to implement. Building such a system in an open-source project is nearly impossible in practice, and it would also come with significant legal and privacy challenges.

!! THIS IS NOT PLANNED, AND IT IS VERY UNLIKELY TO EVER BE IMPLEMENTED. MODCORE WILL KEEP THIS IDEA IN MIND, BUT WILL NOT EXECUTE IT !!

This is a very ambitious and extreme idea from us, and it is quite possible that it will never be executed.

modcore is considering building an independent extension archive platform. The concept is to store multiple versions of browser extensions (CRX files) on modcore’s servers and make them freely available on a website. This would allow users to manually downgrade to older versions of a Chrome extension at any time.

Because manually collecting and archiving every extension version would be an enormous effort, the process would rely on community participation:

• The open-source version of modcore Extension Manager would remain unchanged.

• The private version of modcore Extension Manager (for example, versions distributed through platforms such as Microsoft Edge Add-ons) could optionally download the installed extensions (CRX files) and their version numbers from the user’s device and securely submit them to modcore’s servers.

• This would strictly operate under an opt-in system.
  
  

No personal or anonymous user data would be stored. modcore would only retrieve extension files directly from official platform providers (such as Chrome Web Store or Microsoft Edge Add-ons), never from user-developed or sideloaded extensions. This ensures higher security and authenticity.

How the Process Would Work

If a user explicitly agrees to modcore’s policy, they would grant permission for modcore to collect the CRX files of extensions installed from official stores on their device.

A CRX file contains the complete extension package, but it does not include the user’s personal data stored inside the extension.

Once submitted:

1. modcore’s servers would verify the CRX file.

2. The file would be securely archived.

3. The extension version would be published on a dedicated “modcore Extension History” website.

4. Detailed metadata and version information would be displayed.
   
   

The goal would be to create something similar to an independent extension history platform.

There would be no account system on this website. Only modcore would have access to extension submissions (if users opt in). modcore does not want to expose such sensitive mechanisms to potential abuse, so a secure infrastructure would be required to prevent exploitation or compromise of user systems.

When the Universal Settings page becomes available, modcore plans to offer the following customization options for the popup:

• Adjust the number of extensions displayed per page
  (currently set to 12 by default).
  There is a workaround: open the popup.js file and modify the value in CONSTANTS —
  const EXTENSIONS_PER_PAGE = 12;
  
  

• Icons-only mode for action buttons
  Instead of always showing labels like “Disable/Enable” and “Details,” users will be able to choose whether action buttons display both text and icons, or icons only.
  This does not apply to “Uninstall,” as keeping that button clear is important for UI clarity and safety.
  
  

• Compact mode for the extension list

For the modcore Timeline feature, we have many ideas in mind. The following functionalities are planned for future integration into modcore Timeline:

1. Event Cause Transparency

Users should be able to clearly understand why an event occurred.

An event may be triggered by:

• The user

• An automation

• A profile

• A group

• The system

Timeline entry example:

modcore Extension Manager disabled 

Cause: Automation “Work Profile”  

Trigger: URL match (github.com)

2. Undo Actions

Users can instantly revert actions directly from the timeline.

Examples:

• If an extension was disabled, it can be re-enabled with one click.

• If an extension was uninstalled, a direct link to the Chrome Web Store page of the extension is shown.
  
  

3. Grouped Sessions

Instead of displaying a long list of individual extension changes, modcore EM will group related events into sessions.

For example:

• If an automation disables 12 extensions, modcore Extension Manager will group them into a single session such as:
  “Automation triggered: Work Mode”
  
  

This keeps the timeline clean and easier to understand.

4. Extension Insights (Local-Only Data)

modcore aims to introduce an Extension Insights system that collects local data only. All data remains on the user’s device and is never uploaded.

Using this data, modcore Extension Manager can provide insights such as:

• Most frequently enabled, disabled, updated, or permission-changed extensions

• Extensions affected by automations, profiles, or groups
  
  

Example insight:

“This extension was disabled 14 times in the last 7 days.”

5. Pin Important Extensions

Users can pin important extensions to the top of the timeline.

Pinned extensions will always be shown first, allowing users to immediately see activity changes related to extensions they care about the most.

6. Search Assistance

The timeline search will offer intelligent suggestions while typing, such as:

• Extension names

• Event types

• Triggers and causes
  
  

This makes finding specific events faster and easier.

7. Notes

Users can attach personal notes to any timeline entry, making it easier to document why a change was made or add contextual information for future reference.

modcore plans to reintroduce the drag-to-reorder feature. It will become available again in the following areas:

• Selecting and rearranging extensions in the list

• Selecting and rearranging profiles in the list

• Selecting and rearranging groups in the list
  
  

The feature was previously removed due to several technical issues.

If you hover over an extension in the popup for a certain amount of time, modcore plans to display additional information instead of only showing the extension name.

Details may include, for example:

• Extension name

• Permissions (names only, separated by commas)

• Host permissions (separated by commas)

modcore plans to make bulk actions in the popup of the modcore Extension Manager smarter and more advanced.

This includes:

Smart Select – With Smart Select, users will be able to select all extensions based on specific criteria. For example, they could select all extensions that request the "activeTab" permission and then disable them, or apply other filters to perform bulk actions.

modcore plans to add a clear indicator to groups and profiles to show whether the groups or profiles are stored locally or also synchronized in the modcore Cloud.