Skip to content

Releases: glasgowm148/nvidia-MCP

nvidia-MCP 0.5.12

nvidia-MCP 0.5.12 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Oct 19:37
  • An APK install that completed is never recorded as a refusal: an unreadable or changed serial after the install command is outcome_unknown; failures before any install command get the prunable failed_before_install status; the "installing" status is saved before any pm command.
  • File writes that fail after the device-side move (patch apply, restore, direct add-on settings) are outcome_unknown and name the undo backup.
  • Kodi stop/restart report "stopped, not started again" truthfully when a post-exit probe or the start fails.
  • kodi_set_setting says the change is live now and persists when Kodi next exits cleanly (Kodi's JSON-RPC does not save settings).
  • CI runs the byte-parity and Manager integration tests against a kodi-manager checkout.

nvidia-MCP 0.5.11

nvidia-MCP 0.5.11 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Oct 14:39
  • Privacy: key-like words inside one quoted value no longer leak the next value (0.5.10 regression); empty values are not secrets; LWP cookie jars are withheld and Set-Cookie3 values redacted; quadratic redaction patterns are linear.
  • kodi_browse uses Kodi Manager's route guard (vendored, byte-identical) for known add-ons, refusing POV/iPlayer action routes such as bookmark erase, sign-out and playback.
  • Standard profile with writes (Android) lists the file-backup list/read/restore tools needed to undo setting changes; messages name current tools; an empty or differently-cased NVIDIA_MCP_TOOL_PROFILE falls back to standard instead of stopping the server.
  • Forwards are dropped only when the connection was refused (not when Kodi is merely down), outside the route lock; Apple TV treats a cut-off Quit reply as sent; any failure after an APK install started is outcome_unknown; APK pushes use a size-scaled timeout; file-backup timeouts are plain failures.
  • Standard tool discovery starts with 10 everyday Android tools; optional Manager/provider tools follow configured capabilities. NVIDIA_MCP_TOOL_PROFILE=full exposes advanced file, Android and APK workflows after a client restart. Profiles do not change permissions.
  • Advertised tools use consistent action names, explicit parameter descriptions and clearer settings/file/backup/layout boundaries. Old names remain callable through the same validation and safety guards; the deprecated mixed patch tool is no longer advertised.
  • Add synthetic protocol and catalogue regression checks and document the migration. No new delete/uninstall operations or device access during tool discovery.

nvidia-MCP 0.5.10

nvidia-MCP 0.5.10 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Oct 09:09
  • adb forwards that disappear (Shield sleep/reboot, adb server restart) are re-established instead of failing every Kodi/Manager call until restart; a request is resent only when the connection was refused before anything was sent. adb connect clears cached forwards.
  • Large push_verified pushes get a size-scaled timeout (and accept one).
  • Privacy: quoted values containing spaces and JSON-escaped pairs are fully redacted.
  • Empty NVIDIA_MCP_STATE_DIR/LOCALAPPDATA (and empty or relative XDG_DATA_HOME) no longer put private state in the working directory.
  • APK recovery bundles of attempts that failed before any transfer are removed, and stale untouched bundles are pruned.
  • "Kodi is playing" and similar guards are recorded as refusals with specific kinds; an install timeout after transfer is outcome_unknown; a Quit cut off mid-reply counts as sent.
  • Add-on ids made of dot segments are rejected; a missing Kodi folder is reported as not found; SDK tool start failures are actionable.
  • Kodi Manager add-on settings: rows from raw/settings.db stores are written to the store they were listed from, and the page keeps the add-on's editable/read-only reason.

nvidia-MCP 0.5.9

nvidia-MCP 0.5.9 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 23:30
  • Device command status trailers now report the command's own exit code. Previously the status was always 0, so a failed tar, cat or head on the device (including the Kodi data snapshot before an APK install) could pass as success.
  • adb and SDK child processes no longer inherit the MCP server's stdin, so a long adb shell cannot consume the client's JSON-RPC messages.
  • A Kodi that stalls its reply while quitting is treated as "quit sent" (then waited for) instead of "Kodi refused Application.Quit", on Android and Apple TV.
  • kodi_status stops after the first connection failure by error kind instead of by message text.
  • Operation history records trakt_unavailable as a refusal (byte-identical with Kodi Manager 0.7.36).

nvidia-MCP 0.5.8

nvidia-MCP 0.5.8 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 22:26
  • Operation history retries SQLite busy/locked errors (including table creation on connect and
    reads) for about 2 s, so concurrent writers on Windows no longer drop records. The module stays
    byte-identical with Kodi Manager 0.7.35.

nvidia-MCP 0.5.7

nvidia-MCP 0.5.7 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Oct 21:54
  • Add support bundle v1 and bounded private operation history shared with Kodi Manager; carry correlation and backup/undo references across the optional interface.
  • Preserve Manager reason codes, refuse automatic write retries after ambiguous replies/timeouts, and keep completed work successful when audit recording fails.
  • Add synthetic cross-project and generated-wheel/add-on interface checks. The pinned Manager 0.7.23 ZIP remains unchanged; new diagnostics are capability-negotiated.
  • Complete fresh Apple TV installation and CLI environment/path instructions; correct the sample Manager minimum and backup-ownership guidance, and document private token entry when storage is blocked.
  • Shorten the project and profile-helper READMEs, add a documentation index, move the generated tool catalogue to docs/tools.md, and correct outdated setup/build examples. Runtime and bundled companion are unchanged.

nvidia-MCP 0.5.6

nvidia-MCP 0.5.6 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Oct 10:37
  • Fix the opt-in Android profile handoff's automatic reopen race. Arming no longer starts a ten-second countdown while Kodi is quitting. The child waits for Application stopped, obtains a versioned READY acknowledgment, and schedules one reopen two seconds later before ending the old process.
  • Helper APK 1.1 / versionCode 2, client DEX and shell script must be rebuilt and deployed together with the existing private token/signing identity. An outdated APK refuses before Kodi quits. Readiness expires after two minutes and is consumed once; cancel clears it and any pending launch. Unexpected process death before the saved shutdown checkpoint still requires manual recovery.
  • The actual Java readiness policy is tested for short/slow shutdowns, expiration, duplicate readiness, permission revocation and cancellation. A private build with unchanged signing key/token passed automatic Adults → Kids → Adults switches on the reference Shield / Kodi 22 RC1 (29.1 / 23.5 seconds), returning to Home and verifying both profiles' channel counts.

nvidia-MCP 0.5.5

nvidia-MCP 0.5.5 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Oct 09:53
  • Bound HTTP exchanges to 60 seconds with a socket deadline, including dripping headers and success/error bodies. Disable keepalive reuse so a cancelled timer cannot affect another request; retain the 20-second read/3-second connect timeouts and byte bounds. Never retry mutations automatically.
  • Classify answered-but-stalled responses as response_timeout; partial or malformed replies stay distinct from offline services. Apple TV launch/restart cannot use these failures as offline permission. Preserve the known no-reply disconnect case.
  • Refuse successful Manager envelopes missing data, normalize deeply invalid JSON and avoid oversized error-body copies.
  • Bundle Manager 0.7.23 with delayed access/profile rechecks, retired-generation refusal and operation-scoped backup roots. Add real loopback header-deadline and synthetic stream/profile regressions. No live TV changes; physical Apple TV validation remains pending.

nvidia-MCP 0.5.4

nvidia-MCP 0.5.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Oct 08:12
  • Bundle Manager 0.7.22: failed self-restore rollback preserves live access/identity, and aliased tvOS backup paths keep XML in virtual storage.
  • Clarify older alias-affected snapshot refusal and fresh-backup guidance. No MCP tool/backend contract changes; retain private pairing traces, Android defaults and reviewed layout gates. Physical Apple TV validation remains pending.

nvidia-MCP 0.5.3

nvidia-MCP 0.5.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Oct 07:53
  • Silence pyatv's PIN/key logs throughout private pairing, including when debug logging is enabled. Restore prior logger levels after success, cancellation or failure; retain unrelated application logs.
  • Bundle Manager 0.7.21 with nested-profile read confinement and Kodi's physical Siri Remote XML exception. Add regressions for both successful and failed noisy pairing.
  • Preserve Android/Shield defaults, tool contracts and reviewed layout gates. Physical Apple TV validation remains pending.