What's new in BibCode

Each environment has a Host dashboard (the environment card's menu, Settings > Remote Servers, and the status bar's Resource Manager) with its host's CPU, memory and volumes, live and since the server started. It lists the volumes it hides and why, shows per-volume statistics, never reads network volumes, and says when the volume list is not answering. Agents can read the same figures with the `host_metrics` MCP tool. (#292)

The Host dashboard on Linux no longer lists another running BiBCode AppImage's mount, or one a killed instance left behind, as a full read-only volume. (#353)

A refused pairing offer or pairing credential is now logged as a warning with a fixed reason, so a pairing that fails shows in the server log; the log never holds the offered link or the credential. (#358)

An expired pairing link, pairing offer or session is refused from the moment it expires. Before, one whose expiry fell on a whole second could still be accepted for up to a second, because expiry times were compared as text. The same text form could delete a signed-in device's refresh token up to a second early. The server now writes every stored timestamp at one fixed width, and re-writes the timestamps a client sends or a session import carries in that form before storing them. (#362, #366)

With the Profiler on, an error that the "Something went wrong" screen catches is recorded as a `client.render-error` event and grouped in one finding. It holds the error's type, React's error number, component names and the route pattern, never the error's message. (#360)

Stage, layer and Jobs headers in the pipeline detail view now read as group labels on their own strip, apart from the job rows below them, in the wide and the stacked layout; each is still one heading with its status, name and job count. (#340)

A push that fails for missing credentials on a remote server now says that Git ran on that server, names it, and tells you to run `git push` in a terminal there; Source Control and the Git Manager show the same guidance. (#343)

Background status reads no longer take Git's index lock, so your own `git add` or `git commit` in a terminal no longer fails with "index.lock: File exists" while BiBCode is open. On Linux and macOS BiBCode asks Git to stop before it forces it; on Windows it forces it as before. Either way it then removes an `index.lock` that its own stopped process left and that nothing else is using, including when it quits. (#341)

Local status for a worktree is delivered while a stacked action or a Git Manager push, publish, force push or remote branch delete waits on the network. Writes stay one at a time; pull and fetch still wait. (#345)

The profiler warns about a leftover worktree folder only when it shows worktree evidence, one finding per folder, and the warning ends when the folder is gone. BiBCode records the worktrees it creates, so folders that were never worktrees no longer warn every ten minutes. (#344)

Create worktree starts fresh every time it opens, after a creation or a close: the last Name, Create From, mode, base override, Advanced, Create more and agent pick no longer come back. Input stays while the dialog is open, and Create more still keeps the project, mode, agent and base override for its batch. (#346)

Source Control has a Review changes button that starts a code review of your branch and its uncommitted changes in a chat panel beside the thread or in an AI Terminal. A Claude review starts in Claude's plan mode, a Codex review runs in Codex's read-only sandbox, other chat agents ask before edits or are only told not to edit, and Settings → Agents and the button's tooltip say which applies. A review's findings offer no Implement. The review prompt can be set per user in Settings → Agents and per project from the button's menu, which also starts a review once with another agent or with added instructions. Mod+Alt+Shift+R starts a review from the keyboard. On Windows, a terminal review gets the prompt with its line breaks as spaces. (#293)

Sign-in guidance after a failed fetch or push now appears only when Git's own `fatal:` line says it could not read a username, so a commit message or hook output that contains those words no longer triggers it. (#354)

A pull request that the forge CLI could not look up is no longer asked for again at once on every status change: a failed lookup waits 5 seconds, and a pull request shown for a branch disappears when the lookups keep failing and the last answer is more than 5 minutes old. A status-neutral local change no longer leaves an outdated answer in place, and a lookup that is running when BiBCode quits ends with it. (#355)

A worktree recreated at the path of a removed one keeps its own creation record, and a record on a volume that is not mounted is no longer deleted by the profiler's worktree audit. A failed worktree creation that is rolled back is now visible to the profiler. (#356)

A new worktree's or project's chat lists only its own provider's models in the composer, before the first message too; to use another provider, add a chat panel from the chat header `+`. A new chat that has not been sent still lists every ready provider. A chat whose provider is disabled or removed now says so above the composer and keeps Send unavailable, and Add as project in Files opens the new Main on your Default Agent instead of Codex. (#347)

Expanding a reasoning row in the chat no longer scrolls the list to its end on Windows. (#351)

The app no longer falls to the "Something went wrong" screen (React error 185) when a closed branch picker in Git Manager, or a closed model picker, receives a new list, as happened after a branch switch and a fetch in a repository with thousands of branches. (#360)

The model picker opens with an empty search every time, instead of the text from the last time it was open. (#358)

Markdown opens editable in rendered view, with a formatting group in the Files toolbar (paragraph, headings 1 to 5, bold, italic, strikethrough, bullet, numbered and task lists, block quote, a link dialog, Insert image next to the file, collapsible section). Undo and Redo work in both views and a save changes only what you edited; frontmatter and constructs the editor cannot represent stay as written or read-only. (#342)

Images a Markdown file links by a relative path show in the editable rendered view, read from the project relative to the file, in the desktop app, the browser and remote environments; an inserted image shows at once, and a path outside the project is not read. (#345)

Ticking a task checkbox in a read-only Markdown or `.mdx` file keeps the file's source Undo history. (#342)

Mermaid diagrams in an editable rendered Markdown file are drawn again, as one block that is not edited in place; the file's source is kept as written. (#342)

The Linux AppImage now carries its own GStreamer plugins for the audio Files previews in WAV, MP3, Ogg, WebM and FLAC files, instead of relying on the system's plugins, which its bundled GStreamer cannot load on newer distributions. M4A is not covered: its AAC decoder is not bundled.

A PDF preview in the Files panel is no longer blocked by the page's content security policy in Chromium-based webviews and browsers: the Windows desktop app, and browser mode in Chrome or Edge.

A read-only rendered Markdown file (large files, and files the editor cannot change safely) now loads its relative images from the project, as the editable view does. (#358)

After you allow an update to install, the Files block survives a reload of the window and covers a Files source opened during the install, and the "Installing an update" dialog has Check again, which asks the desktop whether the install is still running. (#357)

While an update you allowed is installing, the remote-update notice's Manage devices action is switched off and says it is available when the update finishes, instead of opening Settings underneath the dialog. (#357)

Share this host lists this computer's private addresses (local network, VPN or overlay, and Tailscale) while remote access is still local-only, each marked as enabling remote access; choosing one turns remote access on and makes the code for that address. Before, only "Automatic (LAN)" was offered. (#361)

On Windows, when BiBCode has no administrator rights and needs its firewall rule, it now asks through the Windows permission prompt when you generate a code, and if you decline it says what is missing and offers Retry, instead of failing with a raw error. Without administrator rights BiBCode cannot remove that rule later: turning sharing off returns the server to local-only and may leave the rule in place. A rule that was disabled or changed to block is replaced instead of reused. (#361)

BiBCode no longer manages Tailscale Serve: the Tailscale HTTPS switch is gone, BiBCode only reads Tailscale addresses, and a Serve address you set up yourself is listed when it answers. (#361)

Settings > Appearance lists six built-in themes (Tokyo Night, Matrix Dark, Matrix Light, Verdant Light and the existing Light and Dark) and lets you duplicate, edit with a live preview, import, export and delete custom themes, with contrast warnings. New terminal sessions and the pipeline job log can follow the theme's terminal colors, and a theme can also set scrollbars, focus rings, control shadows and selected rows. (#290)

Clicking a theme row applies it and, when the theme's base differs from the mode on screen, switches the mode with an Undo that restores the previous mode and theme. (#290)

The left panel draws its repository, environment, primary checkout, worktree and chat rows as five visually distinct levels in every built-in theme, and a theme can style each level. (#290)

On the desktop app, exporting a theme or plan opens the native Save dialog, and closing, quitting, restarting or installing an update with unsaved Files edits asks first with Save all, Discard and Cancel. (#290, #342)

On the macOS desktop app, a menu, popover, select or combobox opened over a native browser preview is drawn above it, and the preview is hidden only where the popup covers it. (#358)

When you return to a Claude AI Terminal on a macOS or Linux server after it printed more than BiBCode keeps for a redraw (1 MiB or 5,000 lines, or 512 KiB in the client), BiBCode asks Claude to redraw its screen, the way it does when resumed, so characters missing from the replay come back. This is a best-effort repaint for Claude terminals BiBCode starts, not a rebuild of the terminal's state; other programs and Windows servers still need a panel resize, and a Claude session you suspended in that terminal resumes. (#348)

A terminal that kept an old row count, so an AI CLI lost its bottom lines or footer until you changed the panel's width, now corrects itself: the server confirms each size in order with the output, a size it did not apply never resizes the view, and a window whose connection dropped gets the terminal's size back when it reconnects, unless someone typed in the other window meanwhile. (#348)

A terminal laid out with no width or height, such as a center terminal behind a maximized right panel, keeps its size instead of resizing its program to 2 columns or 1 row. (#348)

A terminal refits when the display scale changes, for example after moving the window to another display, so a bottom row clipped by the new scale's row height no longer stays cut off until a panel is resized. (#348)

When resizing a terminal's program fails, BiBCode retries it a few times, so the program no longer keeps its old size, with its bottom rows cut off, until the next panel resize or keypress. (#348)

Opening, collapsing or dragging a panel no longer resizes its terminal's program to 2 or 5 columns on the way: a terminal takes a new size once its panel holds still for a moment, and a small panel that holds still still sizes it. (#348)

A terminal that was off-screen or hidden while its program kept printing after its rows shrank comes back showing its last lines and footer, instead of a view stuck rows above them until you changed a panel's size; a terminal you had scrolled up to read stays where you left it. (#348)

When two windows, for example on two machines, show the same terminal, the window you last used sizes it and the other one shows the whole terminal scaled down to fit instead of cutting off its bottom rows; a window nobody is clicking or typing in, such as an idle server host window, no longer takes the size back when it regains focus, where its web view reports recent input. A click or Fit to this window that takes the size leaves the terminal focused, so the first keys you type reach the program. (#348)

A terminal repaints and refits after a font loads late, and one created after the server's settings arrived no longer keeps a stale picture until a panel is resized. (#348)

Every terminal counts an emoji as two columns, as programs such as the Claude CLI assume, so their lines no longer drift. (#353)

Fit to this window now says when the server already holds the size, and a terminal no longer shows a transient size change of a few rows right after you return to it. (#353)

A new terminal tries the WebGL renderer again after an earlier terminal fell back to the standard one. (#353)

A client uses the typed-last size hand-over only with a server that says it has it, so a client and a server of different versions keep working. (#358)

Claude AI Terminals keep status hooks on Claude Code up to 2.1.323.

A file restore in a checkout that other chats share is refused while one of them is writing, warns about their changes before restoring, and holds their turns from planning to completion. Rewind conversation only rewinds a chat without touching the working tree. (#279)

A restore can proceed beside a chat on an external OpenCode 2 server you mark Only BiBCode uses this server; BiBCode refuses if it sees that server working. (#326)

BiBCode's Git calls read only a curated set of system Git settings (line endings, symlinks, a recognized Git LFS filter, known credential helpers, TLS settings), so checkpoints run no system hooks, other filters or textconv, LFS files restore and check out with real content, and background fetches never open a credential window. When the system configuration cannot be read or holds an unrecognized LFS setup, checkpoints fall back to inheriting it as before. On Windows, clones and checkpoints use Git-for-Windows-safe null paths. (#283, #264)

On the desktop app, a Git Manager or Source Control fetch, pull or push that needs Git Credential Manager offers a sign-in for the named destination, capped at 10 minutes. Source Control pull and push can be cancelled. (#325)

`bibcode mcp --client <name>` keeps an agent's retries, panels and paired webhook endpoint across restarts. Revoke or Stop ends that identity; an idle named client is listed with Revoke, and Take over sticks to it until Hand back. (#280, #324)

Access-change events are sent under the auth lock, so a revoked client no longer reappears in Settings. (#294)

Opening a file uses its own tab and keeps the Files tab with its open folders and selection. Folder crumbs are clickable, and Show in Files reveals the file. (#288, #323)

The pipeline list has an aligned header, resizable and hideable columns and a "+N" stage overflow; widths are remembered per repository. The pipeline page's stages fill the panel, can wrap, open a job's log beside them, and GitLab pipelines that use `needs` can group jobs by dependency. (#285, #286, #321, #322)

The list's Status column shows "Passed with warnings" in full, and opening a job in the narrow, stacked layout brings its log into view. (#334)

Pipelines and Pull requests load for a self-hosted GitLab or GitHub Enterprise on a non-default web port, and SSH remotes to such a host match it by name. (#332)

Claude AI Terminals keep status hooks on Claude Code up to 2.1.319.

`bibcode storage restore --resume` checks each staged file's size and SHA-256 before finishing an interrupted restore. The recovery journal is now version 3; a version-2 restore journal is refused with a documented manual recovery. (#289)

A desktop stop no longer waits for an outside agent's in-flight MCP `wait_for_thread`. (Refs #303)

Server startup runs provider and tool version probes concurrently. (#318)

The README shows light and dark screenshots, a feature overview and the bibcode.dev link; CI checks Markdown links. (#291, #320)

The macOS crash smoke logs its build time; the CI guide describes its settings. (#295)

Load-sensitive queue, client-runtime, desktop, job log parse and Windows server tests no longer depend on machine speed, and Cursor and Grok oversized-output recovery is covered. (#263, #264, #316, #319, #327, #328, #329)

Native Git watcher tests no longer fail when macOS reports fixture setup changes late under heavy load. (#330)

Diff tool, MCP interrupt and terminal observer tests no longer fail under CPU load: they wait for the fake tool's own output, count only interrupt events, and keep a held test join off the shared reaper. (#333)

Server tests no longer depend on how fast a loaded Mac first runs a new executable: Cursor fixture tests reuse a binary that has already run, the startup probe test runs its scripts once first, isolated test cases are timed from their first output and fail instead of hanging when a child outlives SIGKILL, and the clone retention test answers for Git. (#335)

A web link-notice test loads its modules outside the test timer. (#336)

Desktop tests reserve their ports across test processes, so the exposure-restart test no longer loses its port to a parallel test. (#338)

CI runs a Secrets job: gitleaks scans every commit a pull request or push adds, merge resolutions and merged branches included, and a hash-based guard checks files and commit messages for private values. Test fixtures and plan docs use placeholder hosts and names. (#331)

`scripts/gitlab-local-test/` starts a throwaway GitLab CE with a runner in Docker for testing pipeline screens without a real GitLab server.

The divider between a split chat and terminal is easier to grab, follows dragging smoothly, and keeps chat content within its pane. (#284)

Compare mode's file list can be resized to read long file names. (#306)

A turn's changed-files tree starts collapsed. (#311)

Codex no longer requests the MCP catalogue that can exceed its chat transport limit on new or resumed threads. Oversized stdout failures during launch stop automatic retries and preserve Retry/Dismiss recovery. MCP status now reflects startup notifications, so servers without notifications may be absent. (#316)

The Codex skill picker includes skills installed through plugins, including Superpowers. (#298)

Codex stderr logs no longer appear as raw Codex warning rows with ANSI escapes and incorrect severity. (#299)

The Claude model picker shows model names rather than taglines with Claude Code 2.1.318. (#300)

Orphan worktree directory findings identify each directory separately and retain path evidence outside the home directory. (#309)

The `profiler.finding` webhook sends notifications for new findings, reopenings, and severity changes; unchanged recurrences remain available through catch-up. (#310)

Android device previews distinguish an installed SDK missing its emulator from a missing SDK and show the appropriate installation advice. (#312)

The Unix PTY setup-failure test waits for a complete descendant PID before checking process-group cleanup. The native macOS arm64 CI build has a four-hour job budget, matching x64. (#314)

Changed files coverage now clicks View diff through the chat and verifies that the selected diff stays open through same-turn plan updates. (#275)

The packaged resume-at-end check follows the active timeline through turn completion, avoiding stale scrollers and replies from history. (#215)

The desktop no longer loses its local server at launch. A host with a live Another device pairing restarts its server to switch remote access on. In v0.15.0 that server could take just over the 5 seconds the restart allowed to stop, and the desktop then stayed open with no server, showing cached data and "Local is not connected". Remote access read as switched off and paired clients looked lost, though their pairings were intact. The restart now waits up to 30 seconds, and a stop that still times out is reported as an error instead of being treated as a verified local-only state.

Outside agents can authenticate webhooks (bearer token, projectId, per-endpoint status filters), keep one identity across runs, and act from the CLI with `bibcode thread ...` and `bibcode mcp call/tools`. (#271)

Codex chat works again when BiBCode's MCP is registered and enabled. The `mcp_servers.bibcode` collision no longer breaks it. (#273)

The MCP Files tools write through handle-bound file changes on Windows. (#216)

MCP agents can clone over SSH, pinned to the checked public address. (#217)

MCP `preview_*` tools declare real, compact argument schemas. (#220)

A lost `/oauth/token` response no longer leaves an unrevoked mcp-client session. The relay publishes a pending link record and revokes unconfirmed credentials. (#281)

Side chats (`:btw`, `:side` and the + menu) start with the thread's context, delete themselves when closed unused, and can bring an answer back to the host draft. (#265)

Scrolling up through very long replies no longer loops the list into React's maximum update depth. (#228)

"Open in BiBCode browser" on a chat link opens it in the in-app browser. (#210)

Threads open with a byte-budgeted history window and page older history on scroll. (#226)

Cached threads resume as unchanged after a cold start, checkpoint file lists are capped, and HTTP assets are compressed. (#227)

The shell stream sends only the threads that changed, instead of the full list every 500 ms. (#223)

The Git Changes diff has resizable panes and next and previous difference navigation across files. (#211)

Git discard reports a stranded staged entry as `kept_in_staging`. (#218)

Commit-message drafts typed in two tabs no longer overwrite each other. (#219)

The thread's pull request refreshes right after an agent runs `gh pr create` or `glab mr create`. (#221)

Images, SVG, PDF and audio preview through the capped asset route, and timeline images load lazily. (#224)

On Windows, BiBCode's Git reads the system `core.autocrlf`, `core.eol` and `core.safecrlf`, and nothing else from the system configuration. (#282)

A failed write of the error status keeps the thread. (#234)

A turn captured with a missing baseline is handled. (#235)

Leftover refs from two Git failures on one turn number are fenced from later diffs. (#236)

The first turn's delivery waits for its ref-0 baseline capture. (#261)

Storage reports database size and free space, new stores use incremental auto-vacuum, and the offline `bibcode storage compact` command compacts a store. (#230)

`bibcode storage compact` also handles stores whose pre-compact backup takes longer than 30 seconds. (#262)

Load bytes and time are measured on a 3G profile and gated by a CI byte budget. (#225)

Idle terminals stop scanning the host process table every second. (#232)

Recovery after a memory dip no longer reads as growth in small processes in the memory leak check. (#272)

Terminal file links match Windows backslash relative paths and case- or slash-variant home folders. (#231)

The Cursor skill scan is bounded and keeps a partial list on timeout. (#229)

Update notices cover Claude Code and CodeGraph, as they already did for Codex. (#212)

Remote install no longer falls back to a desktop bootstrap token that the restart revokes. (#233)

The seeded-upgrade lane on macOS arm64 sees the pre-update backup. (#238)

The three seeded-upgrade builds share one Cargo target, which cut the macOS x64 lane from 185 to 122 minutes. (#239)

Three server tests that failed under heavy local load are hardened. (#237)

A lint rule bans em dashes in interface text. A lone dash placeholder is allowed. (#222)

The fix for "View diff" staying closed over a task panel that opened automatically has shipped, and the issue stays open until the reporter confirms. (#275)

Test hardening for load-sensitive tests and for tests that fail only on a Windows development machine is partial. (#263, #264)

Some checks have no native evidence yet: the Windows WSL seeded-upgrade lane was skipped, and the Unix-only permission checks for the Git configuration change (#282) run only on CI.

Open follow-ups: checkpoint and bootstrap Git policy (#283), backup resume content check (#289), and access-event ordering in Settings (#294).

The macOS reconnect footprint still needs heap evidence. (#134)

Claude Code, Codex, Cursor, OpenCode and other MCP clients can start and steer threads, answer questions and approvals, read turn diffs and revert, manage worktrees, branch, commit, push and pull, create, edit and merge pull requests on GitHub and GitLab, read and write project files, open terminals, drive the browser and device previews, open chat panels, and read diagnostics. (#139)

Settings → Agents → Agent integrations has Connect an agent, which adds BiBCode to Claude Code, Codex, Cursor or OpenCode in one click and removes it again. "Agents may" sets what agents can do: read only, approval required, or operate. (#139)

Work done by an agent is labeled "Agent · MCP" in the chat, the sidebar and the status bar. Take over pauses an agent's changes, Hand back returns control, and Stop ends its access. An agent's request to show a file waits until you click Show. (#139)

Remote agents can connect over HTTPS with OAuth. Each new client shows a consent code that you approve under Requests to connect, or with `bibcode mcp authorize`. Access lasts 30 days and can be revoked. (#139)

Outbound webhooks send signed thread, turn and approval events to an HTTPS address, with retries and a delivery history. (#139)

Agents can clone public HTTPS repositories. Internal hosts and SSH URLs are refused, and hooks never run. The Files tools never read or change `.git`, and refuse to change files on Windows for now. (#139)

`docs/reference/mcp.md` and `docs/reference/webhooks.md` describe every tool, argument and error, so an agent can work from the docs alone. (#139)

Every turn that ends in a Git checkout records a checkpoint again, so the Diff panel's turn list, turn diffs and revert have data. A queued message waits until the previous turn's checkpoint is saved, and a turn whose checkpoint could not be saved can't be diffed or reverted to. Turns from before this release start recording from their thread's next turn. (#139)

A scroll key pressed during the sent-row glide pages as asked, and no longer jumps the reading line. (#207, #214)

A finished reply no longer drops for a frame when its work log turns into "Worked for". (#208)

Clone from URL in a Linux AppImage no longer loads the bundled libraries into the system Git when `APPDIR` doesn't match the running AppDir. (#209)

The live Codex terminal Activity dock shows on macOS x64. (#192)

Claude Terminal status hooks now cover Claude Code 2.1.220 through 2.1.314.

Discarding to the trash on macOS no longer needs Finder automation and gives up after 10 seconds.

The MCP Files tools refuse to change files on Windows until handle-bound writes land (#216). Agent clones over SSH are refused (#217).

The macOS reconnect footprint still needs heap evidence. (#134)

The sidebar Inbox groups agents into All Agents, Needs Attention, Working, and Done. Open a row to return to its exact chat or terminal. (#186)

Agent status distinguishes active work, questions, failed work, and a provider that has stopped reporting. Open subagents close as Interrupted when their BiBCode-owned provider process ends. (#187, #206)

Activity opens as a collapsible card in its chat or AI Terminal. Each pane keeps its own open state and section. (#188)

Create Worktree and Add Project use the Default Agent selected in Settings for the target environment. (#185)

Text typed while a new chat starts or an attachment waits for authorization stays in the composer. A failed first send restores the draft in the thread. (#189)

The composer stays editable during a disconnect. Send and other actions explain why they cannot run, and a reconnect does not send saved text by itself. (#199)

Keyboard scrolling stops live following. A new sent message lands at its intended offset, and a growing reply or Activity card keeps the right reading position. (#190, #191, #193)

Sidebar subscriptions retain less thread data across reconnects, and long-lived chat handlers no longer hold old renders. (#198, #204)

Diagnostics downloads logs from the selected connected environment. A download opened from a thread uses that thread's environment. (#194, #201)

The CLI can request a remote diagnostics bundle through an in-app approval, or pair a diagnostics-only credential for unattended downloads while the app is closed. (#201, #202)

A v0.13.0 server skips an authorization row with an unknown future scope, warns, and refuses that credential. Before rolling back to v0.12.0 or earlier, revoke diagnostics clients in Share this host or wait for them to expire. (#202)

Claude status checks use the executable and environment that the terminal will launch, including supported mise shims. A failed probe no longer leaves subagents looking active. (#195, #196)

Each provider controls its terminal preparation time. Claude has a bounded preparation period before it starts without status observation. (#200)

Claude AI Terminal status hooks cover the proven Claude Code 2.1.220 through 2.1.312 builds. Newer builds show Status unavailable until a release proves their hooks safe. (#203)

Silent Codex terminal observer exits now log their stage and elapsed time without prompt or terminal content. The macOS x64 terminal Activity check remains open for native confirmation. (#192)

The macOS reconnect footprint still needs heap evidence to distinguish a leak from retained allocator memory. (#134)

The trigger behind the reported remote-server subagent case was not captured; process-end closure is covered by tests, but that exact remote incident remains unconfirmed. (#206)

A new Pipelines module lists a repository's GitLab pipelines or GitHub Actions runs, with filters for status, branch or tag and, on GitHub, workflow. Open it from the Pipelines button next to Git Manager and Pull Requests, or from the repository row in the Repositories view.

A pipeline's page shows its status, commit, branch and times, with its stages and jobs side by side on a wide panel and stacked on a narrow one. A job's page shows its log with colors, timestamps, collapsible sections and search, and a 100,000-line log stays responsive.

Retry, Cancel and Run work for pipelines and jobs on both hosts. A merge request's Pipelines tab and merge box open a job or its pipeline in Pipelines, with a link to the host beside it.

GitLab pipelines and running job logs update live. GitHub runs refresh while the page is open; a running GitHub job shows its steps, with its log on GitHub until the job finishes.

A pipeline you can no longer view says so instead of showing an old copy.

Settings → Source Control → Pipelines turns the module off.

A GitLab merge request's merge box and Pipelines tab show the pipeline it waits on as it runs: its status, commit, branch and a strip of stages. A pipeline that ran before the latest push is marked "Older commit". (#156)

The merge box names the real reason a GitLab merge is blocked, instead of "GitLab is still computing mergeability". Under "Pipelines must succeed" it says when no pipeline is visible, when one waits for a manual job, or when it was skipped or canceled. (#156)

Disable auto-merge on GitLab now fails when GitLab refuses it, instead of reporting success, and uses the newer endpoint on GitLab 19.5 and later. (#156)

The Changes tab's file list can be resized by dragging its divider or with the arrow keys, so long paths are easier to tell apart. Double-click resets it. (#153)

In the Repositories view, the Pull Requests and Pipelines buttons sit on the repository row instead of on each environment row inside it. With several environments, BiBCode asks which one to read from. The Environments view keeps them on each row.

Row action icons are always visible instead of appearing on hover. A chat row's Archive still appears on hover.

When a conversation fills the context window, BiBCode compacts it and sends your message again, so you no longer compact and resend by hand. A message that would start close to Claude's own compaction point is sent after a compaction. While a compaction runs, new messages wait in the queue and Stop is offered. (#160)

A large tool result, such as a command that printed megabytes, is kept as a 16 KiB preview in the chat instead of being sent to every client that opens the thread. The full result stays in Claude's own transcript. (#148)

Codex retries show as warnings while they happen, a compaction shows as a step in the turn, and `/compact` compacts the conversation. A full context window now offers Compact conversation and recovers the same way as Claude. (#163)

OpenCode 2 chats have a context meter, `/compact`, a compaction step in the turn, and a warning when OpenCode retries an upstream error. (#164)

Claude thinking and Codex reasoning summaries show as collapsed "Thought" rows among the tool calls, "Thinking" while they stream. Click one to read the full trace. The working row shows the latest thought, and Claude's thinking no longer shows as a second answer or leaves a turn reading "(empty response)". (#173)

Mermaid diagrams in replies, plans and rendered Markdown files are drawn once their fence is closed. Show source switches back to the source, Copy copies the fenced source, and drawing a diagram no longer moves the line you are reading. Links and images in diagrams are not drawn. (#171)

Find in thread (Cmd+F or Ctrl+F in a chat, or from the command palette) searches a chat's messages, plans and tool commands, including folded turns and rows scrolled out of view, and opens what hides each match. (#175)

History in the composer lists the thread's closed chats and the Claude Code sessions started in a terminal in the same folder. Continue picks one up in a chat panel. A session still open in a terminal is continued in a copy, so two programs never write one conversation. (#141)

Settings → General → Verbose chat keeps finished turns and tool calls open. Turns and tool groups can still be folded, and your choice stays when a row scrolls away. Tool rows show their time on hover. (#142)

The minimap has Previous turn and Next turn buttons, and PageUp and PageDown in the composer scroll the chat when the draft has no use for them. (#176)

The `/` menu opens for a `/` typed mid-prompt, not only at the start of a line. Escape closes the `/`, `@`, `$` and `:` menus for the word being typed. (#152)

The Activity button opens the Activity panel in one click, on the section that needs attention. Always show Activity (on by default) keeps the button on a chat before any activity, and the panel has Subagents and Background tasks tabs when both are running. (#143)

Streaming replies with code are much lighter: a 15,600-character reply took 2.3 ms per update instead of 16.9 ms, and blocks keep their state, such as line wrap, while text arrives. Ported from upstream PRs 11193, 11196 and 11198. (#172)

A Compare view shows one file's previous and current versions side by side in full, beside a list of the changed files with name and status filters. Changes only shows changed lines with the context you choose, F7 and Shift+F7 move between changes, and a narrow panel shows the files as a picker. (#140)

Open with opens a file, or the whole change, in a diff app Git knows, such as Beyond Compare, Meld or WinMerge. The app opens on the server's computer and stays open when BiBCode quits. (#140)

The panel remembers Stacked or Split, and an unsent comment survives switching between Changes and Compare. (#140)

A turn's changes show again; every turn read "No net changes". (#140)

An open file that changes on disk, for example when an agent edits it, now reloads in place if you have no unsaved edits, and Undo brings back the old text. With unsaved edits, a bar offers Reload from disk or Overwrite disk, and no save writes over the newer file. Before, the next save overwrote the agent's work. (#180)

A file deleted on disk shows "Deleted on disk", and a background tab with a conflict shows a dot.

A failed Source Control action is titled by its step, such as "Push failed" or "Commit failed", and shows Git's reason, instead of "failed during execution". The reason stays when the connection drops right after the failure. (#174)

The dialog that commits, pushes and creates a pull or merge request names a failed branch or commit step, such as a rejecting pre-commit hook, instead of blaming the request. (#174)

In Create Worktree, picking a branch fills the field and closes the list, a branch whose name is a number is created from that branch, and reopening the dialog for another project clears the field. (#151)

New terminals no longer inherit tmux, screen or Zellij variables from the server, and fish 4.1 and later no longer waits at startup for a terminal reply. (#149)

Reopening a terminal whose shell exited no longer leaves mouse tracking or bracketed paste on, which typed escape codes into the next shell. (#150)

Up to four devices can run at once in an environment, in any mix of Android and iOS. Each thread shows its own device, the picker says which thread started each one, and deleting a thread stops its devices. Agents act only on their own thread's devices. (#170)

Refresh devices finds a device created in Android Studio or Xcode without restarting BiBCode. It shows only on servers that support it. (#169)

Settings → Providers → Update all updates outdated providers on every connected environment, then installs a remote server's update where its host offers one. Every skipped environment is listed with its reason. (#147)

This version adds store migrations 55 and 56 for Thinking rows and compaction. They are one-way: once v0.12.0 has run, an older BiBCode cannot open the store. (#160, #173)

OpenCode conversations do not compact automatically, and the thread error does not offer Compact conversation for them; type `/compact` in an OpenCode 2 chat instead.

GitHub pipelines refresh on a timer rather than live, and a running GitHub job's log is shown only on GitHub.

Find in thread does not search tool output or drawn diagrams.

The desktop moves to Tauri 2.11.6. Tauri 2.11.5 and earlier let any WebView read IPC channel responses meant for another WebView (GHSA-w28w-mhc8-qvjv, High).

The TLS stack used for outbound HTTPS is updated (rustls 0.23.46, rustls-webpki 0.103.16, webpki-root-certs 1.0.10), which drops a distrusted root and fixes the rustls advisories RUSTSEC-2026-0285, -0346, -0348 and -0349. The server's ZIP handling moves to zip 9 for RUSTSEC-2026-0367, -0368 and -0369.

Development and CI run on Node.js 26.12.1, a security release, and the CI setup action moves to setup-vp 1.21.2, which fixes a command injection. `pnpm audit` now reports no critical advisories (it reported 3) and 55 in total (it reported 163); the rest are pinned by upstream packages.

When a conversation fills Claude's context window, the chat now says so, keeps Claude's own explanation, and offers Compact conversation. Before, the turn failed as "Claude turn failed (blocking_limit)". (#160)

A failed Claude turn now shows Claude's own error text, a running compaction shows as a step in the turn, and the context meter shows when Claude will compact automatically. (#161)

`/compact` no longer stays "Delivery uncertain" and blocks every later message. (#166)

When a background task finished during a turn, Claude's answer to it was cut off by idle suspension. It now gets its own turn and runs to the end. (#165)

A tool call whose input streams in many pieces is stored once, with its complete input, instead of once per piece; threads with many tool calls stop growing the webview. Threads saved by earlier versions keep their extra rows. (#167)

Codex turn errors are classified again: an authorization failure, a rejected request and an HTTP failure each show their own cause instead of a generic provider error. (#162)

Push on a branch that tracks a differently named remote branch, such as one made from `origin/develop`, now publishes a branch of the same name and tracks it, instead of failing. A configured `push.default` other than `simple` is still respected. (#157)

A failed push now shows what Git said. (#157)

The opt-in Profiler records failed commits, pushes and pull requests, and raises a finding when the same step keeps failing in one worktree. (#158)

When a turn ends on a short status line, the "Worked for…" fold keeps the agent's answer above it visible. (#154)

Clicking outside a dialog no longer closes it and discards what you typed, for example in Create merge request. Close it with Cancel, × or Escape. (#155)

Keyboard focus no longer jumps into the composer when a chat finishes loading its provider's skills or agents, so tabbing through a newly opened chat stays where you are. Tabbing back into the composer puts the caret where you left it.

An open folder, file, save or confirmation dialog no longer holds up the desktop app. Each open dialog used to tie up some of the app's background work. On a machine with few cores, two of them could stop the window from loading again after a reload. A confirmation box also froze the whole window while it was open.

An edited file no longer shows its original text after you switch the right panel to another tab and back. The edit was saved, but the editor could show the old text.

Ticking a task in the rendered Markdown view no longer discards source edits that were not saved yet. The rendered view now shows those edits too.

On macOS, Resource Manager and the status bar show each process's physical footprint, the figure Activity Monitor shows, instead of its resident size, which overstated memory about 3.5 times. Linux and Windows still show resident memory. (#159)

A window that is hidden or not focused stops polling diagnostics, and the server stops sending local server lists that have not changed. (#168)

Desktop: Tauri 2.11.6. Tauri 2.12 follows in its own release.

Development: Effect 4.0.2 stable, Vite+ 1.1.0 with Vitest 5, TypeScript 7.0.2, pnpm 11.28.5, Rust 1.98.1, and alchemy 2.0.0-beta.81 for the relay.

Automatic compaction before a context-limit stop, and Compact for Codex and OpenCode conversations, are not yet available.

Windows and Linux still report resident memory rather than a footprint figure.

On an iOS simulator, a finger is no longer left held down when a touch release fails twice. The release is retried before the next input. (#130)

Two simulators with the same name and OS can now be told apart in the Device picker by the end of their identifier, and AVDs whose names differ only by `_` are now distinct too. (#131)

When an Android emulator crashes after booting, the server log now keeps the emulator's last error output. (#145)

On a Mac with a saved remote server, the status bar showed "--" for memory and CPU, and no AI usage, because BiBCode selected the remote before the local server finished starting. It now selects this computer, and a selected server that is not connected is named in the status bar. Introduced in v0.7.0.

A long thread keeps far fewer copies of its messages after reconnecting. The Timeline minimap copied every user message in full on each update, and those copies stayed reachable. In a 200-message test, 8 reconnects grew the JS heap by 115 MB before this fix and by 33 MB after it. (#96, #134)

Leave my changes now saves new, untracked files in its stash and switches branches, instead of being blocked. Restoring that stash over a file with the same name keeps the stash and explains why. (#137)

Create Worktree from a branch that is already checked out now creates the branch you named, instead of a numbered copy of the source branch. (#136)

Reverts in two chats that share one checkout now restore in the order you asked for them. (#129)

Refreshing Source Control no longer waits on the hosting service each time: the open pull request lookup is shared and reused for 10 seconds. (#138)

An OpenCode session sends nothing after it reports that it exited.

On macOS, stopping a process that had already exited no longer logs a false cleanup failure. (#133)

Restoring a "Leave my changes" stash needs Git 2.32 or later.

Each reconnect that resends a long thread still keeps part of an extra copy of its messages, so memory still grows across many reconnects. This is tracked as a follow-up.

Device previews moved from Settings → Diagnostics to a new Settings → Mobile emulators page. It lists a Device previews switch for every connected environment, named by environment when there is more than one, and the Device panel's Open settings goes straight to that environment's switch.

Settings → About no longer repeats a View diagnostics link; Diagnostics stays in the Settings sidebar.

A Device panel shows an Android emulator running on the environment's server beside the chat, and you can touch it, type into it, paste into it, rotate it, and use its buttons. Turn it on per environment at Settings → Diagnostics → Device previews; the server needs the Android SDK with at least one virtual device. The screen is H.264 video, end-to-end encrypted on connections that pin the server's key, and falls back to still images, with the reason, where video can't play, such as a browser on plain HTTP. Coding agents can list, open, screenshot and close the same device. (#70)

On a macOS server with Xcode, the same panel runs iOS simulators, next to an Android emulator if you like. The simulator's screen is live video, takes a single touch, keys and text (text a US keyboard can't type is pasted, so iOS may ask to Allow Paste), and rotates. When BiBCode can't use the installed Xcode's simulator interfaces, simulators open view only, as still screenshots without touch, and the panel says why. BiBCode shuts down only the simulators it started. (#70)

Pasting into an Android emulator types the text a character at a time, paced so Android keeps every key; text over 100 characters is refused with a message instead of being cut short.

OpenCode 2 works as a provider: chats (messages, slash commands, permissions, questions and Stop), streamed replies, and the follow-up turns OpenCode starts itself to deliver a background subagent's result, which now show as running.

Subagent activity is tracked for OpenCode 2, and the provider row lists its models (with variants), agents, commands and skills. A slash skill attaches the skill, and a command wins over a skill of the same name.

Revert to this message rewinds OpenCode 2 conversations turn by turn, then restores the files. An interrupted rewind is finished by reverting again, and the session stays open until it is.

OpenCode 2 terminals open with arguments it accepts (it has no `--model`): observed through `--server`/`--session`, or, when they cannot be observed, as `--standalone` with the selected model.

OpenCode 2 update notices and update actions use `@opencode/cli`, Windows npm installs of OpenCode 2 are recognized, and an OpenCode version BiBCode cannot drive (3.x or later) shows an actionable error instead of reading Ready.

Fixed: OpenCode 1.18.32 and 1.19 rejected every message BiBCode sent, because its delivery id was not a `msg_` id. Deliveries now use an id OpenCode accepts.

Fixed: an inherited `OPENCODE_PASSWORD` no longer breaks the OpenCode servers BiBCode starts.

OpenCode messages are never sent twice: before resending, BiBCode checks whether OpenCode already has the message (OpenCode 1 ran the model again on a resent message). A message OpenCode refuses now fails once instead of staying uncertain, and a 408 or 429 answer is retried after its `Retry-After`.

Terminals over slow links echo as you type: on a 250 ms link, typing 40 characters went from about 10.5 s to 4.3 s, because the server no longer waits a round trip per echoed key.

Large server messages on plain connections (SSH and plain remotes) are compressed, as encrypted connections already were; a long thread's first load is about 70% smaller.

Connecting shows the first thread sooner: on a 250 ms link, from about 1.6 s to 1.1 s. The server descriptor is fetched once per connect and read-only subscriptions go out with the settings request.

Reconnecting to a thread that has not changed costs one small message instead of resending the whole thread (6.5 MB for a 200-message thread in testing).

Reconnects no longer add a provider capability fetch each time, keep a copy of the server config, or keep a copy of the Git status.

A standalone `bibcode serve --mode web` page pairs with its own server again, and a pairing link for another server no longer bounces back to `/pair`. A session check that stalls is asked again instead of timing out on every retry.

A message sent, or a queued message released, while Revert to this message runs waits and is sent once the revert finishes. A revert is refused while a session is starting, still settling a turn, or still running background work such as a Claude background task or Codex subagents.

A revert on one thread no longer holds up checkpoint work on other threads while it waits for a delivery or reopens a suspended provider.

Turning Chat Activity off and back on no longer lets an idle Codex or OpenCode session be stopped before its running subagents are found again.

A provider whose executable is missing fails the message once, with what to do, instead of retrying every second; other launch failures back off up to 30 s, and identical retries no longer update the thread.

Dismissing an uncertain OpenCode message keeps the queue blocked until OpenCode reports the session idle, then releases it; after a restart, a message OpenCode already has releases the queue once the session is idle.

Codex activity recovers long threads from their newest 20 turns through `thread/turns/list` instead of reading the whole history, and only a missing method marks a Codex activity method unsupported. Large or unexpected replies are retried instead of reported unsupported, and a large subagent thread no longer makes the Codex terminal observer reconnect. (#120)

Source Control stays responsive with thousands of changes: the change sections and the Merge Changes list render only the rows in view. (#119)

The Files tree opens as quickly as before while reading the file list once instead of twice. Workspaces past 25,000 entries notice outside changes in subfolders again, and build their index about 30 times faster.

After a checkout, the chat header writes the thread's new branch once instead of several times. The left panel keeps a card's PR badge and uncommitted-changes dot when a pull request lookup fails, and the Agents view shows each checkout's current branch.

On Linux, Git status keeps following a directory after it is renamed (`git mv`, or a rename in an editor or file manager). (#97)

After the local server restarts, the desktop keeps the new server address even when an older topology read finishes or fails afterwards. (#109)

A provider terminal past the observer limit keeps working unobserved instead of breaking, and the refusal is logged; closing such an OpenCode terminal no longer deletes the session you worked in. The limit is now 64 observers across the app.

The profiler no longer reports a provider process BiBCode stopped itself as a crash when the report runs late.

Server tests that capture logs, start terminal observers, or depend on the profiler setting run in a process of their own, and the worktree lifecycle test reads every event of a combined update; several tests that failed under load no longer do.

On an iOS simulator, a touch whose release fails, and whose cleanup then also fails, can leave a finger held down on the simulator.

Two simulators with the same name show as identical rows in the Device picker.

When two chats share one checkout, reverts in both can finish in the order their providers reopen rather than the order you asked, so the earlier revert can overwrite the later one's files.

The Source Control speedup for thousands of changes and the reconnect memory fix were measured on Linux; their macOS measurements are still to be done.

A pull or merge request can open as a tab in a thread's right panel, beside the conversation. Done after creating one from the Source Control panel opens it there, Open MR in panel (Open PR in panel on GitHub) opens the branch's open request, and the full Pull Requests page offers Open beside a thread….

A view of a deleted thread no longer makes the server use several CPU cores after a few hours. Each failed subscription to the thread left a task on the server that received every agent event until the app restarted, and the client retried every 250 ms. A failed subscription now ends with its request, and the client waits longer between retries, up to 30 s. (#113)

Reconnecting to a long thread no longer leaves another full copy of the thread in the app's memory. The app keeps the parts of a resent thread that did not change; in a test with a 200-message thread, six reconnects grew the web view's memory by 20 MB instead of 58 MB. (#96)

The Files panel no longer re-reads the whole file list when a formatter or editor saves files without adding or removing any. A burst of new files costs one read when it ends, or one about every 10 s while it lasts, instead of one every few seconds. (#111)

In the chat panel, Claude background subagents, background shells and Monitor watches are no longer stopped about a minute after the turn ends, and Claude's reply when one of them finishes runs as its own turn. A failed check of Claude's activity flags is retried on the next launch instead of turning off subagent tracking until BiBCode restarts, and each check writes one line to the server log.

An idle chat session is no longer stopped while its provider may still be working: a turn the provider starts itself counts as running, Chat Activity being off no longer lets idle sessions stop running subagents, and Cursor sessions are not stopped while idle. The server log says why a session was suspended.

The BiBCode MCP token is no longer visible on Claude's command line: Claude reads it from a file only your account can open, removed when the session ends. Providers reach BiBCode's MCP server on loopback (`127.0.0.1`) instead of the wildcard address.

OpenCode 2 is reported as not supported yet, in Settings and when you send a message, with the setting to change (point Binary path at an OpenCode 1.x executable), instead of failing later with "HTTP 405" or "error decoding response body". BiBCode now waits for the OpenCode 1.x API to answer before it treats a server as ready.

Revert to this message works again, including a minute or more after a turn: BiBCode reopens the idle session, asks the agent to rewind, and only then restores the files, so a rewind the agent refuses leaves your workspace and conversation as they were. A revert is refused while a turn is running.

Codex rewinds use `thread/revert` and need Codex 0.151.0 or later; an older Codex, or a thread started in Codex's older history format, gets a message saying to update Codex or start a new thread. Codex's answer for a removed method now counts as a missing method, so activity falls back correctly.

Claude, Cursor and Grok cannot rewind their conversation, so for them revert restores the files and says the conversation was not rewound; the confirmation says so before you agree.

After you check out another branch in the Git Manager, the left panel's cards show the new branch even when the repository's pull request lookup fails. They used to go back to the thread's old branch about half a second later.

Removing a worktree thread from BiBCode no longer waits for the removal dialog's Git details to finish loading: those details are read without holding the project's lock. A slow load logs how long each of its steps took. (#114)

The startup crash scan reports only crashes of this BiBCode executable: the same path, or another mount of the same AppImage. An extracted AppImage or another build with the same file name no longer raises a `crash.native` finding. (#110)

Server tests that check log output run in a process of their own, so a test running beside them can no longer switch off the warning they look for. One of them failed a release check. (#112)

On macOS the interface no longer freezes for seconds at a time while the status bar refreshes. Every switch, checkbox and radio button scanned the whole page for its label after each render, which WebKit does by walking the document. Base UI 1.9 skips the scan for labelled controls, and the file checkboxes in the commit dialog now have labels. (#106)

Scrolling up a long conversation no longer holds the interface. A finished message's code blocks show at once and are colored right after, one at a time, instead of all being colored while their rows appear. In a 100-turn test thread, the time the interface stalled while scrolling to the top fell from about 2 s to under 0.7 s. (#103)

The server no longer keeps a full copy of each open thread for every client that shows it. During agent turns that copy grew by about twice the thread's new content, and it was kept for as long as the thread stayed open. (#101)

The process history behind the status bar's resource readout keeps its hour in about 0.5 MB instead of 3 to 15 MB. (#100)

The desktop reads the local server's connection details from memory instead of asking the app on every check, which slowed the web view's memory growth on Linux. (#96)

A program printing many short lines quickly, such as a build or an agent's output, no longer loses lines in the terminal. The server publishes the output waiting together instead of one read at a time. A client that still falls behind gets the terminal's full state instead of a gap, and keeps the input it has not sent yet.

In the Git manager's History tab, a page of older commits that fails to load no longer re-requests itself in a loop. It shows its error, and loads again when you scroll back to the end of the list or choose Refresh.

The file editor's Saved notice no longer stays up after you open another file right after saving.

On the Linux desktop, a remote environment's development server opens at its real address (`http://localhost:5173`, a wildcard address such as `http://0.0.0.0:5173`, HTTPS included) instead of a gateway address, through a tunnel on the environment's own connection. Only the account signed in on this computer can use the tunnel. (#69)

Shutting down or signing out of Windows with BiBCode open no longer crashes it with "cannot move state from Destroyed". It exits, and the next start reports no crash. (#102)

BiBCode 0.7.x on Windows closes when you choose Install for an update. Download the latest installer and run it; your projects and settings are kept. 0.8.0 and later update themselves. (#95)

Events, findings and status name the BiBCode version that recorded them (`bibcode`, `firstVersion`, `lastVersion`, `version`). A `session.start` event records the host, OS and architecture, and client batches carry the client's own version. (#98)

On macOS, `client.stall` no longer counts the timer slowdown of a covered or background window, or the catch-up right after waking. (#99)

A previous run that ended without a crash record names how it ended when it recorded that: a lost display on Linux, a quit, a signal, or Windows ending the session. On Linux the finding adds systemd's own lines about the run's unit. (#87, #102)

On macOS the Profiler samples the WebKit process that runs the interface, so its CPU and memory can raise findings. (#104)

`worktree.orphan-dir` no longer reports hidden folders other tools create in a managed worktree directory, such as Orca's `.orca-worktree-trash`. (#105)

`server.getProviderCapabilities` waiting on a provider check right after start no longer raises `rpc.slow`. (#107)

On Linux, an AppImage run as a systemd service stops its crash monitor before it exits. The service's stop took the AppImage's files away while the monitor still ran, which ended it with `SIGBUS` and raised a false `crash.native` after each update. An update run by v0.9.2 or earlier can still leave one.

An open thread receives only what changed after each event instead of the whole thread, which reached 6 to 10 MB on long threads, and thread and sidebar updates are batched (100 ms and 500 ms). Terminal typing and other replies no longer wait seconds behind those snapshots on a slow link. (#89)

Server replies of 16 KiB or more are compressed before encryption when the client supports it. `BIBCODE_REMOTE_COMPRESSION=0` in the server's environment turns this off. (#89)

The Profiler records, every five minutes, how many bytes each method sent to remote clients (`rpc.bytes`). (#89)

The Pull Requests panel paints the list and an open pull request or merge request from stored copies, then refreshes them, for GitHub and GitLab. GitLab commands no longer wait about a second each for `glab`'s telemetry request. (#90)

Approving a GitLab merge request reads its permissions in one wave, and a failed pull request action logs its error code. (#90)

After Create, the Create PR/MR dialog shows only Done.

On Linux, the Git watcher no longer watches directories Git ignores, such as `node_modules`, `target`, and agent worktrees inside a checkout: one affected checkout went from about 312,000 watched directories to about 2,400. After a kernel queue overflow, full re-registrations are spaced out (30 s, doubling to 30 min) instead of looping at full CPU. (#88)

Hide on discovered worktrees works again after the worktree catalog refreshes, and a view that subscribes to the branch summary while it is already running gets the current branch at once.

When Claude reports a result before reading a newly sent message, which happened after an idle thread resumed, that result no longer ends the new message's turn. The thread stays Running while Claude works, and the next message waits in the queue instead of showing "Delivery uncertain". A message Claude reads after its 60-second confirmation wait is marked delivered. (#93)

The composer's skills and commands come from a cache refreshed in the background instead of starting the provider's CLI every time, which took about a second for Claude.

A client connected through BiBCode Connect opens a development server on the server's `localhost` in the BiBCode browser at its own `https://` preview hostname. Each Connect endpoint gets four preview hostnames, and the primary client re-links once to add them to an older link. (#68)

The Connect tunnel comes back by itself after a server restart, and linking no longer fails with "Invalid managed endpoint origin." on every real client.

On Linux, when BiBCode runs as a systemd service (for example started with `systemd-run --user`), an update relaunches the new version in its own scope, so stopping the old service no longer kills it. (#94)

The Profiler reports crashes of BiBCode processes that no profiler session covered, such as an app relaunched by an update, from systemd-coredump. (#94)

The packaged upgrade checks can start from any stable release, and on Windows they require the updated app to come back with a window. (#95)

While an agent runs, the desktop no longer reloads every thread's full history in a loop to refresh the archived thread list. The list is refetched only when a thread is created, archived, unarchived, deleted, or closed as a panel, and the Settings archived list and the Reopen closed chat menu refresh when they open. Shell and thread snapshots read only the rows they return, so reconnecting and opening a thread take milliseconds instead of seconds on large stores, and they no longer write temporary files to disk. (#78)

On Linux, BiBCode returns freed memory to the system every 30 seconds instead of keeping several gigabytes after large loads. (#79)

Process diagnostics in the status bar and Diagnostics answer from a sample taken in the background instead of sampling every process while you wait, and sampling skips per-thread data it never used. (#80)

A remote client whose window was suspended, such as a backgrounded macOS app, no longer drops its connection when it wakes, and the server keeps answering connection checks while a request waits for the database. The Profiler records connection ends and reconnects as `rpc.disconnect` and `rpc.reconnect`. (#81)

Typing in a terminal no longer queries the database on every keystroke, and a change of the thread's workspace, such as the worktree created by a thread's first message, no longer interrupts terminal input. (#82)

Process cleanup no longer reports a process group that had already exited as a failure, and never signals a process that was already reaped. (#83)

The server no longer panics when a connection closes while a request is still finishing. (#84)

Inside the Linux AppImage, Git commands and review diffs start without copying the app's memory, so branch lists, status refreshes, and review diffs stay fast while the app holds several gigabytes. (#85)

Settings → General → Open links in chooses BiBCode browser or System browser. The new `browserLinkTarget` default is `app`, so a clicked link opens in the in-app browser. The row is shown only where that browser exists.

Chat links, chat file chips, terminal URLs, OSC 8 hyperlinks, terminal `.html`, `.htm`, and `.pdf` paths, preview popups, and agent `preview_open` share one router. In chat, a modifier-click or middle-click opens the other target. In the terminal, Ctrl/Cmd+Shift-click does.

A server-loopback URL (`localhost`, `127.0.0.0/8`, `0.0.0.0`, `[::]`, `*.localhost`) is resolved for the thread's environment. On the same host it opens unchanged. For a LAN, tailnet, WSL, or host name it is rewritten onto the server's address. A public IP, or a server this client cannot reach, shows a notice with Copy link instead of opening the wrong machine. A development server on the server's own localhost uses the preview gateway below, including over SSH.

Network and device paths (`\\server`, `//server`, `\\?\`, `\\.\`) and `file://` URLs with a host are refused from the terminal. An OSC 8 link whose visible text does not match its destination asks for confirmation. Chat links to network or device paths never become file links.

On the desktop, preview popups become new preview tabs in the same thread, and the opener plugin's click capture is off. Agent-written HTML, XHTML, SVG, and `*+xml` assets are served with a sandbox content security policy. Discovered ports are attributed to the terminal that started them.

A development server on the server's `localhost` opens in the BiBCode browser from a desktop over SSH, a browser on the LAN or tailnet, and WSL. Shared preview state keeps the canonical `http://localhost:<port>` URL, and each client loads the address it can reach.

The gateway binds the address the caller used to reach the server and refuses public and proxied callers with `not-reachable`. Access uses a 60-second single-use capability URL. An HttpOnly cookie is set on a bootstrap page, then the target path replaces it. BiBCode Connect (relay) environments still get the unreachable notice. HTTPS development servers are not proxied.

Provider sessions and every terminal receive `BROWSER=bibcode-open-url`. `bibcode open-url <url>` posts to the server, and the client showing the thread opens it. If no client is listening, the helper prints the URL. On Windows the helper is a `bibcode-open-url.exe` alias.

A typed server refusal (HTTPS, a non-loopback URL, or nothing listening) is shared. A failure of this client's own reach stays on that client and shows an overlay with Reload.

Over SSH, a preview tab keeps the development server's real origin (`http://localhost:<port>`) when that port is free on this computer, so OAuth redirects and CORS allowlists work as on the server. When it is busy, the preview uses a random `127.0.0.1` port and a note names the busy port once. Each environment's previews keep their own cookies and storage. The system browser always opens SSH previews on `127.0.0.1`, since it has no per-environment storage.

In browser mode, previews open in the page instead of a new tab, framed through the gateway. Removing an environment deletes its preview profile unless one of its previews was opened this session.

Settings → About → Diagnostics → Profiler, off by default. While it is on, BiBCode records to local files under its data directory and lists findings in Diagnostics. Each environment has its own switch, and clients send their measurements to the server they are connected to.

Crashes: a crash of the app or server is recorded with where it crashed. A minidump is written by the same executable relaunched as a crash monitor, and the operating system's own crash record is used too (systemd-coredump or the journal, Windows Error Reporting, macOS crash reports). Panics, webview crashes, provider and helper process crashes, and exits that did not finish shutting down are recorded as well.

Memory leaks and sustained CPU in BiBCode's own processes, slow and hung requests with the time split between server, network, and rendering, interface stalls and slow interactions, and failed or incomplete worktree removals.

`bibcode profiler status | findings | events | crashes | symbolicate` reads the data, Diagnostics exports it, optionally with crash dumps, and `bibcode profiler mcp` serves the same read-only data to an AI harness. The `bibcode-profiler` repository skill in `docs/skills/` monitors the profiler, investigates findings, and drafts GitHub issues after checking for duplicates.

Nothing from prompts, messages, or terminals is recorded, and minidumps never leave the machine unless they are exported. A client paired with an older server shows that its profiler is not available there instead of failing the connection.

A Windows update relaunched by an elevated installer returns on the same data root and port, so remote clients reconnect to the same address. A detached waiter starts the app if the installer exits without relaunching it, and it is stopped when the installer fails to start. The handoff is deleted once the new version is running, so a later ordinary launch keeps its own defaults.

The installer's preinstall hook, which ends a running BiBCode and retries replacing it, now runs only for passive and silent installs. An interactive install keeps the standard prompt.

Remote access on a non-English Windows no longer fails when `netsh` reports a missing firewall rule in another language.

An AI terminal or chat panel opened in one client appears, with its existing work, in every client connected to the same server. Closing one closes it everywhere. A tab adopted from another client does not take focus. A label taken from the command follows the session's current command; a custom label stays.

Closing a chat panel archives it instead of deleting it, so its history and provider resume state survive. + → Reopen closed chat lists up to 10 of the host's archived panels, newest first, and brings the panel back on every client. The menu shows No closed chats when there are none, and Couldn't load closed chats. Select to retry. when loading fails. Settings → Archived hides panel threads. Deleting a thread also deletes its panel threads.

A provider session stays up while a subagent is still working. Idle suspension no longer shuts the driver down 60 seconds after the turn that launched those subagents. A clean server shutdown saves each session as suspended with its resume cursor, so an ordinary restart or update continues the same provider conversation. Explicit stop, delete, and restart are unchanged.

Import CLI sessions… on the project menu imports Claude Code and Codex CLI sessions whose working directory is the project root, from the last 30 days, at most 200, excluding BiBCode's own conversations. The imported thread shows that history, and the next message resumes the same CLI conversation. A session that is already imported offers Open.

When a provider conversation cannot be resumed, BiBCode starts a new one and sends a bounded summary of this thread. The thread records "Couldn't resume the previous <provider> conversation. Started a new one with a summary of this thread." The composer notice reads "Sent in a new conversation with a summary of earlier messages." The stored message keeps the typed text. A Cursor `session/load` error starts a replacement session only when the provider says that saved session is gone. Any other JSON-RPC error is returned and the saved session id stays in place. OpenCode starts a new session only on a 404. Claude resumes only when its transcript file still exists.

The Git Manager Merge… dialog has an Into picker. Choose another local branch to merge into it without checking it out: your files and checked-out branch stay as they are, a merge that would conflict is refused before anything changes, and a branch checked out in another worktree is blocked. The result is published with a fast-forward-only update, so a target that moved is left unchanged.

The Merge dialog lists remote branches as sources.

Source Control has Merge into current branch…: pick a local or remote branch, Fetch it, and merge it into the checked-out branch. A merge in progress shows Commit merge and Abort, with Ours, Theirs, and Mark resolved for each conflicted file. Commit merge stays disabled until every conflict is resolved, and the control shows "Resolve and stage every conflicted file first."

Source Control and the Git Manager Changes tab no longer lose their file list while a merge has conflicts, and conflicted files appear once.

On Git older than 2.38, the merge preview says which Git version it needs instead of reporting unrelated histories.

GitLab detail and timeline reads that do not depend on each other now run together, and suggestion note bodies on one discussion page run together too. The list was already one wave.

While the document is visible, a GitLab merge request paints from the last stored snapshot and stays current. Hiding the document stops that refresh. Merge, review, comment, and the other actions stay inactive until a live detail succeeds on this visit. A row hovered for 150 ms prefetches detail and timeline, at most two per environment, and a prefetch younger than 5 seconds is shown when the merge request opens.

GitLab Overview shows Approve under the description. It approves the current head and does not post pending inline comments. After approval the same control becomes Revoke approval. Until the live detail succeeds it stays inactive with Loading…. GitHub still approves from the review popover, and GitHub routes stay on demand.

Snapshots live in the environment SQLite database, capped at 32 MiB. Files over 1 MiB are not stored. Logout and authentication or permission failures delete that host's rows. Rescan does not.

Migration 053, `PullRequestSnapshots`, creates `pull_request_snapshots` with host, project, kind, key, fingerprint, payload, observed time, and generation. That table holds the GitLab merge-request snapshots above.

Migration 054, `ProjectionThreadHostThread`, adds a nullable `host_thread_id` column on `projection_threads` when that table exists without the column. A panel thread records its host thread so every client can open it as a tab under that host.

An intentional hermetic-guard abort still ends in `SIGABRT`. It now clears the core limit and, on Linux, the dumpable flag before aborting, so a passing guard test no longer writes a core or raises a desktop crash notification. Release builds without the hermetic feature are unchanged.

The Profiler's native crash checks on Windows and macOS run in CI. Its whole-app overhead was measured only on a headless Linux server; on Windows and macOS only its sampler was timed. On Windows and Linux a preview tab's web content counts as the webview, so a busy or leaking previewed app can raise a webview finding. A stall caused by a browser-mode preview counts as the client's. A Windows update ends a running `profiler mcp` server.

Windows and macOS were built and upgrade-tested only in CI. The native desktop checks for link routing, cross-client panels, the preview gateway, and Source Control merge were not run on them. Validation for those features was on Linux. The Linux preview child-webview geometry check was launched, but the desktop session was locked, so the UI was not driven. Live preview-gateway procedures (SSH preview, the brainstorm companion over SSH, browser-mode cross-site bootstrap, revocation, the cross-port 403, and whether Codex agents receive `BIBCODE_OPEN_URL_AUTH`) were not run. `fetch .` publishing was not exercised on reftable repositories, and a packaged end-to-end walk through Source Control merge was not run.

On desktop, agent `preview_open` always shows the tab (`show: false` is ignored), and a request for a thread that is not on screen times out. Server ports on BiBCode Connect still show the unreachable notice. HTTPS development servers are not proxied. A hostname that resolves to `127.0.1.1` on the same machine is refused as proxied; use `localhost`. A reverse proxy on another LAN host, global IPv6 to a `::`-bound server, and dev Vite over the LAN are refused. The desktop does not report native page-load failures; after a page has loaded, a dropped forward shows the webview's own error page, and Reload recovers.

A visible terminal tab still closes itself when its session reports `closed` or `exited`. A restart that fails while another client is viewing the tab closes it there too. Split arrangement and tab order stay per client. Terminal scrollback is still lost when the server restarts.

Session continuity applies to BiBCode-hosted agent sessions after the desktop app is rebuilt and reinstalled. A provider that keeps emitting no-op events can hold a session until the 30-minute quiet cap, and a projection that fails to apply can leave a subagent marked live until that cap. A prompt that is already being sent when a chat panel closes still starts. A Codex model taken from an imported transcript may be retired. Symlinked workspace paths may list Claude sessions that cannot be resumed.

A reconcile that finds a provider conversation gone can replace the saved cursor while the row stays frozen to the old id, and a later explicit Retry then fails the identity check. A released frozen retry shows both the new-conversation activity and the notice. A crash right after sending can resend the handoff once.

Pipe-pattern core handlers are not asserted to skip a filesystem core. The dumpable clear still applies on Linux. Hermetic report mode and allowed roots are unchanged.

Open-url tokens live 8 hours with no renewal. `delivered` means a subscriber exists, not that the URL was opened. A desktop SSH forward can be shared across threads after an ephemeral port is reused.

Projects (Environments view) and repositories (Repositories view) are now lifted cards on a recessed list background. Inside a repository card each environment checkout sits on its own shaded band, and chats are borderless rows with a clearer fill for the open one. Dark mode separates the layers much more strongly and brightens secondary text on the cards so paths and ages stay readable.

The Repositories view sorts repositories by name by default, so cards keep their place as chats update. Its sort menu offers Sort repositories (Name, Last user message, Created at), separate from the Environments view's project sort.

The Repositories view has an Add project button in its header and empty state. Because that view hides the environment rail, Add Project now shows its Host selector on macOS and Linux desktop whenever saved remote servers exist, so you pick the target environment in the dialog.

Create new project gains Browse… for its parent folder: the native picker on this device, or the selected remote server's directory browser, returning to the form with the project name kept.

New Branch has a From field that searches every local and remote branch; it defaults to the checked-out branch, the current HEAD when detached, or the commit you opened it from in History.

Check out after creating is on by default. Turn it off to only create the branch: the checkout and working tree stay on the branch you were on.

A new branch never tracks its source, so a branch created from `origin/main` publishes under its own name instead of pulling from and pushing to `main`.

Choosing `main`, `master`, or the repository's default branch as the target of a pull or merge request shows a red warning naming the branch. Creation stays available.

Opening a chat panel on a remote server with latency no longer shows an empty tab while the server creates the chat. The panel shows Opening chat… until the chat arrives; a failed creation still closes the panel with an error.

The new panel layout and dialogs were verified in the web client in light and dark themes; native packaged visual validation on macOS, Windows, and Linux has not been run yet.

Native qualification for remote updates (#16), the typography audit (#27), the light/dark screenshot matrix (#29), and the manual SSH check on a real Mac (#38) remain open.

End-to-end-encrypted file transfers (#18) remain deferred.

The create dialog now offers Mark as draft, assignees with Assign to me, reviewers, a milestone, and labels on GitHub and GitLab. GitLab merge requests also get Delete source branch and Squash commits, prefilled from the project's settings; a project that always or never squashes shows the box locked with a note. GitLab takes one assignee and one reviewer, GitHub several.

Pickers search the host as you type. A picker or settings read that fails offers Retry and never blocks creation; untouched merge boxes then leave the decision to the project.

When GitHub creates the pull request but cannot apply an option (for example a reviewer without access on github.com), the request is reported as created with a warning naming what was not applied, and it is never retried. When a request already exists for the branch, the dialog says your chosen options were not applied.

Provider failures show the provider's own message. GitLab request bodies travel in a private temporary file instead of on the command line.

The dialog brings the outcome into view when the request settles. Azure DevOps and Bitbucket keep the plain dialog, and older servers without `pullRequestCreateOptions` show no new fields.

Pasting a screenshot or other clipboard image into a terminal running Codex or Claude Code now attaches it, including on remote, WSL, and SSH environments. The image is uploaded to the terminal's server, saved there, and its path is pasted. A status with Cancel shows during the upload, typed input waits behind the path, and older servers print a message instead of sending an empty paste.

Selections in terminals running Codex, opencode, or other mouse-tracking programs no longer disappear on the next hover or right-click, so keyboard and context-menu copy work. The desktop selection menu gains Copy.

A browser primary behind the loopback UI proxy now discovers and stores its server through the same authenticated HTTP routing it signs in with. The WebSocket endpoint, the desktop-managed bypass, and non-loopback access are unchanged.

Added the `issue-delivery` skill and a CI-checked delivery checker for agent issue batches, and agents now confirm a delegated reviewer is running before waiting on it.

Create options have not yet been exercised against live GitHub and GitLab hosts, and terminal image paste is unverified in the macOS and Linux webviews and with Windows servers.

Native qualification for remote updates (#16), the typography audit (#27), the light/dark screenshot matrix (#29), and the manual SSH check on a real Mac (#38) remain open.

End-to-end-encrypted file transfers (#18) remain deferred.

The left panel has an Environments | Repositories toggle. The Repositories view groups projects from every connected environment under one read-only card per Git repository, with a card per environment that keeps all of the project's normal actions. The environment rail is hidden in this view, and an empty view links back to Environments.

Each card collapses independently and the primary local environment is listed first. The selected view and group expansion are remembered.

The server derives each project's repository identity from its `origin` remote and publishes it with the project. Credentials, query strings, and fragments are stripped from the stored remote URL. Identities are reconciled after project creation or a workspace move, at startup, and on catalog scans, when `.git/config` changes or at most every five minutes otherwise. The work runs off the catalog refresh lock, with bounded Git reads.

Composer drafts stay reachable when a project gains a repository identity.

A Claude message that starts with a slash command or skill (for example `/superpowers:receiving-code-review …`) no longer hangs in Working. The Claude CLI echoes these messages in their expanded command form, which BiBCode now recognizes as the delivery acknowledgement.

A Claude message that is never acknowledged no longer holds its thread forever. After 60 seconds it is marked uncertain, so you can retry or dismiss it, and later messages can go through.

Stop now works when a provider stops responding. If a provider process BiBCode owns has not settled the turn within 10 seconds, BiBCode ends its session, marks the turn interrupted, and keeps the conversation so the next message resumes it in a new process. An OpenCode session on an external server is only asked to abort, since BiBCode can't end that server's work.

Messages queued for a deleted thread are dismissed instead of being retried forever, and server startup no longer retries sessions of deleted threads.

Push + MR and MR now both push first and then open the shared pull/merge-request review dialog. The source defaults to the pushed branch, and remote branches are listed as sources. The dialog asks you to publish when the branch is not on the remote yet.

Ctrl+C copies text selected in AI terminal chats even when the CLI enables mouse tracking. A plain drag selects text, and Shift+drag (Option+drag on macOS) sends the mouse to the CLI.

Collapsing a project now hides its discovered-worktree section and primary card.

Git branch footer labels stay inside their controls. Connection notices give guidance on server availability and network reachability instead of raw fetch errors.

Registered manual dispatch for the visual and remote-UI release qualification workflows. These remain registration-only on `main`.

Native qualification for remote updates (#16), the typography audit (#27), the light/dark screenshot matrix (#29), and the manual SSH check on a real Mac (#38) remain open.

End-to-end-encrypted file transfers (#18) remain deferred.

Large chat attachments use server staging with sequential upload progress, verified completion, and turn-bound attachment ownership. Upload cancellation restores the prompt and attachments; navigation and an uncertain admission preserve the original attempt instead of silently duplicating a send.

Retrying a message after its provider session loses resumable state can start a new conversation and explains that outcome. Intentional session stops have distinct feedback from lost connections.

Provider delivery settlement fences late events and publications after workspace loss, keeping stopped sessions from being projected as running again. The conservative provider idle policy and its recovery after sends without a turn, turn-less sessions, and failed turns are now documented explicitly.

Clone parent folders can be browsed on the selected server. Add Project waits for host platform information and preserves its entered data while metadata loads.

Automatic fetch attaches again when an unavailable Git repository is repaired.

Hosting CLI launch failures retain their category and recovery guidance in request dialogs. Diagnostics distinguish unavailable timing from measured short operations without exposing private launch context.

Git Manager keeps selected rows aligned with the opened diff, preserves selection through unchanged status refreshes, and shares remaining Changes-panel space between its list and diff. Settings uses the height available above the status bar.

Side-by-side image diffs use each image's natural dimensions within the preview pane, avoiding one-pixel thumbnails.

Expanded the readable text-size floor across chat, Git Manager, Settings, sidebar, and other controls. Complete native visual and typography qualification remains tracked below.

Remote-server updates use shared named confirmation from Settings and sidebar, advisory running-work counts, download/protection/restart progress, actionable failure and Retry, and operator instructions for manual hosts. Host notices identify the requester; browser reload prompts preserve unsent input.

Desktop primary HTTP requests share the bridge-owned bearer cache, so backend restart invalidates old credentials; a late failed exchange cannot clear its replacement.

The orchestration HTTP snapshot now uses its declared client read model with full thread details and archived/deleted markers. Shared Rust serializers preserve existing WebSocket output; a populated cross-language fixture guards decoding.

Heartbeat regressions distinguish controlled scheduling cadence from real-connection survival, and Git status overflow retry has cross-language contract coverage.

Native process sampling starts lazily instead of scanning all host processes on every server construction; requested diagnostics and owned-process cleanup retain on-demand discovery.

Automated provider, hosting, Git, SSH, and desktop fixtures isolate user configuration and credentials. The hermetic guard rejects host provider/hosting executable resolution and credential reads; Unix test-child watchdogs reap owned descendants after parent interruption or death.

Desktop shutdown-race tests observe the exact runtime join. SSH fixtures retain explicit cleanup and loopback behavior across native platforms; delayed-interpreter watchdog fixtures establish their intended TERM immunity before interpreter startup.

Packaged composer fixtures advertise the native Claude skill catalog consistently. Queue smoke checks verify visual FIFO independently of temporary virtualized DOM slot order, retaining reload, steering, and exact provider-input checks.

Windows upgrade evidence records a timed-out version probe as unavailable after verified child cleanup, preserving the overall installer deadline and strict installed-version checks.

Release preflight explains workflow-token permission mismatches before native builds. Cold macOS Intel CI and seeded-build budgets account for the complete required jobs, preserving runtime assertions and all supported platform rows. Both macOS release jobs verify Finder's rendered icon from their exact mounted DMG payload before upload.

Intel desktop and server distributions build on supported macOS 15; desktop installers retain the same signature and Finder pixel checks. Native macOS 26 Intel runtime validation remains separate. macOS 15 verification does not establish hosted macOS 26 Intel Finder qualification.

AppImage packaging reports unsupported GdkPixbuf loader layouts with actionable guidance. Native Windows trust-command coverage, living procedures, and issue-specific evidence reports were expanded.

The remote-update feature is integrated (#16); native qualification remains incomplete. The previous-stable Windows qualification did not establish the installed candidate, and observation hardening is separate from an actual installation pass.

The remaining typography audit (#27), complete light/dark screenshot matrix (#29), and required manual SSH check on a real Mac (#38) remain open. Source and hermetic tests do not establish those native scenarios as passed.

End-to-end-encrypted file transfers (#18) remain deferred and are excluded from this release.

The supplementary throttled browser immediate-close profile for legacy whole-request attachment delivery remains unqualified. API-side queue completion does not guarantee receiver delivery; staged uploads require their normal completion/admission flow.

The desktop restart guard retains its documented check-then-exit limitation around an update admitted concurrently with a manual restart.

The Chat AI command menu discovers skills for the active workspace and provider

Switching workspaces or provider configuration cannot display an older

Cursor discovers nested and linked skills across its supported roots. Claude

Configured sensitive environment values reach native provider launch and

Every creation entry point opens the shared review dialog. The target starts

Source and target dropdowns show only fetched branches from origin, including

Selecting another source keeps the current checkout and working files intact.

The server receives the exact reviewed branches, rejects invalid or identical

Combined commit/push/request actions explain their fixed source and reread Git

Older servers that cannot honor source and target choices disable creation

Unix PTY launches preserve Rust's spawn handshake. Failed executable or

Ctrl+C copies selected AI-terminal output and Ctrl+V pastes through the

Files refreshes no longer crash with “Unknown directory child index” when

Folder-download failures retain their reason and recovery guidance instead

Desktop downloads mint their access token after destination selection, so

Added behavioral regressions for workspace/user skill catalogs, provider

Updated provider, architecture, source-control, observability, and native

The branch picker searches fetched remote branches alongside local

Remote branches appear in their own group, with checkout as their action.

Bring my changes carries non-conflicting edits while preserving Git's

Partial staging of new files works when Git is configured to use mnemonic

Review diffs retain their file names when Git uses mnemonic, omitted, or

Generated commit messages name the changed files correctly with those

Heartbeat scheduling no longer accumulates delays when timers wake

CI and release verification now run package test tasks one at a time as

SSH tunnel test fixtures use numeric loopback without reverse-DNS lookups,

Claude hook tests wait for server admission before toggling activity,

Release, flaky-test diagnosis, and Linux desktop-validation procedures

Failed and uncertain messages explain what happened, name the provider

A queued turn that starts as the previous turn finishes is no longer cut

Provider instances use the same name in Settings, model pickers, chat

Codex custom models accept their configured reasoning effort, and Claude

The work log uses plain titles such as Session ready and **Turn

The left panel groups the primary checkout and worktrees into outlined

Card and project menus group their actions and add Pull, **Copy Branch

When several windows share a terminal, the window you use controls its

Tabs visibly mark their selection, and the command palette highlights

Commits, branches, tags, stashes and fetches made from another terminal,

Clone from URL no longer stops after 30 seconds and keeps running on

Git transfers allow time for large repositories and report stalled HTTP

Changes, History, Tags and the primary workspace card explain whether a

The chosen tab survives Git failures and reconnects. Retry stays busy

Delete Worktree… refuses while a session in that checkout is running

Self-hosted GitLab instances are recognised through configured `glab`

Large History pages and diffs can finish over slow connections without

Connecting allows up to two minutes to receive the server's settings

SSH environments launch and pair correctly, reuse their saved credential

Hosted pairing links stay open until you choose Pair this backend.

Rename… in Settings → Remote Servers changes a saved server's

The Linux AppImage follows the system light or dark theme at launch and

Protected in-app updates work while Share This Host is enabled,

If an update fails and the local server cannot restart, the app explains

Restarting an AppImage after an update or from recovery releases the old

Reconnecting clients reuse recent provider checks for up to five minutes,

Git status resumes automatically after a busy client falls behind.

Interrupted Git commands stop their helper processes too. Terminal commands

Server and desktop tests isolate provider and hosting CLIs, terminal homes

`git pull`, `git fetch` and other HTTPS Git commands in a BiBCode terminal

Claude Code status line scripts and other tools that run the system Python

Chat-mode and terminal-mode agents, their probes and helper processes, Git

Commands started from BiBCode no longer search the current directory for

Send a message while an agent is working and it becomes a queued card in

Steer on the first queued card delivers it into the turn that is still

Stop drains the queue back into your draft before it interrupts the

The queue lives on the server, so every window sees the same queue: a

Queued messages never send themselves into an approval prompt, a question,

`Mod+Shift+Enter` steers the first queued message from the composer.

Sending after a provider process exits mid-turn now starts a new provider

A server restart while a turn was running no longer leaves the conversation

Closing or restarting a terminal while it is still opening no longer starts

The Linux AppImage prefers the native Wayland backend on a Wayland session

A Pull Requests button on each project header (after Git Manager) opens

List with Open/Closed tabs (GitLab: Open, Merged, Closed, All), search,

Detail page in the shape of the GitHub pull request page: header with

Reviewing: post, edit and delete comments; reactions; reply, resolve and

Editing: title, description and base branch; reviewers, assignees, labels

Merge box with the methods the repository allows, subject and body,

Checkout for local verification into the current checkout, another

Every control that the host does not allow stays visible, disabled, with

Verified end to end on GitHub and on a self-hosted GitLab 19.3 instance.

Worktree toolbars no longer show Loading worktrees… after the list has

Worktrees created from a pull request use the head branch name, or

A supervised process spawn retries briefly while the executable is still

Pending changes are grouped by folder inside each section. A folder row

A Group by folder / Flat list toggle next to the section actions is

New branch now forks from the branch you have checked out (or the

An upload URL is now bound to one file name; a leaked upload link can no

Download names with non-ASCII characters arrive intact in browser mode

Upload names are validated for the filesystem that stores them: Windows-only

A refused upload now names the file in its message.

macOS builds stay ad-hoc signed; the README and the release runbook explain

Download on a right-clicked file saves that file; on a folder it saves a

Upload Files… on a folder row, or on the tree background for the

Both actions work for remote environments. Transfers stream over two new

A Tags tab after Changes and History lists local tags and, per remote,

Creating a tag offers Push to `<remote>` after creating; if that push

Push, publish, and force push confirm in one dialog with Also push tags,

Annotated tags are compared by the commit they point to on both sides, so a

A selected project node stays selected in the left panel until another

The Git Manager toolbar shows the connected environment next to the project.

The merge dialog's Merge commit option is the default and stays visibly

A thread that runs in its own worktree shows its branch as a muted label

Asset and transfer URL tokens share one signed-token module with separate

The route inventory used by the maintenance audit now lists the transfer

The project row's branch label updates as soon as a Git Manager or

Worktree rows follow a Git Manager checkout, branch create, rename, delete,

The Git Manager shows which project it manages: the project's header row

The selected host is framed by a primary-colored ring and unselected hosts

Merge commit always records a merge commit. It never fast-forwards and

Squash merge now works in repositories that set `merge.ff=false`,

The bypass-hooks option of the squash-merge operation now applies to the

The merge dialog disables Merge and says Nothing to merge when the

Open in Zed now appears when Zed is installed. Zed is detected on `PATH`,

Every external editor is resolved through one shared server catalog.

Flatpak editors are launched with access to the opened file's directory, so

Remote hosts, and browser clients without a native dialog, open a folder

The Settings remote directory picker uses the same browser and stays stable

The Reuse branch control is visible whenever a branch is selected. It is

A branch list that fails to load is reported in the dialog with a recovery

`Shift+Enter` inside a terminal sends a soft newline, so Codex and Claude

Raised the publication preflight budget to 60 minutes after v0.5.9 approval

Fixed Fetch origin and other system Git operations failing from the Linux

Isolated Git and source-control helper processes from both the current

Preserved unrelated host library directories, credential and SSH-agent

Kept ordinary non-AppImage server launches unchanged and avoided

Added a production-runner regression that builds an intentionally

Added CI coverage using system Git on Debian 12 and 13, Ubuntu 22.04 and

Reproduced the original Fedora failure and verified a patched dry-run fetch

Updated the Linux testing runbook, runtime architecture, CI reference, and

Added capability-negotiated, ordered terminal input. Updated clients can send

Added bounded input windows and reserved RPC capacity for control operations,

Bound each input lease to its physical connection and exact terminal process.

Added Reconnect input after delivery failures. It reattaches to the

Fixed input preparation after open, reopen, restart, and fresh attachment so

Older servers retain the existing serialized input path. Update both the

Claude and Codex usage now comes from the environment selected in the rail,

Manual/background refresh and usage-reset actions target that same selected

A loading or disconnected remote server no longer borrows local account

Fixed newly active center panels remaining blank while a geometry update is

Fixed macOS process termination when navigation cancels an in-flight WebKit

Wait for native navigation and the new document's load event after desktop

Made packaged desktop validation independent of suspended macOS paint frames,

Added regression coverage for input ordering, queue bounds, cancellation,

Added a native encrypted-transport test that delivers reversed frame arrivals

Integrated current main without reverting its toolchain changes and

Updated the connection/RPC architecture, workspace guide, and native testing

The Share this host → Address dropdown now displays each endpoint's IP

Automatic (LAN) remains available. Explicit network addresses appear once

Added Server alias (optional) to the Add Server pairing-code form.

Aliases are trimmed; blank input uses the name supplied by the pairing code.

Aliases use the existing connection catalog labels and retain the

Fixed loopback/SSH-tunnel pairing being rolled back when an already-active

Fixed a terminal cleanup race by retaining a child process's exit result for

Added regression coverage for address selection, alias persistence and

Updated the remote-access guide, connection-runtime documentation, and

Standardized development on Node.js 26.8.1, pnpm 11.25.0, Rust/Cargo 1.98.0,

Updated React and React DOM to 19.2.8 with matching types, and refreshed the

Moved Pierre Diffs to stable 1.3.6 and its public editing API, removed the

Converged Effect core and its selected v4 companions on

Updated the supported Rust and Tauri dependency floors under Rust 1.98,

Retained WebdriverIO 9.29 and the Tauri automation service/plugin 1.2 cohort.

Reworked vendored-reference synchronization into an exact,

Refreshed the exact Effect and Alchemy reference snapshots and made the

Hardened Clerk frontend-domain validation by rejecting malformed or

Updated immutable GitHub Actions pins, release/test contracts, native port

Desktop installers for macOS 11+ on Apple Silicon and Intel, Linux on ARM64

Standalone server archives for all six OS/architecture targets, plus ARM64

Signed updater payloads and a six-target `latest.json` manifest for the

A saved remote server is now identified by the host's storage instance id

The host's declared id is kept beside the client's own key, and the connection

The manual endpoint-and-token path identifies a server the same way, keeping

"Server already saved" now names the entry that was collided with instead of

The remote architecture document records how a saved remote is identified and

The environment rail now reserves the same topbar strip the thread sidebar

The end-to-end-encrypted channel now reads WebSocket frames delivered as

The blocked-remote cancellation test in the Git status broadcaster awaits

The macOS bundle now merges an `Info.plist` that relaxes App Transport

The remote architecture and release documents record the macOS gate beside

Added `bibcode pairing offer`, which mints an encrypted `bibcode://pair?code=…`

`bibcode serve` now prints a ready-to-paste `pairingCode` in its startup line

The Add Server dialog names the CLI as a source of pairing codes alongside the

Added `bibcode service install | uninstall | status`, which installs a systemd

Fixed the desktop webview policy that made every Add Server attempt against

The Linux desktop now offers its acknowledged reset when WebKit reports

Server bind failures now report the address and the operating-system error

The updater signature verifier covers all six supported desktop targets,

Remote access and standalone server guides cover the CLI pairing offer, the

Added Remote Servers settings, pairing-code and `bibcode://` deep-link

Added authenticated Noise NK transport with bounded record fragmentation,

Added grant-derived sharing state and verified exposure transitions. Windows

Hardened pairing and session authority across cancellation, reconnects,

Added remote server update discovery and installation through the existing

Added a GitHub Desktop-shaped centre panel for each project, covering working

Added an on-demand pull-request and checks pane with GitHub, GitLab, and Azure

Kept Git Manager activity server-owned, bounded, non-interactive, and free of

Improved the final packaged behavior found during macOS and Windows native

Redesigned the pull-request review dialog for readable repository/base/head

Added a full-height Agents view with environment/project/status grouping,

Raised the sidebar and navigation text floor, increased the default sidebar

Added a shared orange panel-separator token and aligned the environment rail,

Corrected route, capability, stale-status, dialog, and layout edge cases found

Expanded the release matrix to macOS, Linux, and Windows on both ARM64 and

Added standalone `bibcode` server archives for all six targets plus native

Hardened Windows ARM64 and x64 builds with architecture-aware MSVC setup,

Hardened Linux packaging around an Ubuntu 20.04 server compatibility build,

Hardened macOS/Linux startup PATH hydration so login-shell probes detach from

Database migrations 46–49 add pairing reach metadata, a durable pairing-offer

Remote transport, Git Manager, Agents-view, provider-check, and update

Expanded native CI, release-candidate validation, packaged desktop UI and

Stabilized release gates by target-gating macOS-only test imports, giving

Removed an accidental literal NUL from tracked TypeScript source and added a

macOS 11+ Apple Silicon (`arm64`) DMG

macOS 11+ Intel (`x64`) DMG

Linux ARM64 AppImage

Linux x64 AppImage

Windows 11 ARM64 NSIS installer

Windows 10/11 x64 NSIS installer

Standalone server archives for all six targets, plus Linux ARM64/x64 `.deb`

Added live update-protection progress for every local backend, including the

Classified RPC methods through the typed contract inventory so long-lived

Kept verified backup protection as the default and the primary retry path.

Preserved exact backend-topology safety for the acknowledged fallback: the

Improved the protection-failure dialog so retry, exact secondary exclusions,

Kept each Codex terminal on its launch palette until an explicit restart, so

Applied the resolved terminal palette when opening agent and script

Prevented a light in-band color-scheme reply from selecting Claude Code's

Removed inherited `NO_COLOR`/disabled-color host settings from PTY launches

Changed the device-local terminal-theme default to Follow app theme;

Prevented the chat surface from reading an unavailable nested platform value

Made the startup activity-recovery test use a current fixture timestamp so it

No database migration or intentional breaking API change is included. New

The release pipeline provides macOS 11+ Apple Silicon and Intel DMGs, a Linux

macOS builds remain ad-hoc signed and unnotarized; Windows installers remain

Replaced per-project branch polling with server-owned, event-driven VCS

Added shared local/full status-read owners with cancellation leases, mutation

Added one automatic-fetch owner per physical repository. Linked worktrees

Added lightweight passive VCS summaries for sidebar state. Fresh local and

Reduced Git work by using one porcelain-v2 status snapshot, running numstat

Added bounded, no-follow repository fingerprints so healthy Focus refreshes

Hardened create, publish, retarget, detach, remove, file-write, and stacked Git

Reworked Create Worktree around one permanent Name editor plus optional

If a selected remote branch becomes local before submission, the server now

Added strict Bitbucket request/body bounds and exact selected-remote handling

Added a server-authoritative workspace entry stream and immediate Refresh

Rebuilt the cached file index from concurrent tracked/ignored Git listings

Added explicit cache invalidation for create, rename, delete, duplicate, new

Added drag-and-drop moves to folders or the workspace root, correct new-entry

Failed, cancelled, or availability-raced moves and mutations now roll the

Kept every directory as its own row rather than merging single-child folder

Added compatible runtime error classes beside provider messages. The UI can

Preserved provider-native failure details and terminal reasons for Claude,

Made refused or uncertain delivery visible in the sidebar and thread status,

Hardened OpenCode event-stream handling so connection failures, HTTP errors,

Tightened process, logging, provider, VCS, watcher, workspace, and catalog

Added a device-local Terminal theme setting: Always dark by default,

Fixed resize bursts that could strand Codex or another full-screen TUI at an

Fixed center-panel separators disappearing against adjacent surfaces.

Prevented stale sidebar and thread-status updates from overwriting newer

Database migrations 44–45 add provider error attribution and unresolved

Contract additions are additive and older error-class values decode safely as

Expanded living architecture, source-control, workspace, observability, and

`vp check`, all 11 `vp run typecheck` targets, 8,266 Vite+ tests, release

Packaged macOS interaction was visually verified with Codex Computer Use,

The release pipeline builds and verifies macOS 11+ Apple Silicon and Intel

macOS builds remain ad-hoc signed and unnotarized; Windows installers remain

External Files changes are detected within seconds rather than instantly;

The complete Git Manager interface described in the new implementation plans

Added an authoritative worktree catalog that discovers existing Git worktrees, lets users adopt one or all discovered checkouts without recreating them, and preserves physical identity across path aliases and reconnects.

Added explicit recovery and removal flows for missing or present worktrees, including fresh server-side plans, dirty/stale-registration confirmations, durable retry receipts, and identity-safe cleanup on Windows, macOS, and Linux.

Improved local desktop presentation: macOS and Linux now focus on the local environment, Windows keeps truthful WSL location and recovery controls, Cursor is enabled as a supported provider, and legacy Grok actions are hidden.

Improved Activity timestamps and hierarchy while bounding Claude fallback ambiguity so stale or unrelated processes are not presented as controllable activity.

Hardened provider, terminal, logging, persistence, update, and shutdown ownership under parallel load, including bounded OpenCode reaping, isolated native fixtures, and per-runtime process cleanup that preserves sibling desktop runtimes.

Hardened Linux packaging and expanded repeatable native validation across macOS arm64/x64, Linux x64, and Windows x64.

Database migrations 40–43 add per-project worktree discovery state, repository identity pins, and durable worktree-removal receipts. Existing stores are migrated through the normal verified pre-migration backup path.

No intentional breaking API change is documented. Older servers that do not advertise worktree-catalog support continue without the new catalog controls.

macOS artifacts remain ad-hoc signed and unnotarized; Windows installers remain unsigned.

Native Windows, Linux, and both macOS architectures require their respective release runners for final installer and updater verification.