Repository navigation
v1.2.0
ProjectionLab MCP 1.2.0
A hardening release from a full code audit, plus two things users will notice:
the assistant now says when an update is available, and two browsers no longer
compete for the connection. Update the server and the extension together. A
1.1.0 extension still works with this server (the wire protocol version is
unchanged), but the standby and version-line behavior needs the 1.2.0
extension.
New
- Update notices.
projectionlab_check_connectionreports the server,
extension, and latest npm release versions, with plain-languagenotices
when something is out of date. The assistant mentions a notice once and
carries on. - Version line in the extension. The options page shows a line when the
extension and the server it reached are different releases, with a link to
the releases page or a hint to restart the assistant. PL_UPDATE_CHECK(default on): the server makes one request per start
to npm to read the latest release number. The request carries no personal,
plan, or configuration data. Set it tofalseto turn the check off. See
Privacy.- Standing by. The browser that is connected keeps the connection. A
second browser shows "Standing by", retries every 30 seconds, and connects
on its own when the first one goes away. Pressing Save on a standby
browser's options page switches to it. The bootstrap snippet follows the
same rule.
Security and safety fixes
- A frame that is valid JSON but not an object (
null,42) no longer ends
the server process. Any local client could trigger this without the token. - A blank
PL_WS_TOKENcounts as unset and a token is generated; it no longer
lets a client authenticate with an empty string. - The Plugin API key is scrubbed from every log line, from the fatal-error
output, and from the error details of the plan-data and summary resources. - Snapshots store the Plugin API key as a placeholder and put the real key
back on rollback, so a rollback of settings restores a working key. A
snapshot written by an earlier version that holds[REDACTED]in its
settings is refused with an explanation, in the dry run as well as on
confirm. - A write payload that still holds
[REDACTED]under a secret-named field is
refused, dry runs included, naming the paths. This stops a redacted read
from being written back as real data. projectionlab_update_plan_sectionvalidates the shape ofsectionData
for the section named. An omitted value,null, or the wrong container no
longer deletes or corrupts a section.
Behavior changes
- A plan or event name that partially matches more than one item is refused
with the list of candidates, where it used to pick the first match. - The legacy
patchinput ofprojectionlab_update_plan_eventvalidates
existing fields the waypathChangesdoes, and reports each change as
{ "before": ..., "after": ... }. A field the patch adds reports
"before": "[ABSENT]". projectionlab_rollbackreportssuccess: truewhenever the restore is
accepted, with a separateverifiedflag for the re-read check, like the
other write tools.- A path that addresses an array with anything other than an index, such as
length, is refused. - An invalid
PL_WS_PORTorPL_APP_URLstops the server at startup with a
message naming the variable. An unknownLOG_LEVELfalls back toinfo. - An API error that merely contains the digits 401 or 403 is no longer
reported as a bad Plugin API key.
Extension
- A wrong token or protocol mismatch is not retried until you press Save, and
that now holds across the browser restarting the background worker. - Save works without editing a field, in Chrome and Firefox.
- The extension reconnects within a few seconds after the server restarts.
Housekeeping
- Files written for results too large to return inline are deleted after 30
days, like snapshots. - Snapshot retention goes by file modification time and no longer reads every
snapshot on each write. - When a new browser replaces the connected one, cached data and in-flight
requests from the old one are dropped at once.
The extension was verified in Chromium and Firefox with two browsers sharing
one server.