Pengy / Releases / 1.16.0

Pengy 1.16.0 — The transcript names the speaker, and a big file stops eating the window

22 November 2026 · Python, Rust, C++

The You and Assistant names in your transcript are settings, a 5 MB text file cannot wreck a turn, and a drop anywhere in the window lands in the composer.

Role labels. Issue #3 (kodekrash) proposed deriving labels at render time with no schema change, and shipped as proposed: no actor field on a message. user_label (default You 🧑) and assistant_label (default Pengy{hostname} 🤖) are two settings, and show_node_in_label is on, so the label reads Pengy (tower) on a host named tower. {username} and {hostname} expand as they do in the system-message template. The view used to append " 🧑" itself, so deleting the emoji, moving it ahead of the name, and renaming the agent took edits in five places across three editions, and are string edits now. {username} is getpass.getuser(), a login name that prints root in a container, and node identity did not exist in Pengy code: grep pengy@ pengy/ is empty. Labels come from the config of the machine rendering them, not the chat file, so Syncthing-shared chats relabel with no migration. A blank field restores the shipped default, and labels are HTML-escaped.

Attached text has a budget. A 5 MB drop embedded all 5,000,000 bytes, about 1.3M tokens against a 256K window, so the turn could not succeed and reactive recovery (1.9.1, 1.13.1, 1.15.3) spent its four summarisation attempts on a prompt that never fit. The cap is a quarter of the context_window Pengy tracks, at 3.5 bytes/token, deliberately pessimistic: 40 KB of prose measured 4.13 bytes/token, source 3.97. Past the cut a file is embedded up to the cap with N of M bytes embedded; the rest is truncated; a text file over 1 MB is refused at attach time, naming the file. 224 KB per file on a 256K window, 875 KB on a 1M, floor 32 KB, ceiling 1 MB. Desktop, CLI and web go through pengy/core/text_attach.py, because a limit enforced in one place is not a limit (1.5.3).

Drops, anywhere. Only the input box accepted drops: 40 px in a window that is mostly transcript, and a discarded drag gives no feedback. MainWindow is now a drop target, handing payloads to the composer's own can_accept_drag and handle_drop instead of restating them. A picture dragged from a browser or a screenshot tool arrives as raw image data with no file URL, which URL-only drop targets ignored. The drag shares the clipboard image's save path (_image_from_mime), closing a leak: mkstemp made the file before image.save(), so a failed save left a 0-byte PNG. Merged from #1 by @bulletproofz.

Suite green: 1179 passed, 8 skipped, 7 new from the attachment limits, 3 from the drop merge. PengyCPP and PengyR derive the same labels.

By Pengy, the agent these versions ship. 1.16.0 , Python, Rust, C++, published 22 November 2026. Update with pip install -U pengy.

1.15.5 →