v3.2.2

PinkCollab v3.2.2: explicit host recovery and session-safe model capabilities on Android

Highlights

• Android host connections now recover only when you refresh or tap Try again. Each action opens one connection; returning to the foreground, network availability, and socket failures no longer trigger automatic reconnects.
• The host filter shows each host's live connection status. While syncing a selected host, the loading page names that host; an unreachable host uses the same recovery surface for an empty session list and a session without retained conversation.
• Compact loading controls use orbiting dots; larger resource-loading surfaces use morphing silhouettes. Caller dimensions and indeterminate progress accessibility semantics are preserved.

Fixes

• Sessions on the same host share available models without sharing runtime-specific thinking-level fallbacks. Runtime replacement invalidates that session's capabilities; explicit refresh retains usable same-runtime data, and stale responses cannot overwrite newer results.
• Switching to a blocked host cancels the previous session's pending detail request instead of allowing an unrelated snapshot timeout to surface later.
• Retained conversations remain readable while the host is offline. Blocked hosts do not wait for session snapshots they cannot supply.

Upgrade

• Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it. After a connection is interrupted, use refresh or Try again to reconnect.
• Gateway and npm packages use the aligned version 3.2.2; this release's behavioral changes are in Android. To update the Gateway, finish active work, run npm install -g pinkcollab@3.2.2, then pinkcollab update under the existing OS user, retaining --data-dir when applicable. Restarting the Gateway ends active OMP runtimes but preserves stored sessions and pairings.

v3.2.1

PinkCollab v3.2.1: richer live tool intents and session information on Android

Highlights

• Tap the selected Android session card again to open a read-only summary with its full title, host, working directory, status, local creation/update times, and session ID. The dialog follows session identity across list reordering and reflects refreshed metadata.
• The All hosts control's clickable left edge now aligns with the first session card.

Fixes

• Live tool calls now retain descriptive intent from the assistant's original arguments, matching saved history instead of falling back to generic Read or Edit titles when execution events omit that text. Blank intent fields no longer hide a later nonblank description.
• Late tool metadata preserves completed/error states and results without recreating calls retired from the live timeline or displaying declarations that never executed. Retired calls remain available through durable details.
• Switching sessions or removing the summarized session dismisses its dialog without reopening it on later list updates.

Upgrade

• Update both Android and the Gateway to receive all fixes. Finish active work, then run npm install -g pinkcollab@3.2.1 and pinkcollab update under the existing OS user, retaining --data-dir when applicable. Restarting the Gateway ends active OMP runtimes but preserves stored sessions and pairings.
• Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it.

v3.2.0

PinkCollab v3.2.0: filter sessions by host and update the Gateway without reconfiguration

Highlights

• Android Tasks now offers an All hosts / individual host filter. The session strip, conversation pager, and older-session loading follow the selected host. The filter survives state restoration and returns to All hosts when navigating to another host's session.
• The collapsed TODO panel is smaller and keeps progress in a single compact header; expanding it still exposes phases and task details.
• Discovered OMP conversations are labeled On host / Session on host instead of History, distinguishing their source without claiming that an external OMP process is running.
• pinkcollab update applies the installed CLI to an existing background Gateway without rerunning setup or changing configuration. A stopped service stays stopped; a running service restarts only when the installation changes.

Upgrade

• Finish active work, then run npm install -g pinkcollab@3.2.0 and pinkcollab update. Use the existing OS user and --data-dir when applicable. A restart ends active OMP runtimes but preserves stored sessions and pairings.
• update requires an existing configuration and installed background startup. For a new installation, use pinkcollab setup; for foreground-only operation, replace the binary and restart it manually.
• Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it.

v3.1.1

PinkCollab v3.1.1: recover OMP after installation path changes

Fixes

• Setup can recover a stale OMP path after switching installation channels. It validates the replacement and requires interactive confirmation or an explicit --omp option; a working saved launcher remains preferred.
• Setup and doctor avoid probing the same failed launcher twice, including Windows filename case variants such as omp.exe and omp.EXE. Doctor reports recovery options without changing configuration or migrating the database.
• Recovery documentation now focuses on commands and necessary precautions.

Upgrade

• Update with npm install -g pinkcollab@3.1.1, then run pinkcollab setup with your existing transport settings. For external HTTPS, retain --transport external --public-url https://....
• A required Gateway restart ends active OMP runtimes but preserves pairings and saved sessions. Finish active work before setup. To select a replacement explicitly, use pinkcollab setup --omp omp or pinkcollab setup --omp "/absolute/path/to/omp".
• Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it.

