Files
prompt-optimizer/releases/v2.10.0.en.md
2026-05-03 14:42:38 +08:00

6.0 KiB

Prompt Optimizer v2.10.0

Summary

  • Introduces a prompt model standardization layer that normalizes prompt modes, sessions, histories, examples, favorites, and source assets across workspace types.
  • Reworks favorites into resource-aware prompt assets with version history, reproducibility examples, source bindings, workspace application, and dedicated asset management UI.
  • Adds resource-complete backup/import flows for favorites and related assets, while making Data Manager more compact and easier to scan.
  • Makes Prompt Garden a first-class discovery, import, and favorite source across web, desktop, and extension builds.
  • Improves reliability across variable generation, Electron IPC, desktop preferences, backups, and docs-only CI behavior.

Highlights

This release is a broad foundation upgrade for reusable prompt work. Prompt sessions now have a standardized projection model, favorites can preserve the assets and examples needed to reproduce a prompt, Garden imports can become real favorites with source media, and backups can carry the resources needed to move that work between environments.

Product Updates

Desktop

  • Prompt Garden import and favorite flows are available in desktop builds through the shared built-in Garden defaults.
  • Favorite prompt asset version APIs are exposed through the Electron preload bridge.
  • Preference IPC handlers are registered in desktop startup so preference reads and writes are available through the Electron bridge.
  • Electron proxy payloads are serialized safely before crossing IPC boundaries, reducing failures caused by non-serializable response objects.

Web

  • Added Prompt Garden discovery and paste-import entry points from workspace utility menus and empty image prompt states.
  • Added Prompt Garden favorite import support, including a save-favorite confirmation flow with Garden metadata, media previews, examples, variables, and source details.
  • Pasted full Prompt Garden links now preserve exampleId and subModeKey for workspace imports, while favorite imports intentionally drop exampleId and save the prompt-level favorite.
  • Prompt Garden imports now show a persistent loading message while prompt data and image assets are fetched.
  • Reworked favorite surfaces with a split panel shell, source asset badges, an asset management dialog, prompt asset version list, and prompt asset version preview modal.
  • Favorite editors and detail panels now support richer reproducibility data and source-bound prompt assets.
  • Added workspace application helpers so favorites and saved examples can apply content, variables, image inputs, and source metadata back into matching workspaces.
  • Data Manager now uses a more compact layout and supports resource-complete backup package imports.
  • Filled variables can now be used as generation context when applying or generating prompt content.

Extension

  • Prompt Garden import and favorite flows are available in extension builds through the same built-in online Garden endpoint used by production web and desktop builds.
  • Full Prompt Garden link paste compatibility is supported in the extension UI as part of the shared workspace and favorites components.

Core/Infra

  • Added a prompt model service layer for prompt content, modes, sessions, histories, examples, favorite mapping, and shared prompt-model types.
  • Added prompt session projection and session asset binding utilities so workspace state can be represented consistently across basic, context, pro, and image modes.
  • Added built-in defaults for VITE_ENABLE_PROMPT_GARDEN_IMPORT and VITE_PROMPT_GARDEN_BASE_URL, with runtime and build-time env overrides still taking priority.
  • Added prompt asset version management and standardized prompt asset session handling for favorites.
  • Added resource-complete backup import support and included image model configuration in backups.
  • Added favorite resource package and data manager resource package utilities for moving favorite content together with referenced assets.
  • Added source asset utilities and history source binding helpers to preserve where generated or saved content came from.
  • Added explicit docs-only workflow path ignores for docs/**, mkdocs/**, and releases/** changes.
  • Consolidated prompt model standardization notes for implementation and review reference.

Fixes

  • Fixed Prompt Garden full-link paste compatibility so workspace imports no longer lose the selected example.
  • Fixed a silent waiting period during Prompt Garden favorite import by surfacing visible loading feedback.
  • Fixed duplicate or overly heavy Prompt Garden detail rendering in favorite detail views.
  • Fixed missing image model configurations in exported backups.
  • Fixed desktop preference IPC handler registration.
  • Fixed Electron proxy IPC serialization for payloads that cannot cross the bridge directly.
  • Fixed favorite asset cleanup and source rendering edge cases while moving favorite details into the new surface layout.
  • Fixed workspace routing and restore behavior around externally applied favorite/example content.

Breaking Changes / Upgrade Notes

  • None.

Developer Notes

  • Garden integration is gated by VITE_ENABLE_PROMPT_GARDEN_IMPORT; VITE_PROMPT_GARDEN_BASE_URL controls the source endpoint and defaults to https://garden.always200.com.
  • Web Docker/runtime deployments can still override Garden settings through window.runtime_config; Vite builds for web, desktop, and extension use the root env files plus core defaults.
  • New prompt-model utilities live under packages/core/src/services/prompt-model/*; use them instead of re-deriving prompt mode/session/history/favorite shapes in UI code.
  • Source-aware workspace flows should preserve SourceAssetRef / history binding metadata instead of flattening everything into prompt text.
  • Backup/import work should use the resource package utilities so referenced assets travel with the user-facing data.
  • Release CI no longer runs for pure docs, mkdocs, or release-note directory changes, which also prevents the Docker workflow from following those docs-only updates.