Create and contribute a Kitsuvo plugin
Start with a small, data-only package. Test it in your browser, explain what it does and share it for review.
← Back to the plugin marketplace
What you can build today
Kitsuvo browser plugins are UTF-8 JSON files ending in .kitsuvo-plugin. They select capabilities implemented by the browser. Packages cannot run JavaScript, native code or arbitrary commands, and installing one does not grant page or saved-library access.
The current runtime accepts three reviewed IDs: twitch-streaming, qwen-chat and coding-session. You can customize a supported package's name, description and, for streaming, Twitch shortcuts. A new ID or capability needs a browser implementation and maintainer review before it can install. There is no general extension SDK yet.
Browser plugins are separate from plugins that connect an AI client to Kitsuvo. For assistant skills and MCP packages, use the integration guide.
Choose a supported plugin type
| Runtime ID | Useful customization | Requirements and limits |
|---|---|---|
twitch-streaming | Name, description and up to eight approved Twitch shortcut actions. | Streaming cover is provided by Kitsuvo; a package cannot add a new masking implementation. Check the streaming privacy limits. |
qwen-chat | Name and description for the existing on-device chat capability. | A package does not contain a model or change model behavior. The user downloads a supported model separately and explicitly chooses page context. |
coding-session | Name and description for the existing coding-session capability. | Desktop only; the user needs a supported coding client and chooses when to connect. A package cannot run shell commands or add a coding provider. |
If your idea needs a new runtime ID, arbitrary website actions or executable code, start with a capability proposal. Renaming one of these packages cannot supply that behavior.
1. Create a working package
Copy this example into a plain-text file named my-streaming.kitsuvo-plugin. Keep the twitch-streaming ID: changing the filename or display name does not create a new runtime capability.
{
"schema": 1,
"id": "twitch-streaming",
"name": "My streaming shortcuts",
"version": "1.0.0",
"description": "Local page cover and a shortcut to my Twitch stream manager.",
"streaming_privacy": true,
"actions": [
{
"label": "Stream manager",
"url": "https://dashboard.twitch.tv/u/{channel}/stream-manager"
}
]
}
{channel} is replaced with the channel you enter in Kitsuvo. For example, you can add a shortcut to https://www.twitch.tv/{channel}. Only HTTPS links on www.twitch.tv or dashboard.twitch.tv are accepted; credentials and explicit ports are rejected. Shortcuts open when the user chooses them.
A customized package uses the same installation slot as the original ID. Installing this example replaces the installed Twitch package rather than adding a second streaming plugin. Save your original package if you want to restore it.
2. Follow the package rules
- Use
schema: 1and keep the file at or below 16,384 bytes. JSON must have no comments or trailing commas. - Include
id,name,version,description,streaming_privacyandactions. Unknown fields are rejected. Use a version such as1.0.0and increase it when sharing an update. - Keep the name nonempty and at most 80 UTF-8 bytes, version at most 32 bytes, and description at most 800 bytes. Non-ASCII text can use more than one byte per character.
- Streaming packages use
id: "twitch-streaming"andstreaming_privacy: true. Omit other capability flags for mobile compatibility. Include at most eight actions, each containing onlylabelandurl. Labels must be nonempty and at most 80 UTF-8 bytes; URLs at most 512 bytes. - Chat packages use
id: "qwen-chat",local_chat: true,streaming_privacy: falseandactions: []. Omitcoding_sessionsfor mobile compatibility. The local model download and explicit page-context choice remain separate. - Coding packages use
id: "coding-session",coding_sessions: true,streaming_privacy: false, false or omittedlocal_chatandactions: []. Coding sessions require desktop and a supported coding client.
Streaming and chat have runtimes on Windows, macOS, iOS/iPadOS and Android; installed app versions and model support still matter. Coding sessions are Windows/macOS only. Browser extensions do not install these native browser packages.
3. Install and test locally
- Use a Kitsuvo version with Browser plugin marketplace in Settings. Choose Install downloaded plugin and select your file.
- Check the preview's name, description and permissions before confirming. If Kitsuvo reports an unsupported package, check the ID, flags, field names, size and action URLs above.
- Confirm streaming or chat starts off, then enable it explicitly. Test each shortcut with a test channel and check the cover on a harmless page. For chat, download the model separately and verify page context requires your choice. For coding, connect only to a session you choose.
- Disable and remove the package in Settings. Check that its controls are removed or disabled, then reinstall the original package if you replaced one. Removing chat does not remove the model used by other browser features.
Test every platform you claim to support and report the app version. A desktop test does not establish mobile behavior. Streaming cover and form blurring have limits: check the plugin's requirements and permissions before using it while broadcasting.
Check a package before sharing it
Local installation and marketplace submission are separate checks. Test the exact file you plan to upload, keep it below 16,384 bytes including whitespace and use a version such as 1.0.1. A desktop import succeeding does not prove that the listing's media, text or platform claims will pass marketplace review.
- JSON errors: use a plain-text editor, ordinary double quotes and boolean values such as
true, without comments or trailing commas. Keep unknown fields out of the package. - Unsupported type: use one supported ID with its matching capability flags. Chat and coding packages have no shortcut actions. Mobile submissions must omit
coding_sessionsentirely, even when its value would be false. - Rejected Twitch action: use the exact approved HTTPS hosts listed above. A different Twitch subdomain, embedded credentials or an explicit port, including
:443, is not accepted by marketplace submission. - Text too long: package and listing limits use UTF-8 bytes, so an emoji or accented character may count as several bytes. Shorten the field identified in the error instead of relying only on the visible character count.
4. Upload and request approval
Use Upload or update your plugin to create a listing. Save the listing ID and private management key; you need them to load the listing, submit updates or unpublish it. The site does not save your key in browser storage.
Upload a cover image, one to six screenshots and a short MP4 or WebM demo video. Images can be up to 2 MB each and videos up to 4 MB. Add image descriptions and a video transcript or text description. Include an author, distribution license, tested platforms, requirements and permission details.
Submit the completed listing for approval. Uploaded files remain private during review. A reviewer can approve it or request changes with feedback. Load the listing to see its status. Every package, text or media update requires approval again; the last approved version stays live until a replacement is approved. Choose Unpublish listing to remove the live version.
For unsupported plugin types, use a proposal first:
Email hello@kitsuvo.com with a title such as “Browser plugin contribution: My streaming shortcuts”. Include your contribution proposal and package details so maintainers can review it.
- Describe the problem your plugin solves and whether it customizes an existing ID or needs a new capability.
- Include the JSON in a code block or link to a public source repository, with your author name, version and license permitting review and distribution.
- List permissions, user-triggered network requests, setup requirements and known limits. Keep credentials, private session links and browsing history out of your submission.
- Include install/remove steps, screenshots and results for each tested platform and app version. Mark platforms you could not test.
For a new plugin type, start with the proposal so maintainers can review local data handling, permission boundaries and platform support. Arbitrary IDs will remain unsupported until the browser gains that capability. Contributions to the public assistant/MCP packages can use a pull request in the integrations repository.
Submitting an issue or hosting a package does not automatically add it to the marketplace. Catalog publication requires maintainer review, an accepted runtime contract and a downloadable package.
Questions people ask
Can I build a Kitsuvo plugin with JavaScript?
No. Current Kitsuvo browser plugins are data-only JSON packages selecting capabilities already implemented in the browser. They cannot execute JavaScript, native code or arbitrary commands. Propose a new capability before creating a package with an unsupported ID.
Can a custom plugin have a new runtime ID?
Not yet. The current runtime accepts twitch-streaming, qwen-chat and coding-session. A new ID needs browser implementation and maintainer review. A customized package with an existing ID replaces that plugin in its installation slot.
Is a Kitsuvo browser plugin the same as a Chrome extension or an MCP plugin?
No. A browser plugin installs inside Kitsuvo. The Kitsuvo Chrome or Edge extension installs in that browser. An MCP integration connects an AI client to the installed Kitsuvo desktop browser. Each uses a different package and setup flow.
Does a working plugin publish automatically in the marketplace?
No. Test the supported package, prepare the listing details and required media, then submit it for review. Every update needs approval; an older approved version stays public while a replacement is under review.