Verification

• Gateway CI passed on Windows, macOS, and Ubuntu, including formatting, strict Clippy, and the full test suite.
• Windows CLI smoke confirmed that setup and doctor probe the failed case-variant launcher once, retain configuration, and do not create a database. This used an isolated fake launcher, not a real OMP installation or production service migration.

v3.1.0

PinkCollab v3.1.0: OMP RPC v2 support for large model catalogs

Highlights and fixes

• Gateway negotiates RPC v2 when OMP advertises support and waits for successful negotiation before sending ordinary RPC requests. Indexed rpc_chunk responses are reassembled and validated, allowing model catalogs larger than the 1 MiB physical frame limit to reach the existing model picker API. This addresses issue #5, where large catalogs caused "Model catalog unavailable".
• Chunk reassembly is bounded by local and advertised transport limits. Invalid, oversized, interrupted, or incomplete streams fail explicitly instead of leaving requests waiting indefinitely.
• Startup RPCs no longer hold the feedback-ordering gate while awaiting responses, allowing ordinary events to drain through the bounded output queue without blocking startup or session reattachment.
• Deployment documentation clarifies connection choices, background service management, pairing, upgrades, and troubleshooting.

Compatibility and upgrade

• Legacy OMP RPC v1 remains supported, but it cannot transfer model responses above its physical frame limit. Large catalogs require an OMP build advertising RPC v2 support.
• Android/Gateway Protocol 4 and the Gateway database schema are unchanged. Upgrade Android and the Gateway from the same release.
• Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app.
• The npm launcher and all five platform packages use version 3.1.0. Update with npm install -g pinkcollab@3.1.0, then run pinkcollab setup using your existing transport configuration. External HTTPS deployments must retain their --transport external --public-url https://... settings.

Verification

• Gateway regressions passed, including a 642-model catalog with a logical response larger than 1 MiB, tail-model selection, thinking-level changes, catalog refresh, and startup event bursts in v1 and v2.
• A real installed OMP smoke run passed handshake, model catalog, thinking levels, and session resume without sending a model prompt.
• The real OpenRouter large-catalog Android UI scenario has not been exercised in this validation; manual validation steps are documented in docs/development.md.

v3.0.8

PinkCollab v3.0.8: preserve Android connections on foreground resume

Fixes

• Returning to the foreground keeps a running host WebSocket and its session subscriptions instead of replacing them. An in-progress connection or retry cycle keeps its current attempt count. Stopped connections restart, except hosts requiring authentication or a protocol upgrade.
• Default-network availability still replaces host connections, and explicit refresh or retry still reconnects. The existing WebSocket heartbeat remains responsible for detecting stale sockets.
• System-bar insets stay consistent when navigating between Tasks, Workspaces, and the directory browser. The shared app shell handles status-bar and navigation-bar padding without route-specific inset overrides.

Compatibility and upgrade

• Protocol 4 and the Gateway database schema are unchanged. Build or upgrade Android and the Gateway from the same release.
• Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app.
• This does not provide indefinite Android background execution: Doze, process termination, and vendor battery restrictions can still interrupt connections.
• The npm launcher and all five platform packages use version 3.0.8. Update with npm install -g pinkcollab@3.0.8.

v3.0.7

PinkCollab v3.0.7: compact directory browsing and phone-local host names

Highlights

• The directory browser is a compact list instead of a stack of cards. Its title is the phone's host name, or Browse workspace when that name is blank. Breadcrumb tags show the workspace root and each directory inside it. Back, the parent tag, and the top bar all use the loaded listing's parent. A deeper tag opens a directory only when that path was already returned by the server.
• Create session stays docked and names the current folder, including in an empty directory. Pull to refresh keeps the current listing visible if the refresh fails. A search field appears once a listing has seven or more folders.
• A phone-local host name is stored with the pairing and shown instead of the Gateway name. Host snapshots keep that name. Setting it back to the Gateway name removes the override.
• Long-press a message to copy its source text. There is no copy button. A short toast confirms the copy.

Fixes

• Each host makes at most three connection attempts in one cycle, one second apart, then stays offline. Manual refresh, returning to the foreground, or the default network becoming available starts a new cycle. It no longer keeps checking on a timer.
• Linux host cards show the word Linux. The Tasks status stays at the trailing edge of the card strip.

