PzzaCode 0.2.32

What's new in 0.2.32

This update improves terminal file handling, work preservation, Agents Hub, paired-device controls, dictation, and desktop reliability. macOS builds now target Apple Silicon only.

Terminal file drops

• External file and URL drops no longer navigate the desktop webview like a browser. Internal tile, workspace, and editor drag-and-drop remains available.
• Drop files onto a local terminal to insert their shell-quoted absolute paths. Files dropped onto a remote terminal are uploaded to private temporary storage on that device, and their remote paths are inserted instead.
• Drops never press Enter or submit commands automatically. Validation rejects unsupported files and unsafe paths, bounds upload sizes, and cleans up incomplete uploads.

Preservation-first Sync

• Sync prefers the remote development branch, falling back to main when development is unavailable.
• Tracked and untracked edits are preserved before updating. Ahead or divergent committed work is retained through durable recovery references rather than discarded or merged into the chosen baseline.
• Successful preservation is informational instead of an Attention failure, with recovery details available. Network, authorization, unresolved-operation, concurrent-edit, and other safety errors remain actionable.
• Repository locking and preservation checks protect repeated or overlapping syncs. Ignored files are not removed to force an update.

Faster Agents Hub and reviewed role setup

• Library screens load lightweight metadata first and fetch full content only when needed. Cached, deduplicated reads and incremental per-device global-instruction loading keep a slow device from delaying healthy devices.
• Discover imports have working icons and action states. Complete skill bundles are pinned to verified source revisions, checked for integrity, and imported with bounded concurrent downloads. Repeated imports recognize the same source instead of creating duplicates.
• Skill assets can be inspected without executing imported code. Revision-checked updates and fresh deployment previews protect existing files, profile links, and concurrent edits.
• Discard uses a trash icon and an explicit confirmation.
• Local setup includes reviewed development, browser-testing, and marketing skill bundles, plus Developer, Reviewer, QA, Security Reviewer, and Social Media Manager profiles deployed into separate role folders. These local deployments are distinct from the application bundle.

Clearer confirmations and safer file selection

• Consequential actions use queued confirmation dialogs with cancel-first focus, keyboard trapping, focus restoration, and protection against repeated actions while work is pending.
• Unsaved editor, Agents Hub, and bridge-setting drafts participate in exit and restart guards. Active saves and edits made after a confirmation invalidate stale approval.
• Custom file pickers remain bound to the selected device, ignore delayed responses from a previous host, and prevent selection while loading or after access errors. Fixed-device and disabled fields cannot silently switch destinations.
• New Session and New Workspace forms have more usable space while keeping their actions reachable on smaller windows.

Secure MCP-first paired-device workflows

• Supported paired-device workflows have named controls for discovery, scoped files and terminals, browser sessions, simulator operations, builds, and tracked jobs.
• Pairing and sensitive actions use explicit receiving-device consent. Ordinary MCP requests can request, inspect, or cancel an approval, but cannot approve themselves.
• Access is tied to verified peers, approved projects, finite grants, and resource scopes such as browser origins, tabs, simulator IDs, and application IDs. Expiry and revocation are checked when work executes.
• Mutating jobs use request IDs to avoid duplicate submissions after a lost response. Job status, cancellation, permission refusals, and missing prerequisites remain distinct.
• File and terminal boundaries constrain sensitive paths and returned data. Browser controls do not expose unrestricted evaluation, cookie export, or unsupported extension side-panel automation.
• Explicitly granted terminal, build, and test execution runs with the receiving OS user's permissions. Project scoping is not an OS sandbox.

Quick Chat continuity and model presentation

• A dropped SSH attachment can reconnect in the background to the same verified conversation, with bounded backoff, cancellation, connection status, and a manual retry. Terminal input is never replayed, and a failed attachment does not silently create a replacement conversation.
• New Quick Chat sessions for the Codex profile launch through pz. Existing conversations retain their original launcher and session identity rather than being restarted to change launchers.
• Terminal icons distinguish the launcher from a recognized effective model when attributable evidence is available. Proxy URLs alone are not evidence; unknown aliases retain the launcher icon, and configured evidence is distinguished from reported evidence.

Appearance and Usage clarity

• Semi-transparent mode has a persisted text-visibility slider. Dark themes move text and icons toward white, and light themes toward black, while preserving hierarchy below maximum visibility and contrast on filled controls. UI and MCP appearance settings stay synchronized.
• Usage charts use solid token-volume bars rather than misleading dashed estimate bars. Zero-token days remain zero-height, and daily values are available in a table.
• Missing or partial pricing stays explicit. API-estimate disclaimers use a smaller informational style and are not presented as billed spend.

Native stability and bilingual dictation

• Native file-drop routing preserves the initialized webview and KVO class, fixing the startup crash while retaining native file callbacks and internal HTML drag events.
• Native Quit follows unsaved-work guards and managed cleanup. Speech workers and cached Metal resources are released before process teardown; the sidecar and terminal attachments are reaped without terminating persistent terminal sessions. Cleanup failure leaves the app open for retry.
• Fixed a bilingual dictation case where an uncertain word disappeared during a language switch and was lost when a later decode restored it. Append-only output now waits at the uncertain boundary rather than typing past it or rewriting terminal input. Stable speech continues to stream; uncertain boundaries can delay insertion until recognition settles or the utterance finalizes.

Verification and delivery

• Browser checks use a pinned project runtime and fail clearly when prerequisites are missing instead of silently skipping coverage. Browser setup and execution have explicit commands, and cold navigation has a separate bounded allowance from interaction assertions.
• Full native verification can include the real-model streaming/cancellation and resampling checks. Isolated native harnesses cover startup, file/HTML routing, normal Quit, active recognition, and cancellation without using the running app's sessions or microphone.
• Real bilingual regression evidence records raw decoder words separately from assembled output, and keeps the original audio and expected transcript unchanged.
• macOS builds target aarch64-apple-darwin only. Updater metadata advertises only darwin-aarch64, so ARM artifacts are not offered to Intel installations.
• The local replace/reload workflow verifies the ARM candidate, retains the previous app for rollback, and checks actual process exit when a native Quit returns a non-zero Apple-event reply. Installed-bundle verification checks version, architecture, signing, packaged files, backend health, and preserved terminal processes.

Activation requirements

• Devbox-to-Mac browser and simulator activation still requires a person to complete pairing and grant the relevant resource permissions. Browser access also requires the official extension and its connection/tab approval. These live paths have not been verified end to end; implementation does not replace those activation steps.

Author: Berke (pzzaworks)