Skip to content

What's new for plugin authors

What changed in Kino that matters when you write a plugin, by app version. Every number is in the contract and the reference files.

Kino 0.9.88: titles ready ahead, live by clock, http pictures on screens

Available from Kino 0.9.88

apiVersion 27 (clockLive) arrives with Kino 0.9.88: an older Kino refuses "apiVersion": 27 and ignores an enhancements["27"] block. Everything else here is additive, with no new apiVersion: an older Kino ignores resolveAhead, never calls prepare, has no kino.pluginApiVersion and no kino.screen.httpImages, and drops a screen's http pictures.

  • Getting a title ready ahead. The manifest's "resolveAhead": true lets Kino call resolve for a movie or an episode once the person has stayed about 0.3 s on its title page, and play that answer if they press play within 20 minutes; only for a plugin whose resolve can ask the person nothing (an approved "fetchHosts": "any" and video from any server). Getting a title ready ahead.
  • Warming up before the play. The optional export prepare(ref), for a plugin whose resolve must never run for titles nobody plays (a quota per account, plays counted): Kino calls it at the same moment and ignores its answer, so it can warm a session or a token. 15 s, in the background, once per ref every 5 minutes, 6 a minute; node sdk/run.mjs . prepare <ref>. Warming up before the play.
  • Live by clock (apiVersion 27). A live stream may carry clockLive: the template, duration grid and anchor of a CDN that names its segments by a media clock, and Kino builds the HLS window itself, with no plugin call while it plays. Kino reads it from your feature apiVersion, so an empty "enhancements": { "27": {} } turns it on without raising yours. Live by clock.
  • kino.pluginApiVersion. Your feature apiVersion on this Kino: your apiVersion or the highest enhancements key applied. Check it, not kino.apiVersion, before you send clockLive. kino.pluginApiVersion.
  • http pictures on screens. A screen's pictures (an Image, a heroCard's image and logo, a CircleAvatar, the posters of titleCard, titleRail and titleGrid) may be http on a public host, as a Home poster: IPTV channel logos show. Check kino.screen.httpImages === true; headers still go only with https. http pictures.
  • Identity. kino.identity.telegram gives the token only to the author keys in kinoIdentity.tokenAuthors, now two; any other author gets the id and, with a challenge, the attestation, where Kino 0.9.87 answered permission_denied. Identity.
  • Screens. On the TV a plugin's button is 40 dp tall with 14 dp each side (it was 52 dp and 22 dp), and its own padding replaces that room (Buttons); each destination of a Scaffold's NavigationBar keeps its scroll, as each tab of a TabBar does (NavigationBar).
  • What people see. A "Continuar viendo" card opens the title page, and the install confirmation says "Abrir <name>" when it opens your screen (What people see).

Kino 0.9.87: themes that paint, and the site's saved data in the browser window

Available from Kino 0.9.87

The themes arrive with "apiVersion": 26, which an older Kino refuses as a whole; collect.localStorage and doneWhen.localStorage are additive inside apiVersion 20, so an older Kino ignores them and answers no localStorage.

  • App themes that paint (apiVersion 26). A theme may declare surfaces (a fill, a stroke and a glow for the buttons, the menu, the rail, the round buttons, the cards, the focus ring, the hero and the progress bar), style.gloss, layout (a framed hero and a floating rail, TV only), assets (a background picture and a font that ship in your repository, hash-checked at install), background.image, typography.fontFamily, and the tokens shape.heroRadius and shape.railItemRadius. Seven switches in Ajustes ▸ Experiencia visual let the person remove each effect on its own. Painted surfaces, layouts and files.
  • kino.visualBrowser: the page's localStorage. collect.localStorage: ["key", …] hands you the values of the keys you name, read from the page the window ends on, and doneWhen.localStorage closes the window once the page has saved them. The sheet lists the keys; storeAs still covers only cookies. The rules and a recipe.

Kino 0.9.85 and 0.9.86: protected streams in a list, and subtitles with their own text

  • ClearKey and a list of DRM options (apiVersion 24, Kino 0.9.85). A stream's drm may be a list, best option first, and a block may be type: "clearkey" with its keys. On a phone with Widevine L1, a license refused for output protection is retried once at L1. Kino 0.9.85 also replaces the player's zoom with a picture-format button.
  • A subtitle with its own text (apiVersion 25, Kino 0.9.86). A stream's subtitles entry may carry its own decrypted text (with format vtt or srt, at most 2,000,000 bytes) instead of a url; Kino plays it from a local file.

Kino 0.9.84: share cards, who calls a door, and thumbnails

Available from Kino 0.9.84

There is no new apiVersion: an older Kino drops go.plugin, ignores openFrom inside enhancements["20"], has no ctx and no kino.image, and ignores the fullscreen operation.

  • go.plugin (apiVersion 20). A button on your screen opens another plugin's screen, or its search, from its repository: { plugin: { repo, route?, args?, query? } }, only from the person's press or submit. Kino offers to install it when missing, respects the 18+ lock, asks «¿Activar?» when it is off, opens the route only if the target lists it in openFrom.routes, and otherwise searches that plugin for the query or opens its section. go.plugin.
  • openFrom.routes in the manifest (apiVersion 20, also in enhancements["20"]). 1 to 16 routes of your screen that other plugins' cards may open; your screen reads route.args in its open event. openFrom.
  • ctx.caller for providers. Every proto_ export gets a second argument, ctx, with the calling plugin: { id, repo, name, adult } (cut the @ref off repo before using it in go.plugin). ctx.caller.
  • kino.image.thumbnail(url, { maxWidth?, maxBytes? }). Kino downloads a picture under your plugin's network rules and answers a small JPEG as data: (32 to 400 wide, 2,048 to 32,768 bytes, 20 a minute). Check typeof kino.image === "object". kino.image.thumbnail.
  • Sharing to Kino Social. Kino Social will show the cards in a later version; until then a plugin shares with the share call of its wall door (Kino 0.9.81 and Kino Social 0.9.7), which leaves a draft the person reviews and posts. Sharing.
  • Full screen. The ui operation { fullscreen: true } hides Kino's title bar and the phone's bars for a full-bleed canvas, and { fullscreen: false } brings them back. Only your screen toggles it, so draw your own way out; the phone's Back always closes the screen. Local ui operations.
  • "Letra" for podcasts too. The music player's "Letra" button also shows on podcast items: an episode's transcript, an audiobook's or a reading's text. Lyrics.

Kino 0.9.83: saving where the person is, the player slot, and pictures that need a Referer

Available from Kino 0.9.83

A Kino before it refuses "apiVersion": 22 and 23, and ignores an Image's headers.

  • Saving where the person is (apiVersion 22). The progress capability and kino.progress (set, get, list, clear): Kino keeps how far along the person is in a chapter or a book, per profile, synced between their devices and in backups; resume is up to 1024 bytes of your own JSON that Kino never reads. Kino draws nothing: your plugin builds its own "keep reading" shelf from list. No consent line; refused in a job that runs for another profile; may be declared in enhancements["22"]. Saving where the person is.
  • The player slot (apiVersion 23). The playerSlot capability and the manifest's slot block: up to three small elements (a text, an icon, an image, a button) in the top-right corner of the TV player, on movies, series and En vivo channels, filled by your playerSlot(context) export and pressed through playerSlotAction({ id, context }). overlay elements show with the controls; a fixed one stays and asks the person in red, on each device. A clock is the example. A text can also say its size, weight, color and background, and any element its left and top, so the person can dress the clock from the plugin's settings (time zone included). The player slot.
  • Kino's new type, your screens unchanged. Kino's own screens move to lighter weights in this release; plugin screens keep the type scale they were designed against (headings still bold), so nothing changes for your screen.
  • Pictures that need a Referer. An Image takes headers: { Referer?, User-Agent? } (no new apiVersion), sent only when the picture's host, and the Referer's, are in your manifest's hosts: manga readers whose pictures answer 403 to anyone else. Pictures that need a Referer.

