Feature request

What is Deskmode missing for the way you work?

A lot of what is in the suite today started as a message from someone using it every day. Tell us the problem you are trying to solve — we read everything, and we reply if you leave an address.

Frequently asked

How requests work

What happens after you hit send, and what we can honestly promise.

What happens after I send a request?

We read every one. Each lands in a list alongside other requests on the same theme: when five people ask for the same thing in five different ways, it's that grouping that makes us notice.

If you left an email address, we write back to tell you which way we're going — including when the answer is "not now".

Will you build everything you receive?

No, and we'd rather say so here than let you work it out from the silence. An admin panel gets worse every time you add an option that serves a handful of people: the extra feature is paid for in complexity by everyone who will never use it.

The requests most likely to make it are the ones that solve a recurring problem, fit into a module that already exists, and don't require the user to configure anything to work.

How do I know whether someone already asked for it?

You'll find the requests we've received and their status at {{link or page showing request status}}. If yours is already there, write in anyway: a second message on the same theme isn't a pointless duplicate, it's the signal that more than one person needs it.

Can I ask for integration with another plugin?

Please do — these are among the most useful requests we get, because they often flag a conflict before it turns into a bug report.

Give us the exact plugin name, its version, and what you'd want to happen when the two work together. If the plugin is commercial, say so: it changes how we can test it.

Do I have to leave my details?

No. The email address is optional and exists only so we can reply: without it we still read your request, we just won't know where to write.

If you do leave it, we use it only for this conversation. It doesn't go on any mailing list, and you can ask us to delete it at any time. The details are in the privacy policy.

Planned | In Development

What we are working on

These are the directions we are heading in. They are not promises with a date: they are here so you can tell us which one you need first, and because knowing what is coming matters when you pick a tool you intend to keep for years.

AI-assisted features

The plugin already gathers the right data: a health score with its reasons, an activity log, failed email deliveries. What is missing is turning that into a useful sentence — what to fix first, what an SMTP error actually means, what happened on this site this week.

The key is yours. Pick the provider you already use and enter your own credentials: requests go from your site to your subscription, without passing through our servers. With no key these features simply are not there — you will never be asked to buy anything from us.


Revision cleanup

Every time you save a page, WordPress keeps a copy. On a site with a few years behind it those copies are often the heaviest thing in the database, and nobody ever looks at them.

We want to add them to the database tools already there: how many there are, how much space they take, and the option to keep a fixed number per item rather than deleting the lot. With a preview of what would go before anything goes, as with search and replace.


Core file integrity

WordPress.org publishes official checksums for every release. Comparing them against the files on your server tells you in seconds whether anyone has altered the core: it is the most direct way to catch injected code, because it does not hunt for suspicious patterns — it looks for differences from the original.


Active Theme Security Scanner

Protect your WordPress site from hidden vulnerabilities and backdoors. This upcoming feature will introduce an automated static code analysis tool specifically designed to inspect your active theme and templates for malicious code.Many nulled or compromised themes contain hidden scripts that hackers use to inject spam, steal data, or redirect your traffic. Our built-in scanner will proactively detect these threats before they can harm your site.


File and folder permissions

A world-readable wp-config.php, or an uploads folder writable where it needn't be, are quiet faults: nobody notices until someone uses them. The check compares real permissions against the recommended ones and flags only what differs.

With a distinction that matters: what you can fix yourself, and what depends on how your host is set up.


Honeypot: Bot traps

An invisible field on the login form: a human never sees it, an automated script fills it in. Whoever fills it has just identified themselves as a bot, and gets stopped — without putting a captcha in front of everyone else.

Alongside a decoy admin address: anyone looking for it is not administering your site, they are probing it, and they go straight into the log of suspicious addresses.


Traffic from the Tor network

Tor is not a threat in itself: it is also the tool of people with legitimate reasons not to be identified. But a login attempt on your dashboard arriving from a Tor exit node deserves a different look from one arriving from your own office.

The list of exit nodes is public and kept current. The idea is to flag them in the activity log, and leave it to you whether to restrict them or simply know.

Missing something you need? Tell us. Nearly every feature in the plugin today started as a real problem someone ran into, not as a line on a roadmap.

Do you have a request? Fill out the form!

Data is processed based on your consent or our legitimate business needs. Read our full Privacy Policy for details on your data rights and retention.
Shopping Basket