Repository navigation
PLI 4.0.1
Pre-release
Pre-release
pli serveprints the PLI mark (folded paper) with the version when it starts. The README gets the PLI logo,
a speed summary, a Hugging Face link for each model family, and says that PLI is tuned for the M1 Ultra.pli setupinstalls PLI;install.shonly makes the virtual environment../install.sh installfinds Python
3.11 to 3.14, creates~/pli/venv(or--prefix), installs PLI in it and runspli setupwith the same options.
pli setupdoes what the rest ofinstall.shdid, with the same checks, messages, defaults and service settings
(profilem1-ultraon an Ultra chip with 64 GB,PLI_ANE_FFN,MLX_MAX_MB_PER_BUFFER=500,
MLX_MAX_OPS_PER_BUFFER=100,--context 229376 --parallel 4,--spill-gib 40with 70 GB free, the hybrid draft),
throughpli pullandpli service.pli status,start,stop,restart,logsanduninstallreplace the
commands ofinstall.sh, which still run them (./install.sh statusispli status).- Nothing is downloaded without consent. Before downloading,
pli setuplists each item: Hugging Face repo, page
and revision (main, not pinned, with its commit), license from the model card, size read from the Hub's API
("about" when the Hub does not answer), where it goes, the free disk, and what it brings. Files already in the
Hugging Face cache are marked "already downloaded" and not counted. It then asks[y/N];--yesanswers yes, and
without a terminal and without--yesit stops and says what to add. It stops too when the disk is too small. - Each item is optional.
--no-hybrid(no MTP head),--no-drafter(new: no draft at all,--drafter none --no-drafts),--no-models(nothing downloaded; the service now starts when the model and the draft are already on
the Mac),--model DIR,--drafter REPO|DIR(new) and--mtp-head FILE(new: a head already written). pli benchruns the public suite pli-bench-v1 against the local server (the port ofpli setup), thinking off.
The bench and its texts (811 KB) are now part of the package (src/tensorfold/bench/);tools/pli_bench.pyruns the
same code from a clone, with standard Python only.tools/quantize_mtp_head.pylikewise runs
tensorfold.install.mtp_head, whichpli setupuses.plialone prints a short help with examples instead of an argument error.- Checkpoint at the start of the last message (
PLI_LAST_MESSAGE_CHECKPOINT, 1,024 in them1-ultraprofile,
off in the code; in production since 3 Nov). Besides the history checkpoint, PLI keeps the state at the start of
the prompt's last message (the turn marker that opens the reply, looked for backwards in the history) when at least
N tokens are read there since the resume. The next request that keeps the history but not that message (a question
replaced, a reply thrown away, a sub-agent on the same history) starts from there instead of from the previous
request's checkpoint. Same text. On the agent session of the public suite pli-bench-v1: the same 8 replies, prompt
served from the cache 73.5% instead of 58.9%, sum of the times to the first token 238.0 s instead of 357.3 s
(-33%), writing speed unchanged. The production namePLI_DEBUT_DERNIERis still accepted.