Kino 0.9.82: files on the device, swipe and theme borders

  • Files on the device (apiVersion 21). The files capability and kino.files: the person picks files or a folder, the plugin gets opaque handles, reads them by ranges or plays them with kino-file:<id>. It uploads nothing. Files on the device.
  • Swipe. onSwipeLeft and onSwipeRight on any node (no new apiVersion; an older Kino ignores them); on the TV they answer Right and Left once focus has nowhere further to go. Swipe.
  • data: images. An Image accepts data:image/png|jpeg|webp|gif;base64,… of up to 200,000 characters (a book's cover read from its file). An older Kino draws the fallback. Image.
  • Bars and heroes. AppBar and TabBar take divider: false; heroCard takes logo (https) and h (height); dense tightens the bar on a TV too (8 dp); the TV's tabs are text with a line under the picked one.
  • App themes. Optional borders (colors.border and shape.dialogBorder, menuBorder, headerBorder, cardBorder, panelBorder), logo.decor and light backgrounds when the theme brings its own readable text. App themes.

Kino 0.9.81: one compact bar and reader blocks for screens

No new apiVersion

These screen features are additive: they need the Kino version that ships them and nothing in the manifest. A Kino that does not know a property ignores it (an AppBar draws two bars at the normal height, an Image reads every fit as cover). mergeWithKinoBar and onBack are the apiVersion 19 features documented below.

  • Recommended for every screen: one compact bar. Set mergeWithKinoBar: true and dense: true on the AppBar of every screen, with a leading that is a real exit ({ close: true } on the front page). On a phone that is one 56 dp bar instead of about 150 dp of header; the TV ignores dense and a player panel ignores both. One compact bar.
  • AppBar: dense (4 dp above and below the row on a phone) and mergeWithKinoBar (one bar: your leading where Close was, your title where the plugin's name was). Scaffold: onBack (Back is sent to you instead of leaving). AppBar.
  • Readers (manga, comics, long documents): Image fit (cover, contain, width), focus and any w:h for aspect; SingleChildScrollView zoom and onScroll; pages reverse (right to left) and progress (segments, bar, none; up to 250 pages with bar or none). Scroll, Image, pages.
  • Routes: route.name is "main" when the screen opens without a route (Kino's Home, a card, the menu). Routes.
  • Six new recipes: a search view that Back closes first, a reader, a carousel, a card in Kino's Home that opens your screen, search inside the field and filters in a bottom sheet.

  • Plugin types are dynamic: a new type in a catalog entry, a store entry or a manifest (manga, audio-books: 2 to 24 lowercase letters, digits and hyphens, starting with a letter) appears as a filter chip by itself, named from its id. Declare it in the catalog entry: a Kino that predates the rule refuses a manifest that names a new type. categories.

Kino 0.9.81: apiVersion 20, plugins that use each other and a browser window the person drives

Available from Kino 0.9.81

apiVersion 20 ships with Kino 0.9.81. Every older Kino refuses a manifest with "apiVersion": 20 with «Este plugin necesita una versión más nueva de Kino»; a provides or consumes inside enhancements["20"] is ignored there instead. contract.json says maxApiVersion 20.

Feature Since How to tell
provides in the manifest: up to 4 doors other plugins can use, each with calls and streams, answered by the exports proto_<door>_<name> apiVersion 20, or enhancements["20"] at any apiVersion an older Kino refuses apiVersion 20 and ignores the enhancement
consumes in the manifest and kino.plugins.call(alias, call, arg): use another plugin's door through Kino, with seven error codes the same typeof kino.plugins === "object"
Streams: state.protocol.<alias>.<stream> = true on a screen and the protocol event in screenEvent apiVersion 20, with screen the same
A plugin that only provides: no capability, "hosts": [] apiVersion 20 an older Kino refuses apiVersion 20
A screen-only consumer (a non-empty consumes, capabilities exactly ["screen"]): "hosts": [] apiVersion 20 an older Kino refuses apiVersion 20
visualBrowser in the manifest and kino.visualBrowser.open: a web window the person sees and drives (to sign in, solve a challenge), with Kino's own consent sheet at every open apiVersion 20, or enhancements["20"] at any apiVersion kino.visualBrowser is undefined on an older Kino; kino.visualBrowser.available is false without a WebView
storeAs.spill: a cookie list longer than 500 characters goes over up to 3 more password settings, in one save; and the window's own timeoutMs replaces the opening call's time bound while it is up apiVersion 20, with visualBrowser the same
storeAs.thenEvent: after Kino writes the cookies into a password setting, it sends your open screen an event of your choice apiVersion 20, with screen the same
The consent line «Usa datos de <provider> (<door summary>)» on a consumer's install sheet Kino 0.9.81 —
  • The plugin protocol: one plugin opens doors (TMDB 1.3.0 and later opens movies), another uses them (the Cine Trivia game). Kino is the only middleman: it validates every request strictly and every answer loosely against the provider's declared types, at most 64 KB each way, 10 s per call and 30 calls in any 10 s per door. 18+ content never reaches a plugin that is not 18+, sealed secrets never cross, and nothing installs on its own: the consumer offers the provider with go.installPlugin. The plugin protocol.
  • The kit: node sdk/run.mjs --provider <folder> answers a consumer's calls from a provider on your computer; screenEvent protocol <alias>.<stream> polls a stream once. Testing offline.
  • A browser window the person drives: with "visualBrowser": true, kino.visualBrowser.open({ url, title, doneWhen, collect, userAgent, timeoutMs }) opens a web window on your own hosts that the person sees and uses, on an Android phone and tablet and, experimental, on Android TV. Kino asks in its own sheet at every open, starts with a clean cookie jar, returns cookies, the page's HTML or its last address, and with collect.storeAs writes the cookies straight into one of your password settings (thenEvent tells your screen when). The "Vincular cuenta" recipe is on the page; enhancements may now carry visualBrowser. A browser window the person drives.

Kino 0.9.81: apiVersion 19, lyrics and go.installPlugin

Available from Kino 0.9.81

apiVersion 19 ships with Kino 0.9.81. Every older Kino refuses a manifest with "apiVersion": 19 with «Este plugin necesita una versión más nueva de Kino». contract.json says maxApiVersion 19.

Feature Since How to tell
The lyrics capability and the lyrics(query) export: a song's synchronized or plain lyrics for the music player's "Letra" overlay apiVersion 19 an older Kino refuses apiVersion 19
go.installPlugin: a button on your screen that opens Kino's own install sheet for another plugin's repository apiVersion 19, with screen below 19 the go is dropped, logged
recommends in the manifest and installed in screen and screenEvent: whether each recommended plugin is installed now Kino 0.9.81, at any apiVersion an older Kino ignores the field; installed is absent
  • Lyrics: a plugin answers { synced?, plain?, label?, instrumental?, matchDurationMs? } for the song that plays; the person picks the source when several plugins answer. Lyrics for the music player.
  • Installing another plugin from yours: go.installPlugin opens Kino's normal install sheet over your screen, and only the person's own Instalar installs it; with recommends, your screen knows which of those plugins are installed and Kino draws it again when that changes. go.installPlugin.
  • Screens: Scaffold.onBack and AppBar.mergeWithKinoBar are apiVersion 19 features (one compact bar), and a TextField hides the keyboard when it is submitted.

Kino 0.9.81: apiVersion 18, app themes

Available from Kino 0.9.81

apiVersion 18 ships with Kino 0.9.81. Every older Kino refuses a manifest with "apiVersion": 18 with «Este plugin necesita una versión más nueva de Kino». contract.json says maxApiVersion 18.

Feature Since How to tell
appThemes in the manifest: 1 to 8 whole-app themes as data (39 tokens, a background, tv/phone, adjustable, pluginColors) apiVersion 18 an older Kino refuses apiVersion 18; below 18 the field is ignored
A theme's price (kinos 1 to 1000, payTo the author's 64-hex coins account), bought once per account through Kino's own sheet apiVersion 18 the same
A theme's experience ("light" or "full"), asked with the person's consent when the theme is turned on apiVersion 18 the same
A theme's vector logo (wordmark, mark) in the menu, header and TV rail apiVersion 18 the same
go.useTheme and go.setExperience on the plugin's own screen; activeTheme in screen and screenEvent apiVersion 18, with screen the same
The themes marketplace category; "hosts": [] in a plugin that only ships appThemes apiVersion 18 for hosts: [] the same
  • App themes: a plugin may restyle the whole app (colours, background, corner radii, type scale, shadows, motion, player control sizes, its own logo). Kino keeps the legibility pairs (text 4.5:1, accent and focus 3:1, a dark background for now), lets the device win (reduced effects, rounded corners off) and never restyles its decision screens, the gate or the splash. The person picks one theme per profile in Ajustes ▸ Apariencia, adjusts what the author allows, and the choice syncs. App themes.
  • Selling a theme: with price, Kino asks the person to buy it before it turns on, shows the price and their balance, and pays the author; the plugin needs no coins capability and never sees the purchase. Priced themes.
  • Screens: a button on the plugin's own screen turns one of its themes on or off (go.useTheme, Kino's toast «Tema aplicado») or asks for the light or full experience (go.setExperience, Kino asks first). screen and screenEvent get activeTheme. go.useTheme.

Kino 0.9.81: apiVersion 17, your month in Kino, per-profile jobs and more screens

Available from Kino 0.9.81

apiVersion 17 ships with Kino 0.9.81. An older Kino refuses a manifest with "apiVersion": 17 with «Este plugin necesita una versión más nueva de Kino». contract.json says maxApiVersion 17.

Feature Since How to tell
kino.library.stats: one month's aggregates (month as yyyy-mm, the current one by default), nothing finer; top at most 20 titles; shares the 30 calls a minute of watched and saved; never 18+ apiVersion 17, with the library capability an older Kino refuses apiVersion 17
Jobs with perProfile apiVersion 17 the same
kino.tmdb inside a job apiVersion 17 the same
AI runs of 60 s and 20 requests apiVersion 17, with ai approved the same
The pages widget and the hero text style apiVersion 17 the same (an older Kino draws hero as p)
The share and enableJob answers apiVersion 17 the same
go.search with "scope": "all" and go.syncProvider apiVersion 17 the same
  • Your month in Kino: kino.library.stats reads the habits of one month of the person's (aggregates, not rows) with your library approval. Rooms, the library and player control.
  • Per-profile jobs: a job with perProfile runs once for each profile on the device. The consent is Kino's own row (each profile may leave itself out), the job hands its result over through kino.shared and skips the work when a fresh one already arrived. A manifest with perProfile and a lower apiVersion is refused. Background jobs, shared results and AI.
  • kino.tmdb in a job and more room for AI: a plugin with ai approved gets runs of 60 s and 20 requests (before, 20 s and 10). Background jobs, shared results and AI.
  • Screens: the pages widget (full-screen pages under Kino's progress bar, swiped on a phone and moved with Left and Right on a TV), the hero text style (a big number, one step above h1), the share answer (Kino draws a node as an image and opens the system share sheet, only after the person's tap), the enableJob answer (turns on Kino's own row of a job, only after a tap), go.search with "scope": "all" (Kino's normal search on every source) and go.syncProvider (opens the sync-provider settings). Screens and components.

Kino 0.9.78: apiVersion 16, Kino coins, and kino.sync.setActive

Available with Kino 0.9.78

apiVersion 16 and kino.sync.setActive ship with Kino 0.9.78. An older Kino refuses a manifest with "apiVersion": 16.

Feature Since How to tell
The coins capability and kino.coins.balance() / kino.coins.give({ to, postId }) apiVersion 16 typeof kino.coins === "object"
kino.sync.active() and kino.sync.setActive(on), with the syncProvider capability Kino 0.9.78, with any manifest apiVersion typeof kino.sync.setActive === "function"
  • Kino coins (coins): Kino coins are a free currency shared by all of Kino: the person earns 1 coin every 10 minutes watched, at most 20 a UTC day, and gives them one at a time. kino.coins.balance() answers { balance, earnedToday, capToday } and kino.coins.give({ to, postId }) gives ONE coin to the account to for the post postId. It is a declarative capability that never stands alone, is not offered through enhancements and is approved with a red consent line. If the person switches coins off in Kino's settings, the plugin must show nothing of them. Kino's own client talks to the coins service: your plugin never learns its address nor its session.
  • Switching provider from the plugin: kino.sync.active() tells whether this plugin is this device's sync provider and kino.sync.setActive(on) changes it. Turning on asks the person in Kino's own dialog (a decline answers false and changes nothing); turning off asks nothing and returns to Kino's local sync. It only runs from a tap of the person's, never from a job. It is not an apiVersion: feature-detect with typeof kino.sync.setActive === "function". Sync providers.

Kino 0.9.77: apiVersion 15, identity, notices and plugin stores

Available with Kino 0.9.77

Available with Kino 0.9.77. An older version refuses these plugins with «Este plugin necesita una versión más nueva de Kino»; none of these features is offered through enhancements.

Documented on 2026-10-29. contract.json says maxApiVersion 15; apiVersion 15 ships in Kino 0.9.77. The Node kit already knows all of it (Test it locally).

Feature Since How to tell
The identity capability and kino.identity.telegram apiVersion 15 typeof kino.identity === "object"
The notifications capability, kino.notifications.post and clear apiVersion 15 typeof kino.notifications === "object"
The pluginStore capability, the manifest's pluginStore block and the exports storeSync, storeList and storeSearch apiVersion 15 an older Kino refuses apiVersion 15
season and episode in a series' kino.library.watched() Kino 0.9.77, with the library capability the fields exist only on a watched series
  • Identity: your plugin's server knows who the person is without a sign-up, with a pseudonym per plugin and a signed token, bound to this device and to your code through a challenge. It answers only plugins signed with Kino's own author key. Identity.
  • Notices: your plugin leaves short notices in the Home bell, from a screen or its background job. Notices in the bell.
  • Plugin stores: a plugin that is a source of plugins for Kino's store (local, with a list it hands over in the background, or live, with its own API). Kino paints the store from a local index, mixes the stores, applies its blocklist and the 18+ code, and installs through its consent sheet. The store view has the tabs «De Kino» (From Kino), «De la comunidad» (Community) and «Instalados»; a reload icon ends with a toast. One plugin per id across stores; a store whose rows Kino lost is synced from scratch (no since, no state: answer the full list); the blocklist refreshes with every sync. With Kino Plugins, the store that ships in the app, the app no longer searches GitHub by itself. Plugin stores and two example stores; node sdk/init.mjs my-store --store local|live.
  • The library: a watched series carries season and episode. Rooms, the library and player control.

Kino 0.9.74: apiVersion 14, plugin screens

Available with Kino 0.9.74

Available from Kino 0.9.74. An older Kino refuses these plugins with «Este plugin necesita una versión más nueva de Kino»; to keep reaching people on an older version use enhancements (see Screens without raising your apiVersion).

Documented on 2026-10-28. apiVersion 12, 13 and 14 arrive together with Kino 0.9.74: contract.json says maxApiVersion 14 and apiVersionFromApp gives 0.9.74 for all three. The Node kit already knows all of it (Test it locally).

Feature Since How to tell
The screen capability, the screen and screenEvent exports and the manifest's screen block apiVersion 14 kino.screen is undefined on an older Kino
playerPanelTab (a tab in the player panel of any title, live channels too with "kinds": ["live"]), the panel in screen mode and the pinned panel apiVersion 14 an older Kino refuses apiVersion 14
library, playerControl and room (kino.library, kino.room) apiVersion 14 the same
schedule (the jobs block and the job export), shared (kino.shared) and ai (kino.ai) apiVersion 14 the same
unlockWith on a toggle or a select apiVersion 14 below it the key is ignored
maxBytes and stopAt in kino.fetch, r.truncated apiVersion 14 below it the options are ignored
The manifest's enhancements block Kino 0.9.74, at any apiVersion an older Kino ignores it
kino.qr.scan from a screenEvent that follows the person's tap apiVersion 14 —
Exporting and importing a plugin as a .kinoplugin file Kino 0.9.74, any apiVersion nothing to check
  • Screens: your plugin draws a full screen inside Kino from a JSON tree of Flutter-style components (Scaffold, AppBar, TabBar, ListTile, Card, forms, the settings node, tables, accordions, anchored pop-ups, toasts, banners, Kino's own poster cards and rows), with per-size values, on the phone and the TV from the same tree. Kino keeps the state, validates the tree and drops what is wrong without crashing. Screens, and the catalogue: layout, content and actions, forms, overlays and navigation, state, style and recipes.
  • The player panel: the panel may use the screen kit, a tab may go in the panel of another plugin's title or of a live channel, and the panel can be pinned beside the video. The player panel.
  • Rooms, the library and player control: kino.room opens rooms over the Internet hosted on the person's device, kino.library reads what they watched and saved, playerControl lets the panel pause and move the video. Rooms, the library and player control.
  • Background jobs, shared results and AI: job(ctx) runs every so often, kino.shared syncs a few results between the person's devices, kino.ai.ask asks Kino's text AI one short question. Background jobs, shared results and AI.
  • Without raising your apiVersion: enhancements offers all this to people on Kino 0.9.74 and leaves your plugin as it was for everyone else. Screens without raising your apiVersion.
  • A setting the 18+ code guards: "unlockWith": "adultCode". The settings form.
  • Reading only the head of a page: kino.fetch with maxBytes and stopAt. The kino API.
  • A plugin as a file: Kino exports an installed plugin as .kinoplugin and imports it as a local plugin. Exporting and importing a plugin file.
  • Bigger plugins: src/ bundled with esbuild, with check:built. Structure a bigger plugin.
  • Examples: kino-plugin-ui-gallery, kino-plugin-news (Solo noticias) and kino-plugin-watch-party (Party Chat).

Kino 0.9.74: apiVersion 13, sockets, plugin-served bytes and images, a catalog, QR codes

(Released 2026-10-29.) apiVersion 13 = Kino 0.9.74, together with apiVersion 12 (below). The contract (contract.json) says maxApiVersion 13 and apiVersionFromApp gives 0.9.74 for both. Every Kino before 0.9.74 refuses a manifest with "apiVersion": 13 ("Este plugin necesita una versión más nueva de Kino"), so declare 13 only if you use one of its features. The Node kit already knows all of it.

Feature From How to tell
The socket capability and kino.ws (hex/base64 frames) apiVersion 13 nothing to check: an older Kino refuses apiVersion 13
The byteSource capability, { source: "plugin", handle, size, mime } streams and the read export apiVersion 13 the same
The storageLarge capability (16 MB kino.storage, device-only) apiVersion 13 the same
The catalog capability and kino.catalog apiVersion 13 the same
The qrScan capability, kino.qr.scan, and the settings form's qr type apiVersion 13 the same
The imageSource capability, { source: "plugin", handle } images and the image export apiVersion 13 the same
kino.crypto.aesIge, aesIgeVerify, modPow, gunzip, convert Kino 0.9.74 (kino.apiVersion 13), every manifest apiVersion typeof kino.crypto.convert === "function"
"sync": false on a password setting (stays on this device) apiVersion 13 nothing to check: an older Kino ignores the key and syncs the password
Async kino.* answers freed once your code has them; a GC after a call over half the 64 MB; faster atob/btoa Kino 0.9.74, every apiVersion nothing to check
  • Sockets (socket): kino.ws.open("wss://…") to a host you declare, port 443 only, at most 4 sockets, 8 MiB queued per socket, 786,000 bytes per frame; frames as Uint8Array or, much faster, as hex/base64 strings. Sockets and plugin-served bytes.
  • Plugin-served bytes (byteSource): resolve() answers a stream with no URL and Kino asks your read for 1 MiB at a time, plays it in its player and casts it to Chromecast and DLNA from the phone. A complete example over a WebSocket, with its test: Sockets and plugin-served bytes.
  • A catalog of your own (catalog): kino.catalog keeps up to 100,000 items in one SQLite file per plugin and searches them (every word, no case or accents, no SQL on your side); device-only, never synced, not in backups. storageLarge makes kino.storage 16 MB for a few big values, device-only too. Catalog and large storage.
  • QR codes: the settings form's qr type draws a QR from your settingsStatus() and refreshes it every refreshMs; kino.qr.scan() (qrScan) opens the phone's camera scanner from a settings action or a panel action. A two-device login recipe: QR codes.
  • Images from the plugin (imageSource): a poster, backdrop, still or section hero image may be { source: "plugin", handle }; Kino asks your image export for the bytes (at most 256 KB, JPEG, PNG or WebP) when the card comes on screen, one at a time, never while one of your byte streams plays. Images from the plugin.
  • Byte operations in kino.crypto: AES-256-IGE, a decryption checked by its SHA-256 MAC in one call, big-number modPow, gunzip and a native convert between utf8, hex and base64. They are gated on the Kino version, not on your manifest (Kino 0.9.74 has all five, an older Kino none): feature-detect each one. Byte operations.
  • The kit: run.mjs . resolve accepts byte streams, run.mjs --size <bytes> . read … and run.mjs --out <file> . image … call your exports as Kino does (askRead, askImage from tests), and init.mjs --with byteSource,images,catalog,socket scaffolds an apiVersion 13 plugin. Test it locally.
  • A password that stays on one device: a password setting may say "sync": false (a two-step verification password sent once and cleared): never sent to a paired device, in no backup or kit. The settings form.
  • Engine memory (Kino 0.9.74, every apiVersion): the answer of an awaited kino.* call no longer stays in your 64 MB until the sandbox closes, and Kino collects garbage after a call that leaves the engine over half its limit. How your code lives.

Added to apiVersion 13 on 2026-10-25: sync providers and the settings form

Still apiVersion 13 and Kino 0.9.74, added for the account-based sync provider Sync-Gram Cuenta. An older Kino refuses apiVersion 13, so there is nothing to check.

Feature From
syncProvider (or subtitles, tracking, segments) next to socket, storageLarge, catalog and qrScan needs no resolve, search or home apiVersion 13
An action's setSettings may fill one of your own password settings apiVersion 13
sync.provision may name a "sync": false password, a one-shot secret for the new device apiVersion 13
sync.generateKey: true: Kino makes the keySecret value itself apiVersion 13
A settingsStatus answer may carry hide: [setting keys]; a qr setting with no text draws nothing apiVersion 13
A text setting may say "sync": false apiVersion 13
  • Standalone with runtime room: a sync provider that talks over a WebSocket declares ["syncProvider", "socket"] (and storageLarge, catalog or qrScan if it needs them) and still exports no resolve, search or home. The manifest.
  • setSettings fills a password: stored sealed like a typed one, never logged, scrubbed from the answer's message and link; the kit prints it masked. Filling a password.
  • A one-shot secret in provision: a "sync": false password (a two-step password the TV should not type) goes with "Enviar configuración" only while it holds a value, the sending screen names it in one line, and the receiving device keeps it sealed and device-only; never as keySecret. Sync providers.
  • sync.generateKey: for a provider whose service has no shared secret (the person's own account), Kino writes 32 random bytes as hex into the empty keySecret setting when the provider is switched on and when "Enviar configuración" is pressed; no "Create key" step. A key Kino makes.
  • settingsStatus hide: at most 32 of your own setting keys the form does not draw while that answer is current (values kept); a qr with no text draws nothing at all. Hiding items.
  • A device-only text: "sync": false on a text (a phone number shown as typed): never synced, backed up or in sync.provision. A value that stays on this device.
  • What the person sees (no contract change): the provisioning buttons are now "Enviar configuración" and "Recibir configuración" ("Send settings" / "Receive settings"), the settings button on a provider's card is "Configurar" ("Set up") on phone and TV, the cards follow the provider's state (on a device that lacks the settings, "Recibir configuración" leads), the red consent line stays on the install sheet and the switch-on confirmation, a refused camera says how to turn it on, and uninstalling the active provider warns that sync goes off.
  • A third example provider: Sync-Gram Cuenta syncs through the person's own Telegram account (MTProto over kino.ws), signed, not in any catalog: installed by pasting kinotvapp/kino-plugin-sync-gram-account. The three example providers.

Kino 0.9.74: apiVersion 12, sync providers, link and help, setSettings and "Is this you?"

(Released 2026-10-29.) apiVersion 12 = Kino 0.9.74. The contract (contract.json) now says maxApiVersion 13 and kino.apiVersion reports 13, because apiVersion 13 ships in the same release. Kino 0.9.73 and older refuse a manifest with "apiVersion": 12 ("Este plugin necesita una versión más nueva de Kino"), so declare 12 only if you use one of its features.

Feature From How to tell
The syncProvider capability (syncPull, syncPush, optional syncStatus) and the manifest's sync block Kino 0.9.74, apiVersion 12 nothing to check: an older Kino refuses apiVersion 12
The link and help setting types Kino 0.9.74, apiVersion 12 nothing to check: an older Kino refuses apiVersion 12
devices on settings and linkOnly on an action Kino 0.9.74, apiVersion 12 nothing to check: an older Kino refuses apiVersion 12
kino.sync.remoteChanged() for a realtime provider Kino 0.9.74 typeof kino.sync === "object"
An action's setSettings and link answers Kino 0.9.74, every apiVersion nothing to check: an older Kino ignores both, so also say in message what to do
kino.fetch caps raised inside syncPull/syncPush Kino 0.9.74 only inside those two calls
  • Sync providers (apiVersion 12): a plugin can be the transport of the person's cross-device sync. Kino keeps the logic, encrypts the snapshot and hands your syncPush an opaque base64 blob (at most sync.maxBlobBytes, 4 MiB) to store and your syncPull returns it byte for byte, with a version of yours; kino.error("conflict", …) makes Kino pull, merge and push again. The manifest's sync block sets the cadence (poll or realtime), the blob size, the required keySecret (Kino derives the sync key from one of your password settings on each device, so no key travels and the plugin and its service can read the data) and the required provision (the settings "Enviar configuración" hands to a second device, over the local network or a Cloudflare quick tunnel). The capability may be a plugin's only one. Sync providers.
  • Consent: one red line, "Sincronizará tus datos a través de su servicio: el plugin y su servicio podrán leerlos". An update that adds the capability always waits for the person's approval.
  • Configuration aids (apiVersion 12): a link setting (a button that opens an https address through the system only on the person's tap; on a TV, the address and a QR) and a help setting (a button that opens your plain-text instructions in a modal), at most 4 of each. Configuration aids.
  • devices (apiVersion 12): any settings item can be drawn on the phone only (["phone"]) or the TV only (["tv"]); its value is still stored, synced and provisioned. Settings for one kind of device.
  • linkOnly (apiVersion 12): an action that is never drawn and runs only as a link's confirm. Actions only a link runs.
  • What Kino adds to a provider: each provider's page starts with the "Sincronización ▸ Proveedor" button; each provider is its own card in that list, with "Sincronizar cada" (1 to 60 minutes, per device; pullEveryMs is only the default). Sync providers.
  • setSettings (Kino 0.9.74, additive): an action may fill up to 8 of your own text or select settings, saved as if the person typed them; never a url, and a password only from apiVersion 13. Filling your own settings.
  • "Is this you?" (action.link, Kino 0.9.74, additive): an action answers link: { candidate, confirm } and Kino asks the person with its own words before running the confirm action. Linking.
  • Plugin request logs keep only the host: Kino's log line for each kino.fetch of a plugin now carries the method, host, status, size and time, never the path or the query (a bot token in a path, as in Telegram's Bot API, never reaches a log).
  • Two example providers, public repositories: Sync-Gram (kinotvapp/kino-plugin-sync-gram, a Telegram bot of the person's own, recommended) and Sync Servidor (kinotvapp/kino-plugin-sync-server, a server the person runs, not listed). The two example providers.

Kino 0.9.71: apiVersion 11, kino.nuvio

  • A plugin can use the scrapers of a Nuvio repository. You declare the nuvio capability and nuvioRepos (1 to 4 repositories) and, inside your functions, call kino.nuvio.available, use, scrapers and streams: Kino installs the scrapers as the import does, with no screens, asks them for a title, and you sort, merge and label the copies. The scrapers belong to your plugin and are removed with it; torrent-only ones are never installed. Experiment: detect it with typeof kino.nuvio === "object". Plugins that use Nuvio scrapers.

Home by categories, open genre on rows

  • genre on a Home row accepts any category. It used to be ten closed ids. Now a known id or alias (Spanish or English: "Action", "Acción", "Thriller", "Sci-Fi & Fantasy"...) maps to the base id, and anything else is kept as a slug (lowercase ASCII [a-z0-9-], at most 40 characters) appended at the end, after the known ones. Live categories and playlists keep the ten ids. Earlier Kino versions ignore a value outside those ten. Home categories.
  • Home by categories (optional for the person): one flat list of category rows (genre rows with every type mixed, a full row per thematic type such as Anime or Kids, no tabs), one card per title, built only from what your Home rows already left cached. Declare genre on each row and genres on each item, preferably with the vocabulary ids, and send ids/TMDB and year so a title is one card across sources. What the Home does with your categories.

Kino 0.9.66: apiVersion 11, external resolver apps, media and portable

apiVersion 11 = Kino 0.9.66. The contract (contract.json) now says maxApiVersion 11 and kino.apiVersion reports 11. Kino 0.9.65 and older refuse a manifest with "apiVersion": 11 ("Este plugin necesita una versión más nueva de Kino"), so declare 11 only if you use externalResolve.

  • externalResolve (apiVersion 11): a declarative capability (nothing to export). A resolve() answer, or one entry of a Stream's alternatives, may be { external: { protocol, ref, resolver? } } instead of a playable url: Kino hands ref to an independently-installed app that declares it resolves protocol, after the person allows that app for your plugin, and plays the answer it gets back (validated like yours, with hosts judged as for any resolver's answer). Your plugin never learns which app handled it. External resolver apps, the contract.
  • externalResolver (manifest field, apiVersion 11): { package, apk?: { url, sha256, label? }, fdroid?: true, downloader?: { code } } names the one app you want (no other is ever asked) and where Kino may offer to download it, from a GitHub release, checked against the sha256; fdroid: true and a Downloader code (shown, never installed by Kino) are two more optional ways to get it. The manifest.
  • media (a stream's optional, advisory description of the file: container, video, audio and subtitle tracks, whether it was converted) and portable (a universal HLS copy of the same video, made on demand, that Kino may cast to a TV): read from any plugin's or resolver's answer, at any apiVersion; older Kino ignores both. The Stream rules.
  • What the person sees: a consent question the first time an app is needed, "Abriendo con ..." with the app's live progress and Cancelar, and, when it fails, the app's own short sentence next to the code ("No se pudo resolver este contenido (timeout): ..."). What people see.
  • Casting a title from a resolver goes through Kino's cast proxy; it is covered by tests with a fake resolver and was tried on a real Chromecast (a direct file, a converted HLS with renditions, a portable copy); DLNA was tried on an LG webOS TV: the HLS plays (the continuous-TS route does not). Casting a resolver's title.

Kino 0.9.65: apiVersion 10, the playlists capability

apiVersion 10 = Kino 0.9.65. The contract (contract.json) now says maxApiVersion 10 and kino.apiVersion reports 10. Kino 0.9.64 and older refuse a manifest with "apiVersion": 10 ("Este plugin necesita una versión más nueva de Kino"), so declare 10 only if you use the playlists capability.

  • playlists (apiVersion 10): the SDK now accepts a plugin declaring this capability -- the contract for the day Kino's UI connects to it, so a plugin can expose, inside Kino's "Mis listas", the playlists the person already has in your service's account, next to their own. For now no installed or announced plugin uses it, and that UI connection doesn't exist yet. Six exports, every one independently optional -- unlike channels, which requires two --, not even playlists() itself: playlists(), playlistItems({ playlistId, cursor }), playlistCreate({ title }), playlistAddItem({ playlistId, ref }), playlistRemoveItem({ playlistId, ref }) and playlistReorder({ playlistId, refs }). Nothing to do with KinoPlaylist (the M3U/IPTV list under En vivo) or the kind: "playlist" signed in sign(). Playlists.

Kino 0.9.55: apiVersion 9, the player panel, fetchHosts on hand-written plugins, English texts, kino.meta by title

(Released 2026-10-08.) apiVersion 9 = Kino 0.9.55. The contract (contract.json) now says maxApiVersion 9 and kino.apiVersion reports 9. A manifest with "apiVersion": 9 is refused by Kino 0.9.54 and older ("Este plugin necesita una versión más nueva de Kino"), and every feature here needs apiVersion 9: below it Kino ignores them, as an older version does.

Feature From How to tell
The player panel: panel, panelAction, playerEvent, the manifest's panel and the player properties Kino 0.9.55, apiVersion 9 nothing to check: an older Kino refuses apiVersion 9; do not depend on it to play
settingsLayout: rows, columns and cards in your settings Kino 0.9.55, apiVersion 9 nothing to check: below 9, or on an older Kino, the usual list shows
"fetchHosts": "any" on a hand-written plugin Kino 0.9.55, apiVersion 9 kino.fetchAnyHost === true (approved by the person)
English settings and section texts (labelEn, hintEn, confirmEn) Kino 0.9.55, apiVersion 9 nothing to check: below 9, or on an older Kino, the usual ones show
kino.meta({ type, title, year? }) without ids Kino 0.9.55, apiVersion 9 kino.meta.byTitle === true
kino.device: "tv" or "phone", the UI Kino shows on this device Kino 0.9.55, every apiVersion kino.device === "tv" (undefined before)
kino.seed(session): share one anonymous guest session of your source (needs the person's telemetry consent) Kino 0.9.55, every apiVersion typeof kino.seed === "function"
  • The player panel (apiVersion 9). A button next to the subtitles one, only while a title of yours plays, opens a panel you build with panel(context): text, images, buttons, switches, lists and inputs, in rows, columns and cards, with tabs, and with values kept per video or for your whole plugin and synced. panelAction(event, context) answers each button or input (with panel, patch, values, save, focus, message and player), and the manifest carries "panel": { "label", "icon" | "iconFile" } (a 96×96 PNG). The player panel.
  • Player properties (apiVersion 9): player in a panelAction or playerEvent answer drives the player: seekToMs, seekStepMs (5 to 120 s), speed, resize, skip, markers (up to 30 dots on the bar) and autoNext (an end-of-episode countdown, or { enabled: false }). What the person does by hand wins. Driving the player.
  • playerEvent(event, context) (apiVersion 9): tells you about started, paused, resumed, ended, failed and copyChanged while a title of yours plays; fire-and-forget, 5 s, one at a time. playerEvent.
  • settingsLayout (apiVersion 9): arranges the settings you already declared in rows, columns and cards, without removing any. settingsLayout.
  • "fetchHosts": "any" for your plugin (apiVersion 9): until now Kino honoured it only on the Nuvio scrapers it converts. From Kino 0.9.55 a hand-written plugin with "apiVersion": 9 and "fetchHosts": "any" may reach any public host you did not declare with kino.fetch (redirects included), only over https on port 443 and at a dotted name or a public IPv4 address, for sites and extractors that rotate domains. Those requests spend a budget per plugin (60 a minute to one site, 600 every 10 minutes; over it, rate_limited); your declared hosts keep their own rules and spend none of it, so declare your primary sites. The person approves it in red ("Puede conectarse a cualquier servidor público de internet (solo https, nunca tu red local)") and an update that adds it waits for that approval again, the first start after a Kino update included; the home network stays refused and a sealed secret only goes to your hosts. On hidden pages, the start address and every top-level navigation follow the same rule. A host_not_allowed from kino.fetch now carries e.host. kino.fetchAnyHost is true when it is active (false otherwise; undefined on an older Kino). Below apiVersion 9 nothing changes. Reaching any server.
  • Your settings form and your section, in English too (apiVersion 9). Every setting may carry labelEn and hintEn (an action with confirm, also confirmEn), every select option and list field its labelEn, and the manifest's section its labelEn, with the same limits as the usual text. With the app in English Kino shows them; the usual text stays the Spanish one and the fallback wherever one is missing. Below apiVersion 9 they are unknown keys, ignored without being checked. English texts.
  • kino.meta by title (apiVersion 9). When your source only gives you the name and the year, kino.meta({ type, title, year }) looks the title up on TMDB (es-MX, matching the original title too, the exact year or one off) and answers the same as with an id, ids included. When two hits tie or none matches it answers null: it never guesses. Check kino.meta.byTitle === true first; below apiVersion 9, or on an older Kino, the title never arrives and the query answers invalid_request. By title, without ids.

Kino 0.9.54: apiVersion 8, music and podcasts, catalog-only plugins

(Released 2026-10-06.) apiVersion 8 = Kino 0.9.54. The contract (contract.json) now says maxApiVersion 8 and kino.apiVersion reports 8. A manifest with "apiVersion": 8 is refused by Kino 0.9.53 and older ("Este plugin necesita una versión más nueva de Kino"), so declare 8 only if you return music or podcast items or export details. Everything else on this list is additive (valid at any apiVersion, ignored by older Kino), and nothing on it makes you change your plugin. How to use each one and still run on older Kino:

Feature From How to tell
music / podcast items, details export Kino 0.9.54, apiVersion 8 declare "apiVersion": 8 (older Kino refuses the plugin)
"catalogOnly": true Kino 0.9.54, any apiVersion older Kino ignores it: keep resolve and search or home
kino.browser.capture's captureAll, alsoMatch, waitForCookie, returnCookiesOnTimeout Kino 0.9.54, apiVersion 6 with "browser": true kino.browser.captureAll === true
episodes().series.rating/runtimeMinutes, ids.mal/anilist/kitsu Kino 0.9.54, any apiVersion nothing to check: older Kino ignores them
kino.lang in the app's language Kino 0.9.54 read kino.lang; it was always "es-CO" before
  • Music and podcasts (apiVersion 8): an item may be kind: "music" (an album, a playlist or a single track) or kind: "podcast" (a show or an audiobook), with an optional artist. With episodes declared, Kino asks it for the tracks or episodes; without it, the item's ref goes straight to resolve. People get square covers in rows of their own, album and podcast pages with "Reproducir" and "Aleatorio", an audio player, "Seguir escuchando" for podcasts on Home, audio downloads (with download) and audio cast to Chromecast and DLNA. search may get type: "music" or "podcast", and migrate may answer one. Music and podcasts.
  • details(ref) (apiVersion 8, optional, no capability): your own synopsis, art, genres, year, score and runtime for a movie's page, asked alongside TMDB under its own 20 s and allowed to use kino.browser.page. From apiVersion 8 details is a reserved export name: rename a helper of yours that has it. episodes().series takes rating and runtimeMinutes too, and ids may carry an anime's mal, anilist and kitsu, which AniList and meta plugins are then asked by. The title page now follows one fixed order per field whatever answers first, with TMDB first for the synopsis, year, genres, score and runtime. A title's own details.
  • "catalogOnly": true in kino-plugin.json: your plugin lists and describes titles but plays none (a TMDB catalog, a list of new releases, ratings). Kino 0.9.54 sends its titles to "Buscar dónde verlo" (the person's other sources) instead of opening the player, never uses it as a source of a title (the search, "Ver en otros plugins", "Buscar por fuente", the player's "Servidor"), never calls its resolve, does not count it as a source in "Elige tus fuentes", and the install sheet says "Solo catálogo: no reproduce videos" ("Catalog only: doesn't play videos"). With the field, resolve is no longer required and one of home, browse, search or meta is enough; download, drm, channels, streamHosts and "browser": true are refused ("pages" is fine).
  • It is additive: valid at every apiVersion, and an older Kino ignores the field as it ignores any key it does not know. To keep your plugin installing and updating on Kino 0.9.53 and older, keep declaring and exporting resolve (failing with kino.error("not_found", …, { userMessage })) and search or home: those versions require them. node sdk/validate.mjs tells you whether your manifest also works there, and node sdk/run.mjs . resolve <ref> reminds you that Kino 0.9.54 no longer calls it. Catalog-only plugins.
  • kino.browser.capture catches every match: captureAll collects every matching request (at most 20) until the page settles, alsoMatch adds up to 10 more patterns, waitForCookie waits for a cookie such as cf_clearance (with no match, a cookie-only page), and returnCookiesOnTimeout answers what the page had instead of throwing timeout. The answer then adds requests, cookies, userAgent and timedOut. No new apiVersion: check kino.browser.captureAll === true first; older Kino ignored these names, 0.9.54 checks their types (invalid_request). Hidden browser.
  • kino.lang follows the app's language. Kino 0.9.54 speaks Spanish or English (Ajustes ▸ App ▸ Idioma), and kino.lang is "es-CO" or "en-US" accordingly (always "es-CO" before). A language switch closes your sandbox and the next call opens one with the new value; kino.meta's cache is cleared and Home's plugin rows are asked again. Word your row titles and userMessage in that language. The kino API.
  • Kino's error messages to your code are English (e.message of a kino.fetch failure, kino.storage, kino.html, the signing rules) and may change: match on e.code, never on the text. The manifest refusals the person reads at install stay as they were. Errors your code can catch.
  • telemetry: true has a new consent line, "Comparte con Kino registros de errores y datos técnicos de algunas reproducciones para corregir fallas", and also sends a small sample of playbacks that went well (one in twenty, at most 6 until Kino restarts), only once the person agreed to that wording. Your plugin's tab in Ajustes has an "Enviar registros de errores y de reproducción" switch, on by default. Playback records add the codec, the delivery, each stall's likely cause and the network type. Logs and telemetry.
  • Copies: same video, same language. Every alternatives entry must be the same video in the same language (Kino switches between them by itself). After repeated stalls Kino may move once, by itself, to a clearly lighter copy when the labels name the resolution ("720p", "Full HD"). The Stream rules.
  • Downloads that cannot be saved now end as "Este contenido no se puede descargar" (was "Este video no se puede descargar"). Downloads.
  • "De la comunidad" reads 100 plugins a page (was the 30 most-starred), sorted by "Populares" or "Recientes", with "Cargar más" and "Buscar en GitHub" for the typed text: a clear repository name and description help people find you. Publishing.
  • CloudStream plugins: people can add a CloudStream repository and Kino turns each plugin they pick into a Kino plugin that runs through a separate complement app; Music/Audio become music and Podcast/AudioBook podcast. Nothing for you to write: it is what a CloudStream repository maintainer may rely on. Generated plugins get a kino.cloudstream object yours never has. A repository can also be added by its CloudStream short code (cutt.ly, or py.md with a leading !), and a plugin's own settings screen opens on phones. CloudStream plugins.
  • Fixed: kino.tmdb and kino.meta after an abandoned call. When Kino abandoned a call of yours (a screen closed, a time limit) but still used its late answer, every kino.tmdb or kino.meta that call made afterwards failed with not_allowed, so a TMDB catalog could show one Home row instead of all of them until a restart. From 0.9.54 they keep answering until that call's evaluation ends. The kino API.
  • no_tmdb_key's sentence for the person is now "Agrega tu llave de TMDB en Ajustes ▸ Tu llave de TMDB" ("Add your TMDB key in Settings ▸ Your TMDB key"); 0.9.53's also pointed to a Stremio TMDB addon. Today's Kino says "Agrega tu llave de TMDB en Ajustes de todos los perfiles ▸ Llaves" ("Add your TMDB key in Settings for all profiles ▸ Keys"), where the key now lives. Nothing to change: match on e.code, never on the text. The kino API.

Kino 0.9.53: kino.meta and kino.tmdb

No new apiVersion: it is still 7, and nothing on this list makes you change your plugin. Both new calls exist only from Kino 0.9.53, so feature-detect them (typeof kino.meta === "function", typeof kino.tmdb === "function"); node sdk/validate.mjs warns when your code calls one without that check.

  • kino.meta(query): ask Kino what it knows about a title ({ type, ids: { imdb, tmdb, tvdb, kitsu, mal, anilist }, lang }) and get synopsis, year, poster, backdrop, logo, genres, runtime, episodes with their ids, the cross-reference of every id, ratings and cast, or null. Kino answers from its own TMDB lookup, AniList for anime, and the person's other meta plugins, merged the way its info page merges them; your plugin never touches a TMDB key, and it is never asked on its own behalf. 30 calls a minute, 8 s at most, cached 30 minutes. The kino API.
  • kino.tmdb(path, params): TMDB's read-only v3 API with no key in your plugin. Kino's own key goes first, behind Kino's TMDB cache (on disk, shared with its own screens, a copy up to 7 days old when TMDB is down) and limits of its own (20 calls per 10 s per plugin, 60 per 10 s for all plugins), so plugins cannot spend Kino's quota. Only when Kino's key fails (TMDB answers 401/403/429 for it, or one of those limits is spent) does the same request go again with the person's key: the one they type in Ajustes ("Tu llave de TMDB", today under Ajustes de todos los perfiles ▸ Llaves; optional, synced between their devices), else the one they configured in an installed Stremio addon, once they agree. A key your plugin keeps in its own settings is never used. Kino adds the key; your code never sees any, and TMDB needs no entry in your hosts. no_tmdb_key (with Kino's sentence for the person in e.userMessage: "Agrega tu llave de TMDB en Ajustes, o instala un addon de TMDB de Stremio configurado con tu llave.") is left for a Kino build without a key of its own and a person without one. Allowlisted read paths only, 40 calls per 10 s per plugin whichever key, cached 10 minutes. A TMDB-based catalog no longer needs its own key setting (keep it only as a fallback for older Kino). The kino API, a complete example.
  • The Node kit runs both: KINO_META_FIXTURE, KINO_TMDB_KEY (or "tmdbKey" in sdk/config.json) and KINO_TMDB_FIXTURE. Test it locally.

Kino 0.9.51: apiVersion 7

apiVersion 7 = Kino 0.9.51. The contract (contract.json) now says maxApiVersion 7 and kino.apiVersion reports 7. A manifest with "apiVersion": 7 is refused by Kino 0.9.50 and older ("Este plugin necesita una versión más nueva de Kino"), so declare 7 only if you use tracking or segments. Nothing else on this list makes you change your plugin.

  • tracking (apiVersion 7): your plugin exports track(event) and Kino tells it which movie or episode plays on that device, from any source: start, progress, stop and watched, with the episode's own ids and the show's apart. Approved in red ("Le contará a … qué ves y cuándo lo terminas"), with a "Enviar lo que veo" switch in your Ajustes tab; events wait in a queue that survives offline and a closed app (ordered retries, 200 per plugin, 7 days). Return { skipped: true } for an event your service has no use for. Telling a tracker what the person watches.
  • segments (apiVersion 7): your plugin exports segments(query) and tells Kino where any movie's or episode's intro and credits are; the "Saltar intro" and "Saltar outro" buttons and auto-skip use them on phone and TV. No red approval. Where the intro and credits are.
  • Subtitles for the exact file: subtitles() gets file: { hash?, size?, name? }, what Kino knows of the playing file (its OpenSubtitles hash, its size, its name, or a release-style one built from the title), to rank the exact release first. A Stremio addon gets it as the videoHash, videoSize and filename extras. No new apiVersion. Subtitles for any title, Stremio addons.
  • meta with a logo, ratings and cast: a meta answer may carry logo (shown instead of the name on the info page), ratings (up to 6, from IMDb, Rotten Tomatoes, Letterboxd…) and cast (up to 20); an AIOMetadata-style Stremio addon gives them through its logo, imdbRating and app_extras.cast. No new apiVersion: older versions ignore them. Describing other titles.
  • stremio:///detail/… links open the title in Kino (Seenr's "Open in Stremio" and the like) instead of being ignored. Stremio addons.
  • "Tu servidor" 1.5.0, the reference plugin, now shows everything a server of one's own can use up to apiVersion 7: tracking, segments, subtitles with file, meta with logo, ratings and cast, and the apiVersion 6 features (section, categories, request signing, copies, the full settings form, a resolve: true playlist, liveSearch and channel paging). Example plugins.

  • Nuvio compatibility v2: Kino converts many more Nuvio scrapers. Multi-file scrapers (siblings read from the same repository, at most 16 files and 1 MiB), a Node subset (path, url, util, events, querystring, timers, buffer and http/https/undici over kino.fetch; setInterval, queueMicrotask), each scraper's onSettings as a settings form synced across devices, and every playable copy offered as a labelled alternative in the Servidor menu (embed pages last). A Kodi-style url|User-Agent=… address becomes headers. Peer-to-peer and debrid scrapers are refused ("No compatible"). None of it is for your own plugin: it is what a Nuvio scraper may rely on. Nuvio scrapers.

  • Settings form: a section's hint may be up to 300 characters and wraps (sectionHintMaxChars in contract.json). Builds before 0.9.51 refuse one over 80, so keep it short if your plugin must install on them. The settings form.
  • A % in an error's text no longer crashes the app. Up to 0.9.50, an error from your plugin whose text carried a % (a percent-encoded URL such as ?q=Inception%20s in a "fetch failed") could kill Kino outright. Now an error's text can be anything; if your plugin must run on 0.9.50 and older, keep encoded addresses out of its error messages. Errors your code can catch.
  • Recomendados gains Stremio utility addons (subtitles such as OpenSubtitles v3 and Subtis, catalogs such as Cinemeta, TMDB and IMDb) and free, legal channels (Pluto TV, Radios). The list is no longer published on npm: Kino reads it from this repository on GitHub, then from archive.org, then from jsDelivr's copy of the same GitHub file. An addon that plays video is still never recommended. Stremio addons.
  • A Stremio addon whose description denies torrents is no longer hidden ("no incluye streams, torrents ni contenido P2P"); the id and name stay strict. What Kino refuses.
  • Your plugin's card no longer wears a "Kino" badge (it read as made by Kino); Stremio addons and Nuvio scrapers keep theirs.

Kino 0.9.50: apiVersion 6

apiVersion 6 = Kino 0.9.50. The contract (contract.json) now says maxApiVersion 6 and kino.apiVersion reports 6. A manifest with "apiVersion": 6 is refused by Kino 0.9.49 and older ("Este plugin necesita una versión más nueva de Kino"), so declare 6 only if you use something on this list. Everything a plugin can now change in how Kino shows it is gathered on Customize your plugin.

  • Larger and typed sealed secrets: up to 8,192 bytes, and typed cipher keys (use: "cipher-key") that also work for des-ede3. The manifest.
  • migrate: move to your plugin what the person had saved and Kino can no longer open. Moving saved titles.
  • Request-signed streams: signing: "request", signContext, the sign export, resolve(ref, { retry }) and alternateHosts. Signing every request.
  • The settings form: the section, status and action types (up to 16, on top of the 12 valued ones), settingsStatus, action with clearSettings, validateSettings, the plugin's own tab in Ajustes and syncing across devices. The settings form.
  • debug and telemetry (true or "verbose"), kino.log.report, the Registro page, the KinoPlugin/<id> and KinoPlay logcat tags, and playback metrics. Logs and telemetry.
  • Modo debug in every plugin: every installed plugin (yours, a generated Stremio addon, a Nuvio scraper) has a "Modo debug" switch in its Ajustes tab, with no work on your side: on, its failures show on screen and its Registro can be copied or shared, so a person can send you a screenshot or their Registro. "debug": true now only makes the switch on by default; without it the switch starts off. The person's choice survives updates and syncs to their other devices. Modo debug.
  • Early rejections are caught: a throw in an async function before its first await is caught by the caller's try/catch (or .catch(), Promise.all), as in Node; only a rejection nobody ever handles still fails the call. Keep awaiting first if your plugin must run on 0.9.49 and older. The rejection trap.
  • section, categories and theme: a section of your own, a group in Categorías and your colors. Section, categories and colors.
  • scopedSearch: answer the search inside a "Ver más" page yourself. The contract.
  • kino.error(code, message, { userMessage }): your own sentence for the person, with safety rules and attributed to your plugin. The contract.
  • adult: true entries behind the person's 18+ code (they used to be dropped). 18+ content.
  • Channels in your Home rows (kind: "live" in home; they used to be dropped). Live channels.
  • Key pairs in kino.crypto: generateKeyPair, sign, verify, importKey, deriveSharedSecret. The kino API.
  • The hidden browser: "browser": true (approved in red, "Puede abrir páginas web ocultas para encontrar el video") and kino.browser.capture, which opens an embed in a hidden in-app WebView inside a resolve the person started and returns the video requests it made, held so their tokens stay fresh, with the headers and cookies to play them. All its traffic goes through a proxy with a per-capture credential and vetted, pinned IPs; the home network never; one page at a time; cookies and storage wiped. A page that asks for a human ends with blocked: Kino never solves a captcha. An approved plugin's resolve gets 75 s. Also, with "browser": "pages" (its own red line), kino.browser.page, which reads a page's HTML through the same hidden browser when the site's automatic check passes by itself (never from categories; the top document must stay on your hosts, every redirect hop checked, or the read ends blocked). Hidden browser.
  • Stream.label and labelled lazy copies: name each copy ("Latino · Servidor 1") for the player's new Servidor menu, and list copies as { label, ref } that Kino resolves through resolve(ref) only when the person picks one, the automatic fallback reaches it (at most 20 s each) or a download's copy choice probes it. A failed pick returns to the copy that was playing. Labelled and lazy copies.
  • meta: describe titles other sources listed (synopsis, images, episodes) when TMDB and AniList have nothing. Describing other titles.

No new apiVersion (for any plugin):

  • alternatives on a Stream: up to 8 copies of the same video; Kino moves to the next when one cannot play on the device. The contract.
  • Play on the TV from the phone, new chapters of followed series and "Para ti" work for titles of any plugin. What people see.
  • Updates: a check when the app starts (at most every 12 h), a badge for pending ones, and a failed call with a pending update says so. Publishing.
  • A signed plugin at two repositories counts as the same plugin with the same id and key. Signed plugins.
  • subtitles export: answer the player's "Buscar subtítulos en línea" for any title Kino knows by IMDb or TMDB id, alongside your videos or as a subtitle provider ("capabilities": ["subtitles"] alone). Subtitles for any title.
  • Stream.skip: where this file's opening and ending are, for "Saltar intro" / "Saltar outro"; yours win over AniSkip, a hand correction wins over yours. The contract.
  • The manifest's categories (movies, series, anime, live, radio, subtitles, utilities, adult): the plugin marketplace's category chips. The manifest.
  • Settings form: settingsStatus() is asked again after every action, so refresh: true is no longer needed. The settings form.
  • Logs: only a plugin that declares telemetry sends kino.log lines with a failure, recommended or not; for now there is no switch to turn it off. Logs and telemetry.
  • "De la comunidad" is its own tab of the Plugins screen. Publishing.
  • Stremio subtitle addons (OpenSubtitles v3, translators such as GTSubs) install as subtitle providers; machine translations show as "Español (traducido)". Nothing for you to write. Stremio addons.
  • Reserved ids: live, local, unknown, plugin, own, subtitle-keys, subtitle-prefs (the list changed: older versions reserve a few more, so if one says "El id … está reservado por Kino", pick another).
  • Claims and takedowns of community plugins: community-blocklist.json.
  • Sending to the TV: every HLS goes through the phone; a file without headers goes direct and, if the TV fails it, through the phone. Sending to the TV.
  • genre on a Home row, a live category or a playlist (peliculas, series, anime, infantil, documentales, deportes, noticias, musica, entretenimiento, otros): Categorías groups the browsable rows of every plugin by it, and En vivo filters by it across providers. Optional; without it Kino guesses from the title. The contract.
  • streamHeaders on a playlist: the User-Agent or Referer the player sends for every channel of the list, kept apart from the list's own download headers. Live channels.
  • A failing synchronous kino.* call is catchable (a full kino.storage, a kino.crypto error): your try/catch gets an ordinary Error; Kino 0.9.49 ended the whole call there. Errors your code can catch.
  • After a Kino upgrade, plugin updates that wait for approval are installed once, from the plugin's own address, with a one-time "Se actualizaron tus plugins" notice listing what each may do now. Publishing.
  • The settings form, documented whole: every field type, attribute and default, with a complete example. The settings form.

(Kino builds before genre and streamHeaders ignore them; the exact version that first shipped each was not checked.)

Also in this version (documented earlier on this page as "next version"):

  • Install from a manifest URL. People can paste the https URL of a kino-plugin.json on any public server, not only a GitHub owner/repo. Such a url: install reads entry and icon next to the manifest, cannot use sealed secrets, always counts as unsigned, and never appears in "De la comunidad" (discovery still uses the GitHub topic). A kino-plugin.json URL on GitHub, raw.githubusercontent.com or jsDelivr (cdn.jsdelivr.net/gh/owner/repo@<exact ref>/…; @latest is the default branch, a version range is refused) becomes owner/repo as before. Installing from a manifest URL, Publishing.
  • liveSearch, a new optional export for live channels (no new apiVersion: it stays 3 with channels). Kino asks it from En vivo's search while some of your channels were never listed; it returns channels like a liveChannels page, at most 100 kept, from 2 typed characters, 15 s. Live channels.
  • Big live catalogs keep paging. liveChannels gets 10 pages at first, then 5 more each time the person scrolls near the end, up to 10,000 channels (200 pages) per category. Older versions stop at 10 pages. Test with node sdk/run.mjs . live search <query>.
  • M3U lists may be UTF-8, Latin-1 or UTF-16; #EXTINF attributes may be single-quoted or bare; a list over 20 MB or a guide over 50 MB is cut at its last whole line instead of refused. Live channels.
  • Stremio addons can be installed by people from the same field (Kino generates the plugin; nothing for you to write). Their resolve, like a converted Nuvio scraper's, gets 75 s. What is supported, what is refused (torrents and P2P, always) and how to make an addon work well: Stremio addons.
  • ditu is no longer a reserved plugin id (older versions still refuse it, so avoid it).

Kino 0.9.46 to 0.9.49

  • A leading ./ in entry and icon is accepted. Kino drops it and installs the plugin. Kino 0.9.45 and older still refuse it (El campo "entry" debe ser una ruta relativa a un archivo .js), so keep writing "plugin.js" and "icon.png". The kit's validate.mjs refuses "./plugin.js" for that reason. Details.
  • Your logs help when a recommended plugin fails. For a plugin in Kino's recommended catalog, a failed call's last 30 kino.log lines (scrubbed, 2 KB) go with the error report as plugin_log. Log steps and statuses, never what the person typed or a secret. kino.log.
  • A live channel never shows a download button, even in a plugin that declares download.

About the version of each item

These items are in the builds released as 0.9.46 to 0.9.49; the exact version in which each one first appeared was not checked.

Kino 0.9.45

Contract (contract.json, maxApiVersion 5):

  • Signed plugins, apiVersion 5. Optional author signature in kino-plugin.json (node sdk/seal.mjs --keygen, --sign; validate.mjs checks it), key pinned at first install, "Firmado por su autor" on the consent sheet, "Firmado" badge, the author key in the details. It needs Kino 0.9.45+; older apps refuse an apiVersion 5 manifest. Earlier drafts of these docs said 0.9.46: it shipped in 0.9.45. Signed plugins.
  • No maximum number of hosts. The old limit of 20 is gone (only the manifest's 16 KB bounds it). Kino 0.9.44 and older still refuse more than 20, and the kit warns about it. The manifest.
  • kino.apiVersion reports 5.

Behavior you may notice (no manifest change):

  • Sending to the TV (Chromecast and DLNA) works for plugin titles. Direct for mp4/webm and HLS with no headers; through the phone when you set headers; never for DRM, DASH, progressive MPEG-TS or a format nothing identifies. Sending to the TV.
  • Plugins follow the person across their devices (phone and TV): installs, switches, approvals, settings and passwords (encrypted) sync, and the other device installs your plugin from the same address. Plugins on other devices.
  • Install addresses can also be a raw.githubusercontent.com/.../kino-plugin.json (or manifest.json, for Nuvio) URL, or a github.com/.../blob/... one; a ref that only comes from a pasted URL is not a pin. Index, Nuvio scrapers.
  • HLS downloads: EXT-X-DISCONTINUITY is kept as is unless the format changes at it; a bad key or an empty segment ends as "Este video no se puede descargar"; a retry resumes only with the same content. Downloads stay declarative: "download" in capabilities, nothing to export. Downloads.
  • M3U channel headers: #EXTHTTP, url|User-Agent=... and #KODIPROP headers are read; only User-Agent, Referer, Origin and Cookie are kept. Live channels.
  • kino.fetch: refused redirect hops count toward the 60-request limit, at most 6 fetches in flight, at most 3 host questions per call, IPv6 forms of private addresses refused, no device proxy. A plugin converted from a Nuvio scraper gets 250 requests and a 75 s resolve. Limits.

About the version of each item

The contract file states the version only for signed plugins and the host limit (0.9.45). The other items above are in the build that was released as 0.9.45; the exact version in which each one first appeared was not checked.

Already there before 0.9.45

streamHosts: "any" (apiVersion 4), liveStreamHosts: "any" (apiVersion 3 plus the channels capability), fetchHosts: "any" (written by Kino into converted Nuvio scrapers only, never for your plugin), and the question Kino asks the person the first time a stream uses a host you did not declare. They are documented in the manifest, live channels and the contract.