piclaw

PiClaw v3.3.3 — “Batteries Not Included”

The maintenance department has repaired the phone’s Delete button, fitted the GPU gauges with better instruments, and clarified which doors an add-on may use. The desktop application has meanwhile left the building. Its historical releases remain available, but new releases will concentrate on the web interface, server, containers and portable command-line packages.

Dependency updates arrive together, with their browser and authentication compatibility repairs included. The committee responsible for moving one chair at a time has been replaced by a committee capable of checking whether anyone is still sitting in it.

Highlights

• Keychain controls work on narrow screens. Delete and confirmation controls remain reachable on phones, with touch targets and keyboard focus behaviour preserved.
• GPU meters show more useful telemetry. VRAM displays gain sparklines and alignment fixes; optional NVML data adds GPU activity history.
• Add-ons gain dictation and authenticated socket hooks. Lifecycle fixes and qualification cover the new extension surfaces.
• Provider waits and proxy handling improve. Bounded wait fixes address slow prompt startup, while trusted-proxy HTTPS handling controls secure cookies and HSTS correctly.
• Dependencies move forward together. Browser, passkey and consumer compatibility fixes accompany the upgrades. Native desktop applications are discontinued.

Controls within reach

Keychain action cells wrap correctly at narrow widths. Delete, Yes and No controls remain inside their action area, with usable touch targets and focus restoration after confirmation.

The fix was exercised in the real Settings interface in Chromium and WebKit at phone, tablet and desktop widths. The button is once again responsible for deleting the selected entry, rather than testing the user’s accuracy.

Better instruments

VRAM meters gain sparklines and consistent alignment. Optional NVML telemetry supplies GPU activity readings and history alongside memory usage.

These displays depend on available telemetry. Unsupported or unavailable measurements are not invented to keep the instruments looking busy.

Add-on connections

Core hooks support dictation providers and authenticated add-on sockets. Follow-up changes address dictation lifecycle, import and socket behaviour, public hook parity and keychain availability.

Tool-activation responses report the effective active tools. Session-command eviction protection and activation guidance improve recovery paths.

These are extension surfaces and supporting fixes; they do not install or activate a server-dictation service automatically.

Same-origin widgets can also load WebAssembly through the qualified widget capability path.

Providers and proxies

Provider-concurrency fixes bound waits associated with prompt startup and provider operations.

Trusted-proxy HTTPS handling determines secure-cookie and HSTS behaviour from the trusted request context. Operators should retain the intended proxy trust configuration; forwarding headers from arbitrary clients do not acquire authority by arriving confidently.

The strict reply-persistence adjustment is scoped to UI-only theme replies.

Dependencies and desktop retirement

The coordinated update includes:

• Preact 11.0.1, with browser and consumer compatibility fixes.
• SimpleWebAuthn 14.0.3, with coordinated ASN.1 dependency pins.
• OpenAI 7.31.0.
• Updated GitHub Actions pins.
• Pi 1.1.0, unchanged.

Native desktop application source, build commands and release-asset production are removed. Existing historical desktop assets are retained. Web, server, container and portable command-line installations remain supported.

Related piclaw-addons #201 coordinates Pi 1.1 compatibility and browser/consumer fixes. Add-ons retain their separate publication lifecycle.

Documentation

The provider-

Locally tested hotfix. Local qualification for #1619 passed before merging. The artifact-only release workflow skipped repeat test suites, UX, integration and image smoke checks. Source: c4c7f699aa8fa5afc7d10cd416609cb2cd10149b. Actor: piclaw-bot. Artifact run.

PiClaw v3.3.2 — “Apollo 13”

The composer’s controls had become sufficiently enthusiastic about sharing a row that typing was beginning to require clearance from the navigation department. This patch restores their seating arrangement and teaches the quota display to read the duration printed on each window’s paperwork.

The release machinery receives a repair of its own: Docker smoke checks no longer require a host-side Bun installation merely to inspect the Bun installation inside the image.

Composer steering and release repair

Ctrl/Cmd+Enter steers an active turn in both skins; Enter queues while busy, and Shift+Enter inserts a newline. Starting-turn submissions retain their payload through the durable fallback, and draft clearing requires a positive acknowledgement. #1617 implements these changes.

