Skip to main content

Seraph v2026.6.30 Release Notes

Seraph v2026.6.30 is the June 30, 2026 release line for the screenshot-folder and remote-VLM analysis split.

Highlights​

  • Seraph now consumes ordinary screenshot image files from a configured local folder instead of requiring screenshot capture ownership for this path.
  • Screenshot producers remain product-neutral and disconnected from Seraph: no manifests, sidecars, API handshake, or producer-specific metadata are required.
  • Seraph computes its own local image facts, duplicate markers, observations, and report-ready details from .png, .jpg, and .jpeg files.
  • End-of-day reports include screenshot-folder observations through Seraph's existing screen-observation reporting path.
  • Settings now expose the screenshot-folder source state, manual scan action, local-only reads, and scheduler ingest posture.
  • The public companion repo seraph-quest/vlm-screenshot-server documents and runs a Dockerized image-analysis wrapper for private OpenAI-compatible VLM backends.
  • Seraph docs now include the Unsloth Gemma 4 26B-A4B GGUF target setup for a 24 GB GPU server and clearly mark first-class local-vlm Seraph provider wiring as follow-up work.

Boundaries​

  • Framekeeper or any other screenshot producer should only write screenshot files for this Seraph path.
  • Seraph does not connect to a screenshot producer service.
  • The VLM screenshot wrapper is a companion service; current Seraph releases do not automatically call it until the local-vlm provider is implemented.
  • Raw screenshots remain local unless the operator explicitly sends them to a configured local/LAN VLM endpoint.

Release Checklist​

  • Version files updated to 2026.6.30.
  • Release tag should be v2026.6.30.
  • The GitHub Release object must be created for v2026.6.30; a tag alone is not enough.