Skip to content

Plompy Engine 0.12.0 — small fish, your whole machine

Choose a tag to compare

View all tags
@dalkedev dalkedev released this 11 Nov 22:43
· 4 commits to main since this release
v0.12.0
8b50c55

Meet Plompy

The engine is now plompy-engine, with an orange fish mascot, new README artwork and a refreshed project identity. It is the same self-hosted engine: private Discord threads, provider-bound coding sessions, a durable queue and Markdown memory on your own machine.

Upgrade compatibility

  • New configuration uses PLOMPY_*; legacy SZPONT_* settings remain accepted, with explicit new settings taking precedence.
  • Existing managed MCP files, browser identity, session state and cross-version locks remain usable. SQLite stays at schema 6.
  • Existing Docker installations can reuse their exact persistent volumes and physical legacy paths using compose.legacy.yaml.
  • Python uses plompy_browser / plompy-browser, with compatibility aliases for existing installations.

Before upgrading, follow the migration guide. Stop the old worker, keep a coordinated private backup and retain the same persistent data. A repository rename does not automatically upgrade your private VPS or Discord application.

Verified build

The tagged source passed the engine, Python, MCP and Playwright checks. The release workflow built and smoke-tested native Linux amd64 and arm64 OCI artifacts before publishing those same bytes. Upgrade regressions cover legacy tool approval, strict credential paths and shared-volume identity.

Public image: ghcr.io/dalkedev/plompy-engine:0.12.0

Pinned release:

ghcr.io/dalkedev/plompy-engine@sha256:004fc8c56f23ebae0a5324b132061929c3f1d085fef47f7451704b36c9ae1a73

The attached brand kit contains the original transparent mascot, README banner, social card and usage notes.

Documentation · Buy me a coffee

Assets 3
Loading