The Docker smoke fixture now passes the runner’s UID/GID to the container, allowing its agent to write private bind-mounted workspace/config directories. This preserves strict permissions and avoids assuming runner UID 1000. The previously failing AMD64 image passes both bind and named-volume checks with this fixture.

#1618 corrects browser-test ordering: the malformed-ACK probe waits for the enabled send control, confirms submission, and waits for the error notice. Runtime behaviour and original assertions are preserved.

Emergency feedback hotfix

#1619 restores native pending feedback and timeline steering conventions in both skins, removing redundant post-acknowledgement banners while retaining draft/error safety. This retag uses the explicitly authorised artifact-only emergency path; local qualification passed before merging; the artifact workflow does not repeat release tests, UX, integration or image smoke checks. Historical UX reports will be removed because they describe the prior tag.

Highlights

• The Visual composer is usable again across screen sizes. The jump-to-latest divider occupies its own full-width row, leaving the textarea, tools and send controls accessible.
• Codex quota labels follow the reported interval. Weekly-only and other window layouts no longer inherit misleading labels from their position in the response.
• Docker publication can reach its smoke checks. The Makefile invokes the shell entrypoint directly, removing the missing-host-Bun failure while retaining mandatory image validation.

Room for the controls

The Visual skin separates the jump-to-latest divider from the horizontal compose controls. Desktop, tablet and phone checks cover layout, hit-testing and actual typing in Chromium and WebKit.

The existing timeline and divider behaviour is preserved. The divider still helps you reach the latest message; it has relinquished its claim to the keyboard’s floor space.

Quotas with the correct timetable

Structured and compact Codex quota labels now derive independently from each window’s reported duration. A weekly-only primary window is labelled weekly; conventional five-hour and weekly windows retain their familiar labels.

Other durations receive corresponding labels, while missing or invalid durations use an unknown-window label. Usage percentages, reset information and credits are unchanged.

The launch checklist

Docker smoke checks still target the exact built image digest and verify the expected Bun and restic versions, HTTP serving and process supervision. Failures still block downstream publication.

The host starts those checks through the shell script directly. Regression tests exercise the

PiClaw v3.3.1 — “The Last Starfighter”

The Department of Release Scheduling has acquired a calendar. Previously it worked from Earendil’s release announcements, which arrived with such enthusiasm that yesterday’s compatibility work occasionally qualified as archaeology before lunch. PiClaw is moving to a monthly release cadence, allowing upstream releases to accumulate, receive proper testing, and enter the building through the same door as everyone else.

Most future development will focus on transitioning to pi-durable, whatever that turns out to be once the plans have finished negotiating with the implementation, and reviewing and merging community pull requests. Contributions are welcome. The maintainer will continue tending the machinery, but will cease personally answering every upstream trumpet with a fresh expedition.

This also leaves room for other projects: rcarmo/gi and a pi-durable-based Obsidian extension using rcarmo/fixtures-vibes. The latter proposes to give the notes a durable agent, which should at least ensure that someone remembers why all those notes were written.

Local-model hotfix

Local models now use the normal system prompt and active tools by default. The compact local-lite profile is explicitly opt-in through Settings → Compaction → Local models → Local-lite prompt and tools in both web skins. Turning it off restores the previous tools on the next turn. The persisted setting is domains.tools.localLitePromptProfileEnabled, default false; Ollama, llama.cpp and private-network endpoints no longer trigger automatic tool removal unless it is enabled.

This v3.3.1 retag includes 754097577.

Release-tip update

This retag includes #1613, which fixes negative process-group operands in the local test runner’s stop/resume commands. A -- delimiter prevents the group ID from being parsed as a signal option. Linux regression tests cover both signals and preserve the child exit code.

The previous Docker publication failed because the ARM64 runner could not find bun before starting its smoke gate. Image publication is being retried; this test-runner fix does not repair that workflow setup issue.

Highlights

