Plompy 0.11.0
Browser, research and analytics tools
This is a historical release. Its notes describe this version, not the current setup. See the latest stable release before starting a new installation.
This version predates Plompy Local. It covers the Discord engine; the separate local MCP gateway and starter kit arrive in 0.13.0.
GitHub notes and assets for this version may use the earlier Szpont name. Historical filenames and source links are preserved.
What changed#
- Add Playwright, Perplexity, Firecrawl, TinyFish and PostHog to the guided integrations menu for Codex, Claude Code and OpenCode, with maintained task instructions and explicit authentication modes.
- Provision an optional pinned Playwright MCP server with isolated headless Chromium, sandboxing, private per-launch output and no runtime browser installation. Exercise navigation, snapshot references, typing, clicking, screenshots and concurrent session isolation on a synthetic local page.
- Configure hosted MCP OAuth without initiating login during setup. Add an optional pinned stdio bridge for API keys held in separate private credential files; keep secrets out of managed configuration, arguments and the whole-agent environment. Bound requests, propagate cancellation, reject redirects and avoid replaying uncertain calls.
- Support Firecrawl's explicit keyless mode and request PostHog's server-side read-only mode. The PostHog integration does not install an analytics SDK or collect engine telemetry.
- Include the small API bridge in the Codex Docker image and test packaged configuration offline on both architectures. Browsers, model accounts and vendor access are provisioned separately.
- Retain Node 26 LTS, SQLite schema 6, provider bindings, saved sessions and explicit recovery semantics.
Downloads and source#
This GitHub release has no separately uploaded download assets. Its source and published distribution details are linked from the release page.
Original GitHub release · Source at v0.11.0 · Changelog at this tag
Before you upgrade#
Back up private state and credentials, review the version's migration boundaries, and retain a compatible rollback snapshot. A release does not update an existing deployment automatically.