Hello from TASTEDEV,
We would like to introduce TASTEREMOTE, a remote desktop project that lets you view and control a remote computer through a web browser. Install the host app on the PC you want to access, then connect from a browser without installing a separate viewer app. You can use the TASTEDEV-operated server or run your own server.
TASTEREMOTE is under active development as we continue to improve its features and stability. Depending on your setup, you may encounter bugs or features that are not yet fully polished. Please review the supported operating systems and known limitations before getting started.
If you run into a problem or have feedback, please leave a comment or question on the product page. Including your operating system, TASTEREMOTE version, and the steps that led to the issue will help us investigate and improve the project.
Product and downloads: https://tastedev.net/products/remote
Documentation: https://tastedev.net/docs/remote
For setup instructions and development updates, follow the development log through the Learn more link below.
There is still work to do, and your feedback will help us improve TASTEREMOTE step by step. Thank you for your interest, for trying the project, and for sharing your experience with us.
The TASTEDEV Team
Version 0.156.5, published on October 21 at 16:24 KST, fixes AliasChoices for path parameters. Version 0.156.6, published at 16:57 KST, respects model alias settings for query, header and cookie parameters. GitHub stable releases and PyPI wheel/source files with actual upload times were verified for both. Check regression coverage for aliased API paths and request models.
Version 0.156.7, published on October 21 at 17:16 KST, fixes validation error locations for form and file AliasChoices. Version 0.156.8, published at 17:45 KST, preserves uploaded file positions when converting to bytes. Both stable GitHub releases and PyPI wheel/source files with actual upload times were verified. Check regression coverage for form/file alias error responses and upload-stream processing.
The stable GitHub release published at 00:47 on October 21 in Korea and its PyPI distribution files were verified. This feature release adds Pydantic validation options to request parameters (PR16542). Developers configuring request-input validation should review the options they use and their existing validation tests after upgrading.
The October 21 Korean-date stable release and PyPI distribution were verified. Deprecated **extra keyword arguments were removed from Path, Query, Header, Cookie, Body, Form, and File; unknown arguments now raise TypeError. Move additional JSON Schema properties from Query(custom="value") to Query(json_schema_extra={"custom": "value"}), for example. Check custom arguments and related validation tests before upgrading.
The official stable GitHub release and PyPI files were verified. This release fixes preservation of Pydantic Field() attributes in request parameters (PR16547). It is distinct from the removal of **extra in 0.155.0. Projects declaring validation or schema attributes with Field() should check existing input-validation and schema tests after upgrading.
This stable fix preserves Pydantic field metadata when request options are omitted. The GitHub release and PyPI distribution files were verified. Check affected request models after upgrading.
This stable fix preserves Pydantic field metadata in inferred request parameters. The GitHub release and PyPI distribution files were verified. Check affected request models after upgrading.
This stable release fixes AliasChoices for query parameters, HTTP headers and cookies. The official GitHub release and PyPI distribution files were verified. Check alias handling after upgrading request definitions that accept multiple input names.
This stable release fixes AliasChoices for named JSON body parameters and alias extraction for form models. The official GitHub release and PyPI distribution files were verified. After upgrading, check request body and form paths that accept multiple input names.
October 21 22:55 KST stable release combines query/header/cookie models. Test extra=forbid with dependencies, independent defaults/validation for shared names, and per-model header conversion. GitHub release and actual PyPI files/upload times verified.
The official Microsoft blog, GitHub prerelease, and npm 7.1.0-beta package were verified. It supports import attributes in ambient module declarations, covers source phase imports, and strengthens constraints in distributive conditional types. This is a beta rather than a stable release; check build tools, type declarations, and existing type-check results on a separate branch.
Stable releases 44.9.3 and 43.8.3, published at 12:27 and 12:05 KST on October 21, list backported fixes from ANGLE, Chromium, PDFium, Skia and V8. The 45.0.0-beta.7 prerelease, published at 11:22 KST, fixes Linux X11 paste hanging until an app restart and backports upstream fixes. At 13:04 KST, npm version, distribution URL and integrity metadata were verified for all three versions, resolving the previously unconfirmed distribution of two versions. Distinguish beta from stable and test affected paste paths. Version 42.11.18, published on October 21 at 13:53 KST, also backports fixes from the same upstream projects; its npm distribution was verified. The official release explicitly states that 42.x is out of support and recommends upgrading to a newer version. This patch does not resume 42.x support.
Electron 45.0.0 was published as stable on GitHub at 14:22 KST on October 21. It upgrades to Chromium 156.0.8078.48, Node 24.22.0 and V8 15.6. Sandboxed preloads lose Buffer and the events, timers and url modules, requiring polyfills where needed. Raw descriptors for files inside ASAR fail with EBADF, writes fail with EACCES, and screen-sharing permissions use display-capture instead of media. Check preload, file access and permission handlers. At 16:05 KST, npm 45.0.0 version, distribution URL and integrity metadata were verified, resolving the earlier unconfirmed distribution status. Distinguish stable from the earlier beta.
All three official GitHub releases were verified. npm distribution of 43.8.2 is now confirmed, in addition to 44.9.2 and 42.11.17. The earlier 43.8.2 request returned 404; the check at 09:01 KST on 2026-10-21 verified its version, distribution URL and integrity metadata. No individual fixes were listed, and none were inferred. The 42.11.17 release warns that 42.x support has ended and recommends upgrading.
This release fixes claude -p incorrectly reporting “Not logged in” when started inside a cloud session without its environment variables. It also fixes API errors being replaced by “prompt is too long” and unnecessary compaction in sessions with many MCP tools. The stable GitHub release and npm 2.1.306 distribution were verified. These are execution and error-handling fixes, not a new plugin or skill release; check automation and environments with many MCP tools.
When allowManagedPermissionRulesOnly is enabled, plugins mounted by path by Claude Desktop no longer retain allowed-tools. GitHub and npm stable distributions were verified. Review plugin behavior under organizational policy. The official skills guide explains that /doctor in v2.1.305 or later proposes usage-reduction changes based on the last 7 days of /usage. This applies to Pro, Max, Team and Enterprise plans; the check is omitted while Remote Control is connected.
Stable 0.65.0 keeps loading other extensions when one fails the allowlist check. Version 0.66.0-preview.0 hardens single-line SKILL.md description parsing and adds opt-in private-network endpoints for MCP OAuth. Both GitHub and npm distributions were verified; preview is not stable.
At this first check, Claude’s official marketplace showed 1,134,112 installs for Frontend Design and 1,009,371 for community-made Superpowers. The same Superpowers repository appeared in Gemini’s extension list. GitHub stars were 7,511 for openai/plugins and 28,189 for openai/skills. The latter README points to openai/plugins for current plugin examples. These are cumulative observations, not period rankings, growth or release dates.
October 21 OpenAI announcements expand ads to 26 countries and describe an advertising LLM separated from answer generation. Vendor claims, not independent verification; review integration boundaries and access.
October 21 OpenAI research announcement; authors provide reproduction code and read-only MCP resources. Hypotheses, not proven clinical efficacy or independent replication. Evaluate as research tooling, not an official Codex plugin.
Announced: 2026-10-21. OpenAI proposes a coordinated PHP vulnerability response through Patch the Planet and provides phpcheck-server and phpcheck-url skills in its official php2shell-checker repository. These check server versions and URL response headers; they are neither plugins nor exploit tools. OK does not verify a fix and UNKNOWN does not mean safe: compare the running PHP build with vendor advisories. Claims about AI discovery and effectiveness are the provider's statements.
Official announcement: 2026-10-21. The proactive agent in a separate app carries over memory, skills and connected apps and works in the background. Access starts through a US Pro/Max waitlist with shared usage limits. Sending messages requires approval. Teams should review permissions and usage; this is a research preview.
Official announcement: 2026-10-21. The Enterprise public beta adds change-based scanning, fix/reopening tracking, project knowledge and threat models, plus API, webhooks and an MCP connector. Teams can integrate their remediation workflows. The connector is not a separate plugin/skill release or independent evidence of security performance.
Official announcement: 2026-10-21. Proposals address model/agent security and shutdown controls, defender tools and training, legacy modernization, independent evaluation, incident reporting and coordinated response. Teams can use this as input to accountability and response design. These are vendor policy proposals, not enacted law or completed product features.
Official announcement: 2026-10-21; updated policies take effect 2026-11-20. Routers, AI gateways and other services offering direct model access require prior review and approval. Merely integrating models into app features does not itself trigger this requirement. OpenAI also describes consistent safeguards across providers and work on SafetyIDs. Developers should review their service model and the effective date. This is a vendor policy announcement, not legislation or a new API release.
The daily Trending list checked at 10:06 KST on October 21 newly showed wshobson/agents and sickn33/agentic-awesome-skills. The former describes a community plugin marketplace for tools including Claude Code and Codex; the latter describes a community project offering a skill catalog, CLI and local MCP. At 10:07 KST, GitHub API cumulative stars were 41,257 and 48,097 respectively. These are not installs, daily gains, popularity rankings or new releases, and the projects are not treated as official vendor plugins.
Supabase, Twenty and Freehire were newly observed on GitHub daily Trending on October 21 at 21:00 KST. API cumulative stars at 21:02 KST were 112,611, 58,796 and 2,014 respectively. These are PostgreSQL development platform, CRM and job-search projects; these figures are not installations, daily growth or rankings.
Inside Java listed JEP 543 as targeted to JDK 28 on October 21; the individual OpenJDK document shows Status Integrated and Release 28. It finalizes Structured Concurrency without further changes from the JDK 27 preview, managing failure, cancellation and observability by grouping related tasks within one lifetime scope. The JEP last-updated date is October 17; this is not a new SDK release today. Services using StructuredTaskScope should review task completion and cancellation.
Announcement date: 2026-10-21 (date only). OpenJDK published a special advisory concerning CVE-2026-91403 (CVSS 9.1) and eight compromised intermediate CA certificates. Affected versions are 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.32.1, 8u504 and earlier. Standalone Java runtimes should receive vendor updates first; otherwise, review the official certificate blocklist or certificate revocation checking guidance. Distributions using OS certificates can update those certificates, but FreeBSD and Homebrew packages must be updated directly. This describes Java-specific security impact and responses to the same certificate incident addressed by the Python updates; it does not confirm distribution of a new JDK version. Additional verification: OpenJDK’s response guidance was last updated on October 24 at 19:24 UTC. Check vendor release notes for the separate fix identifiers JDK-8395690 and CVE-2026-114820, and follow guidance for the runtime’s distribution type. On Debian and Ubuntu derivatives, an existing ca-certificates-java issue can make OS certificate package updates insufficient.
Stable releases published on October 21 at 20:54–20:56 KST fix NSIS downgrade blocking over MSI installations and file-association path quoting, Linux undecorated-window resizing and unnecessary Cargo rebuilds. They also include zip v9 security fixes. SDK and Rust CLI distributions were verified on crates.io; npm CLI 2.12.4 was also confirmed in the official registry at 22:04 KST; the earlier 21:10 KST 404 record is preserved. Regression-test installation, signing and repeated builds.
October 21 Go-team announcement: optional responses through November 3 inform next year’s priorities. Share development difficulties; this is not a new SDK release.
Announced: 2026-10-21. Python 3.15.1, 3.14.9 and the special 3.13.17 security announcement include pip 26.2.2 and certifi 2026.10.19 for the eMudhra/emSign certificate incident. Existing virtual environments also need separate pip and uv updates. For 3.13.17, ten official Windows, macOS and source-file URLs returned HTTP HEAD 200, and the Windows manifest SHA-256 matched.
0 comments
Sign in · Sign in to leave a comment.