• A shared live browser pane. CDP streaming provides a common browser surface with input, fit modes and resizing, qualified against Chromium and Safari-engine clients.
• Less uncertainty while working. Immediate prompt-submission feedback, safer editor saves, stable thought previews and per-window workspace state make the interface easier to trust.
• Pi 1.1.0 compatibility. The Pi package family moves together to the exact 1.1.0 release. The existing integration wrapper is retained; a durable-runtime migration is future work.
• Stricter packaging checks. Vendor inventory, gzip and metadata checks detect repository payload drift; Docker smoke failures block publication.

Windows, editors and messages

An About dialog exposes version information, and each window remembers its workspace state. Divider scroll chevrons are visible on both sides. Quick-action popups ignore keys already handled elsewhere and repeated typeahead keys, preventing two officials from processing the same form.

Prompt submission reports sending and startup progress immediately. Stale HTTP responses no longer revert newer thought previews. Editor saves preserve edits made while a save is in flight, and conflict copies are created beside the original file instead of being dispatched to an unrelated district.

GPU meters retain previously proven rows through transient telemetry loss, with unavailable samples represented as gaps rather than invented measurements.

Agents and browser work

Agents gain quota inspection and combined model/thinking controls. Multi-agent respons

PiClaw v3.3.0 — “Modern Times”

The factory has been refitted while the workers were still arguing with the machinery. MCP servers get a management desk, provider login gets a private interview room, and the conversation timeline is required to contain the conversation. The GPU department has been issued meters. Previously it was allowed to describe its workload by making the rest of the building warm. Management called this telemetry. The fire brigade had another word.

The promised Earendil upgrade also happened. Then upstream kept moving, so the migration followed it through to Pi 1.0.4. The factory now checks the version stamped on the actual package, having learned that an upstream announcement is neither a delivery receipt nor a signed confession. This release concerns the tools you can use, the controls you can reach, and the long-standing arrangement whereby one SQLite writer could establish a five-second dictatorship while the interface stood respectfully silent.

Highlights

• Manage MCP servers in Settings. Classic and Visual can preview and apply adapter server overrides for transport, authentication references, tool exposure, lifecycle and timeouts, while preserving inherited and private configuration.
• Enable MCP codemode deliberately. Adapter scripting has Auto/On/Off controls and acknowledged Apply. Nested tool calls retain policy hooks; model execution inside scripts is disabled.
• Provider login keeps its secrets to itself. Owner-bound, transient dialogs handle sensitive instructions and inputs; successful login requires an explicit action before selecting a model.
• Return to a conversation without losing the middle. Cached timelines catch up through contiguous pages, restore their viewport and reading position, and offer a compose-divider handle to jump to latest.
• Inspect supported GPUs without hiring a subprocess per glance. Linux Intel i915 gets activity and memory details; NVIDIA VRAM uses a shared, cached NVML worker.
• Send and pin while the database is busy. Input admission yields during writer contention; pin and picker conflicts report a retryable failure instead of holding the web event loop hostage.
• Pickers stop hiding the matches they found. Model and session popup headings stay in normal flow during typeahead instead of covering the first result. Disabled meter rows also disappear; actual zero readings stay visible.

MCP acquires a personnel department

Both web skins now expose adapter server management through owner-only Settings. Preview shows the proposed effective configuration before Apply; edits invalidate old previews. Disabling a server leaves it inert. Removing a local override may reveal an inherited definition, and the preview warns about it. The office will accept a resignation, but it must first check whether someone downstairs still employs the same server.

Apply requires acknowledgement that active turns may be interrupted. Server changes drain current main and side sessions, await adapter shutdown acknowledgements, save privately and reload through a common startup barrier while retaining session identity and history. A failed activation reports saved but not activated. The old server must acknowledge its departure before a successor starts; a death certificate signed by the replacement is no longer considered sufficient evidence.

Adapter codemode can be switched on or off for current and new sessions. Auto leaves scripting inactive, On enables it, and Off blocks it even after explicit tool activation. Scripts can make nested tool calls under the existing policy hooks. Images and truncated output can be written to private temporary files with reported paths. Model execution inside scripts remains disabled: the accounts department has declined to approve a machine that can employ another machine without establishing who receives the invoice.

The standard MCP adapter remains the runtime owner. Native engine replacement is unavail