Who it is forA developer at a company running WorkDSH Enterprise Desktop who needs an internal plugin that reads business data for signed-in employees.
The problemEach internal plugin would otherwise need its own login flow and token handling, which is slow to build and risky to get wrong.
The outcomeA Host plugin that reads the current member identity and calls a business endpoint on the company backend under that member's login.
What you need first
- WorkDSH Desktop downloaded from the project's release page
- A personal project goal, or a company account if you need enterprise features
- Enterprise Connection plugin file, only for the collaboration and business plugin use cases
Steps
- Install and activate Enterprise Connection, then sign in to the company account in Desktop.
- Write the Host entry for your plugin so it injects workdshEnterprise and does not run in the browser page.
- Call identity() to get the current member, then call request() with the plugin name, operation, method and body.
- Implement the matching business endpoint and its authorization on the company backend, without another login flow.
- Read the integration guide to package the type dependency and check request restrictions before shipping.
Prompt for your agent
Using the WorkDSH repo at techflag/workdsh, write a Host plugin named <plugin name> that injects workdshEnterprise and calls the business operation <operation> on the company backend. Expected output: a plugin entry that returns the member identity and the list response. Verify that the request reaches the POST endpoint under /api/extensions/ and that the backend rejects members without permission.
Caveat. The README's example requires Desktop 2.0.6-alpha.3 and Enterprise Connection 0.1.0-alpha.2, and workdsh-contracts is not a published public npm SDK, so you must package its type dependency yourself.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page