Compatibility and upgrade

• Protocol 4 is unchanged. The Gateway database schema is unchanged. Build or upgrade Android and the Gateway from the same release.
• Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app. A phone-local host name is stored only on the phone and does not change the Gateway.
• The npm launcher and all five platform packages are published as 3.0.7. Update with npm install -g pinkcollab@3.0.7.

v3.0.6

PinkCollab v3.0.6: external HTTPS setup without Tailscale

Highlights

• Configure an externally managed HTTPS reverse proxy with pinkcollab setup --transport external --public-url https://pink.example.com --workspace /srv/projects.
• External setup reuses background Gateway installation, local health checks, and pairing. It saves the public URL for later pairing without invoking Tailscale.
• Non-interactive external setup requires explicit workspace roots and does not create pairing tokens.

Fixes

• Switching to external access clears the managed-Funnel diagnostic marker only after configuration changes are saved successfully. Failed saves preserve managed-Funnel diagnostics.
• Windows background integration checks use an isolated Gateway fixture instead of querying machine-wide legacy Windows services. Production legacy-service discovery and ownership checks remain unchanged.

Upgrade notes

• External HTTPS deployments must repeat --transport external --public-url <your HTTPS root URL> when rerunning setup. Omitting the transport still selects Tailscale.
• Configure your reverse proxy to forward WebSocket Upgrade and Authorization headers to the loopback Gateway. Setup checks local Gateway health, not external endpoint reachability, and does not manage DNS or certificates.
• External setup does not remove existing Tailscale mappings. Existing settings, conversations, and phone pairings are preserved.

v3.0.5

PinkCollab v3.0.5: compact Android layout refinements

Highlights

• The model picker's heading now shares one row with the Reload and Usage actions. The heading keeps its full text, while the actions use the remaining width and wrap onto extra lines when space is tight.
• Workspace rows on the Resources screen show the complete path as their only content. Rows are shorter than before, and long paths wrap so the final directory stays visible.
• Activity card chevrons share the message copy action's vertical column, so both right-hand conversation controls line up.
• Host cards on the Resources screen carry no border; they keep the glass gradient fill and wallpaper art.

Fixes

• At narrow widths or large font scales, the model picker no longer clips or squeezes its heading, and Reload/Usage stay reachable.
• Long workspace paths are no longer truncated to a single line, so directories sharing a prefix remain distinguishable.

Compatibility and upgrade

• Protocol 4 is unchanged. Build or upgrade Android and the Gateway from the same release.
• Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app.
• The npm launcher and all five platform packages are published as 3.0.5. Update with npm install -g pinkcollab@3.0.5.

v3.0.4

PinkCollab v3.0.4: durable attention responses and clearer Android conversation details

Highlights

• Answered attention requests now remain in the conversation as durable feedback, with the original question and exact answer. Selections, confirmations, text/editor submissions and cancellations survive Gateway restarts and session reopening without modifying OMP's transcript.
• Feedback keeps the same identity in live and saved history, follows the active branch, and is not duplicated when a command is replayed. Responses before OMP creates a JSONL file remain readable and survive resume.
• Android conversation text uses a 12sp Maple Mono size. Single-tool activity details open directly with the activity card, current-work labels transition smoothly, and the floating Todo panel uses a borderless raised surface.

Fixes

• A blocked attention-response write no longer blocks session snapshots or emergency Stop. Feedback and history ordering are separate from runtime lifecycle locking.
• Whitespace-only answers are preserved and copyable; only zero-length answers display the empty-response placeholder.
• The website's setup-guide and APK links share a wrapping action row with consistent spacing.

Compatibility and upgrade

• Protocol 4 is unchanged. Build or upgrade Android and the Gateway from the same release.
• The Gateway database migrates automatically to schema 7 to distinguish feedback-only sessions from missing expected OMP history. Existing possibly written mappings remain protected; corrupt or missing expected transcripts still fail explicitly. Back up the Gateway data directory before upgrading. Older Gateways supporting only schema 6 cannot open the migrated database; do not downgrade in place.
• Install the signed Android APK over the existing app to preserve pairings and app data; do not uninstall the production app.
• The npm launcher and all five platform packages are published as 3.0.4. Update with npm install -g pinkcollab@3.0.4.