What's new in BibCode

BiBCode v0.5.13 shows where pending changes live in the Source Control panel,

narrows Files-panel upload tokens to a single file, and makes download and

upload names behave on every platform.

shows the full relative directory (shortened from the start so the deepest

part stays readable), a file count, a collapse chevron, and a checkbox that

stages, unstages, or selects every file in that folder in one request. File

rows underneath show only the name and its diff stats.

remembered per user. The flat list keeps file names visible and shortens

only the directory.

current HEAD commit when HEAD is detached) instead of the repository's

default branch, and the dialog shows that base branch in a highlighted chip

before you confirm.

longer write any other name in that folder, and a request that names a

different file is refused.

(`Content-Disposition` carries an RFC 5987 encoded name), and a name that

previously broke the response no longer does.

rules (reserved names, `<>:"|?*`, trailing dots or spaces) apply only when

the server runs on Windows, so Linux and macOS workspaces keep accepting

their legal names. Names up to 255 bytes upload; the desktop host shortens

an over-long download name instead of refusing it, and on Windows renames a

download that Windows could not store, reporting the saved path.

that folder and network permissions are asked again after each update.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.12...v0.5.13

BiBCode v0.5.12 adds Download and Upload to the Files panel for local and

remote environments, gives the Git Manager a Tags tab with push options, and

fixes four left-panel and Git Manager presentation problems.

`.zip` of the folder. The desktop app asks for a destination folder and never

overwrites an existing file (`name (2).ext`); a browser uses its own

download location. Folders over 2 GiB or 200,000 entries are refused with a

message before the download starts; symbolic links and special files are

skipped, ignored files are included.

workspace root, opens a file picker and uploads the chosen files into that

folder. It is disabled on file rows with the reason in the label. A file

that already exists asks before it is replaced; a failure names the file and

the rest of the batch still uploads. Files up to 1 GiB each are accepted.

token-authenticated routes on the server that owns the workspace

(`/api/transfers/{token}`, five-minute signed tokens bound to one file,

folder, or upload directory), so they work on every connection profile.

After an upload the file tree and the Git status refresh at once.

the tags that remote advertises, in collapsible sections whose state is

remembered per project. Remote tags are queried when the tab opens and on

its refresh button; rows are marked when a tag is missing locally or points

elsewhere, and an unreachable remote shows its reason with Retry.

fails the tag still exists locally and the failure says so.

which sends every local tag with the branch in one atomic push.

tag that matches the remote is no longer reported as differing.

thread is opened.

selected.

after its title instead of a folder icon that looked like the project's

"New worktree" action.

purposes, so a token minted for one can never be redeemed as the other.

routes.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.11...v0.5.12

BiBCode v0.5.11 makes the left panel follow Git Manager branch changes at

once and makes the active host and the managed project visible at a glance.

source-control mutation finishes, or a terminal command exits, instead of

waiting for the passive status summary's 30-second cycle.

pull, merge, rebase, cherry-pick, revert, or reset without waiting for the

worktree catalog's polling interval.

stays highlighted in the left panel while the manager is open, and the

toolbar leads with the project's name, with its checkout path on hover.

are muted, so the active host is unambiguous next to the panel separator.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.10...v0.5.11

BiBCode v0.5.10 makes Git Manager merges keep their promises, detects and

launches Zed as an external editor, lets Add Project browse remote host

folders, and fixes Create Worktree and terminal input problems.

overrides repository settings such as `merge.ff` or branch merge options

that would skip the commit or squash it.

`merge.ff=only`, or a branch `--commit` merge option; Git previously

rejected or aborted the squash.

squash commit itself.

source branch has no commits the current branch lacks.

through the `zeditor` alias, a Flatpak export (`dev.zed.Zed`),

`~/.local/bin`, the macOS app bundle CLI, and the Windows per-user install

directory.

Detection runs on the server that owns the environment, so a remote

environment lists the editors installed on that remote host.

projects outside the home directory open without extra Flatpak overrides.

browser that lists the selected host's directories; Type a path instead

switches to manual entry of an absolute or home-relative path. Local and WSL

locations keep the native folder picker.

through the dialog's exit transition.

enabled for a free local branch and disabled, with an explanation, for a

remote branch or a branch already checked out elsewhere.

hint, and a typed name still creates a new branch.

Code prompts insert a line break instead of submitting; plain `Enter` still

submits.

runs reached the previous 30- and 45-minute limits while the full test graph

was still running. Every gate stays enabled, and the workflow contract and

release runbook record the measured limits.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.9...v0.5.10

BiBCode v0.5.9 fixes Git network operations from the Linux AppImage and adds

repeatable compatibility coverage for Debian, Ubuntu, Fedora, and Arch.

AppImage with `symbol lookup error` when Fedora's `libcurl` loaded an

incompatible `libnghttp2` bundled by the AppImage.

AppImage library directory and stale `.mount_*` directories inherited after

application updates. This applies to text and binary-output Git commands.

settings, command-local environment overrides, and Linux loader semantics for

current-directory entries. The desktop process environment remains unchanged.

distribution-specific library paths, so the fix uses each host's own system

Git dependency set.

incompatible shared library, proves the system Git HTTPS helper fails when it

loads that library, and verifies the patched runner restores normal helper

initialization without contacting an external Git server.

24.04, Fedora 44, and Arch rolling. Coverage includes extracted AppImages,

paths containing spaces, stale mounts, colon and semicolon separators, and

parent-environment isolation.

against the affected repository completed without a loader error or changing

refs or `FETCH_HEAD`.

script reference to define the cross-distribution Git compatibility contract

and distinguish it from complete packaged desktop qualification.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.8...v0.5.9

BiBCode v0.5.8 improves remote terminal responsiveness and makes AI usage status

follow the server you are working on.

subsequent keystrokes before the previous write's reply, reducing the extra

queue delay on remote connections. A controlled 120 ms round-trip test reduced

median time queued before sending from about 59 ms to under 1 ms. Network

round-trip latency still affects when remote output appears.

including when terminal traffic competes with persistent subscriptions.

Unicode paste and control sequences retain their delivery order.

Failed, duplicate, incomplete, disconnected, or stale input cannot be replayed

into a replacement process. A delayed old attachment request cannot replace

a newer attachment's lease.

existing agent process without restarting it or replaying discarded text.

immediate programmatic writes work before the terminal renderer arrives.

Visual panel hiding and moving preserve the existing input binding.

desktop client and remote server to activate ordered input; failures on the

new path never silently retry through the old path.

rather than always using the primary local server.

environment. Late responses remain associated with their original server.

usage. Terminal counts and remote diagnostics also follow the selection,

while the separate local desktop diagnostic source remains available.

waiting for paint. Initial and activation layout measurements run before

paint and refresh replaced targets, while ordinary resizing remains batched.

request. Optimized builds now retain the exception unwinding required by

Wry's recovery path, with a native release-profile regression and build guard.

test reloads. This avoids sending JavaScript into a document being replaced.

Readiness generations are recorded only in test builds. Backend logs and

bounded macOS crash summaries are retained for native test failures. macOS

smoke tests now verify and run an isolated installation copied from the DMG.

Scenario reloads restore the test motion guard, while motion assertions

explicitly exercise native transitions.

wait for native viewport resizing and workspace terminal controls, and target

Pierre selection shortcuts

at the shadow editor on Windows. Existing edit, undo, and lifecycle assertions

remain in the native platform suite.

stale attachments, legacy-server compatibility, immediate writes after

lifecycle changes, and provider-usage isolation.

into a real PTY in the correct order and refuses another socket's lease use,

even when it authenticates with the same bearer.

regenerated the new RPC fixtures against the current Effect protocol.

procedures for input recovery and selected-server usage.

On macOS, copy BiBCode.app from the DMG to Applications before launching it.

Desktop installers and standalone server distributions are provided for macOS,

Linux, and Windows on ARM64 and x64. Linux server `.deb` and `.rpm` packages are

included for both architectures. Stable desktop updater payloads and signatures

remain available through `latest.json`.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.7...v0.5.8

BiBCode v0.5.7 makes remote servers easier to identify when sharing a host or

saving a paired connection.

address or hostname instead of repeated labels such as “Local network” and

“Private network”. Active LAN, Tailscale, and NetBird interfaces can be

distinguished directly in the list, with duplicate endpoint URLs removed by

the existing selection logic.

native sharing is enabled; endpoint availability, default selection, public

address restrictions, and pairing behavior remain unchanged.

The alias is saved on the connecting device and appears in its saved-server

list and environment rail, including after reconnecting or restarting.

Failed pairing preserves the entered alias for retry, while successful

pairing clears the completed form.

storage-instance identity introduced in v0.5.5. They do not rename the remote

host, change its identity, or affect names on other clients.

standard credential could not call the administrative confirmation RPC. The

client now verifies that credential through its connection supervisor;

server permission checks and pending-pairing confirmation remain enforced.

late subscribers, including children that finish before a watcher attaches.

hydration, blank aliases, and failed-pairing retry behavior.

macOS, Linux, and Windows native validation procedures.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.6...v0.5.7

BiBCode v0.5.6 is a supported dependency and toolchain convergence release. It

moves the web, desktop, server, relay, and repository tooling onto one reviewed

set of current compatible versions while preserving the native Rust/Tauri

runtime and the existing browser/desktop RPC boundary.

Vite+ 0.3.0, Vite 8.2.2, and the single Vitest 4.1.11 runtime supplied by

Vite+. The main workspace now uses TypeScript 7.0.2; the Astro marketing app

remains on TypeScript 6.0.3 until its public checker supports TypeScript 7.

Base UI, Lexical, TanStack, fonts, icons, DOM test runtime, and other

maintained frontend dependencies as compatible cohorts.

retired Pierre prerelease patch, and retained diff review, partial staging,

editor history, undo, and conversation rendering behavior.

`4.0.0-beta.107`. Alchemy remains on the newest compatible beta.72 release,

paired with the exact Drizzle ORM and Kit RC5 build required by that train,

avoiding the incompatible Effect RC.112 split.

including the source compatibility repairs required by the new compiler and

libraries. The application remains a native Rust/Tauri desktop and server

runtime; no production Node.js service or Electron host was introduced.

The 1.3 line remains blocked until upstream fixes teardown ordering and aligns

its globals/expect dependency train.

history-independent snapshot transaction. Linked worktrees share one writer

lock; literal Git paths, pruning, casing, and file modes are preserved; and

typed failures, defects, interruption, and timed rollback all quiesce their

child processes before recovery advances. An unverifiable recovery keeps the

lock for explicit repair instead of exposing partial state.

dependency ledger declaration-complete: 221 audited entries, no pending row,

and no unaccounted direct dependency or toolchain declaration.

unsupported Punycode labels before URL construction. Valid IDN custom Clerk

domains remain unsupported until BiBCode owns one deterministic

cross-runtime IDNA validator.

probing, process-watchdog coverage, raw Git parsing, and repository identity

checks used by the cross-platform build and packaged-test paths. The Git

broadcaster cancellation regression now proves synchronous lifecycle

cancellation and joined cleanup without depending on a five-second scheduler

race, and Claude hook-plumbing coverage uses an isolated probe context under

parallel load. Catalog joins now reserve a workspace's current direct path

before any retained-snapshot fallback, preventing duplicate old/new ownership

after a retarget; its integration coverage uses an owned healthy-refresh

boundary.

and x64, and Windows 11 ARM64 plus Windows 10/11 x64.

and x64 Debian and RPM packages and `bibcode-server-SHA256SUMS`.

stable in-app update channel. macOS applications remain ad-hoc signed and

unnotarized, and Windows installers remain without Authenticode.

Full Changelog: https://github.com/mubeda/BibCode/compare/v0.5.5...v0.5.6

BiBCode v0.5.5 fixes desktop pairing: Add Server refused every pairing code

with "Server already saved" even when no server was saved at all.

rather than by the environment id the host declares about itself. Every

BiBCode server declares the same id — `local` — including the server the

desktop app runs in process, so the app's own Local environment and every

remote host claimed one key in the client's environment registry. Pairing saw

that key already taken and refused the code; removing the saved server could

not help, because the entry it collided with was Local, which cannot be

removed. Two different remote servers would have overwritten each other the

same way. Reproduced in the desktop app on a data root that had never seen the

remote host, and verified afterwards against an independent second server:

both hosts declare `local` with different storage ids, the remote pairs

end-to-end encrypted, and it now appears in the environment rail alongside

Local instead of replacing it.

resolver checks the endpoint against that stored value on every connect, so

the identity assertion is preserved rather than dropped. Servers saved before

this release carry the declared id in their existing field and resolve through

it unchanged — no re-pairing and no migration.

the declared id for hosts that report no storage id.

printing one generic sentence, so the dialog says which saved server to

reconnect to or adopt.

why a host's declared id cannot key it. The Linux, macOS, and Windows desktop

runbooks check that a paired server appears alongside Local and that a second

offer from the same host is refused by name.

BiBCode v0.5.4 fixes the desktop workspace sidebar: the floating **Toggle main

sidebar** control sat on top of the environment rail's first entry, so aiming

at Local collapsed the sidebar instead of selecting the environment.

header reserves, so the first environment entry starts below the fixed

toggle instead of underneath it. The rail's separator line is continued

across the reserved strip, keeping the header edge unbroken between rail and

sidebar. On a native macOS titlebar the control resolves to the top-left

52px column, which is exactly the rail's width, so the two overlapped

completely; a WebKit geometry harness built from the shipped stylesheet

reported 672 px^2 of overlap and a hit-test at Local's centre landing on the

toggle, and reports no overlap with Local receiving the hit after the fix.

The thread sidebar brand drops its control-clearance margin because the

control no longer overlays that header, while the collapsed-sidebar centre

panel header keeps using the shared offset variable. A regression assertion

pins the reserved strip ahead of the environments group.

BiBCode v0.5.3 fixes the encrypted pairing channel in every desktop app: with

the v0.5.1 connect policy and the v0.5.2 macOS transport exception in place,

pairing still ended as "Server unreachable" because the client rejected the

server's handshake reply.

`ArrayBuffer`, which is what every real browser hands over once the socket

is switched to `binaryType "arraybuffer"`. The client previously treated

such frames as non-binary, failed the Noise handshake as a protocol error

right after receiving the server's reply, and closed the socket without

sending its pairing message. Verified end to end inside a WebKit page

carrying the app's policy against a live server: the handshake completes,

the pairing token is consumed, and the session is minted. A regression test

drives the handshake through a socket that delivers `ArrayBuffer` frames.

the cancellation before releasing the blocking permit, removing a race that

failed a release preflight under CI load.

BiBCode v0.5.2 is a macOS-only fix on top of v0.5.1: the desktop app can now

reach plain-HTTP remote servers on a LAN or tailnet, which App Transport

Security had been refusing before any packet left the machine.

Security for web content only (`NSAllowsArbitraryLoadsInWebContent` and

`NSAllowsLocalNetworking`) and declares the Local Network usage description,

so Add Server → Pairing code works against `http://` servers. Native

code keeps the default policy, and the hardening test rejects the blanket

`NSAllowsArbitraryLoads`.

the webview connect policy introduced in v0.5.1.

BiBCode v0.5.1 makes headless servers pairable from the desktop app without a

browser detour, keeps them running across reboots as a per-user service, and

fixes two connection blockers found in real use: the desktop webview refused

plain-HTTP remote servers, and a WebKit downgrade left the Linux desktop unable

to open its connection database.

offer directly against the data root, beside a running server, for pasting

into Add Server → Pairing code. Endpoint and reach rules are shared with

the Share tab, and the command fails closed until the server has started on

that data root once.

when bound to a routable address. `--no-startup-pairing-offer` (or

`BIBCODE_NO_STARTUP_PAIRING_OFFER=1`) keeps that credential out of service

logs; loopback and wildcard binds print none.

Share tab.

user unit on Linux (enabling lingering so it starts at boot), a LaunchAgent on

macOS, or a logon scheduled task on Windows, running `bibcode serve` as the

invoking user with that shell's `PATH` so provider CLIs keep finding their

credentials. Nothing ships inside the Linux packages; the definition is

written on request.

a LAN or tailnet server fail with "Server unreachable" before a packet left

the machine, on all desktop platforms. `connect-src` now admits `http:` and

`ws:` in addition to loopback and TLS, while scripts and default sources stay

same-origin; a hardening test pins the policy.

"Unable to establish IDB database file", which happens when an AppImage

bundling an older WebKitGTK opens a connection database migrated by a newer

one. The dialog explains each cause, and the runbook documents the data-root

isolation that avoids it.

instead of a bare "failed to bind the server listener".

including Linux ARM64 and Windows ARM64, and manual release repair runs stay

pinned to the immutable tag while using current release tooling.

startup pairing code, and running the server as a per-user service. The

remote architecture document records the offline offer path, the startup

offer, the service installer, and the webview connect policy. The three OS

runbooks add headless pairing, restart, and service validation steps.

BiBCode v0.5.0 adds first-class remote environments, a complete project-level

Git Manager, and a dedicated Agents view. It also expands native desktop and

standalone-server releases to six OS/architecture targets and hardens the

connection, process, packaging, and test boundaries exercised by those

features.

flows, manual and SSH-assisted connection setup, saved-server lifecycle

controls, compatibility/version status, remote update actions, and an

environment rail that scopes projects and actions to the selected machine.

no-downgrade credentials, pinned host identity, transport-scoped sessions,

and explicit protocol-compatibility negotiation for off-host connections.

remote access uses a program-scoped firewall rule and rolls back firewall,

listener, and persisted state when widening or narrowing cannot complete.

concurrent server processes, stale delivery, duplicate requests, revocation,

forwarded loopback peers, and bounded per-principal byte/message capacity.

Remote failures remain typed and retryable without silently substituting a

local or WSL backend.

desktop-owned updater boundary, including status badges and bounded

multi-server checks.

tree and staged changes, per-line and per-hunk selection, commit/amend/undo,

safe discard, paged history and diffs, branches, tags, fetch/pull/push,

publication and force-with-lease, stashes, merge previews, rebase,

cherry-pick, squash, reorder, revert, reset, conflict recovery, and image

diffs.

provider resolution. Pull-request creation now opens a non-mutating review

dialog and only publishes the branch and creates the PR after final

confirmation; retries reuse an existing pull request.

background telemetry. Repository generations fence stale reads, concurrent

mutations share one owner, capabilities degrade independently, and remote

environments retain the same typed RPC boundary.

validation: clean checkouts select History, dirty/loading selections are

preserved, merge recovery stays on Changes, history rejects stale pages,

symbolic remote `*/HEAD` pointers are not shown as branches, and a temporarily

missing upstream tracking ref no longer makes the manager unavailable.

metadata, clear branch-publication guidance, stable padding, and a fixed

action footer.

filtering, unread state, provider identity, branch and conversation previews,

live detail, and capped server-pushed shell summaries.

width with double-click reset, and improved Linux WebKitGTK font hinting and

subpixel rendering without changing other applications' GTK settings.

sidebar, content headers, Git Manager, diff/file/preview panels, terminal,

status bar, and top frame in both themes.

during packaged macOS, Linux, and Windows interaction testing.

x64. Desktop downloads now include two DMGs, two AppImages, and two NSIS

installers; the signed updater manifest contains all six matching targets.

ARM64/x64 Debian and RPM packages, install-and-run container tests, a sorted

SHA-256 manifest, and optional minisign signatures.

drive-safe portable ZIP creation, checkout-local Vite+ execution, cached NSIS

tooling, explicit sidecar execution manifests, bind-only port probes that do

not trigger firewall prompts, and targeted cleanup for test-generated rules.

native package smoke matrices, AppImage portability, minimal RPM curl

dependencies, and ownership restoration after container builds.

inherited controlling terminals, accept a complete framed result without

waiting for lingering descendants, and reap their process group before

desktop startup continues.

idempotency ledger, shared authentication-authority revision state, and active

pairing-delivery state. Existing stores continue through the verified

pre-migration backup path.

contracts are additive; no intentional breaking API change is documented.

upgrade smoke tests, remote Docker validation, source-control fixtures, and

cross-platform runbooks. The macOS Git Manager flow was exercised against a

real private GitHub repository through branch, diff, staging, commit, history,

push, pull-request, checks, tag, fetch, and checkout behavior.

uncached Rust workspace jobs an explicit workflow budget, and replacing a

scheduler-sensitive Git broadcaster teardown timer with canonical lifecycle

retirement. Windows forced-shutdown coverage now exercises the production

timeout instead of a scheduler-sensitive 250 ms fixture window, and

cross-process auth revocation coverage distinguishes queued prior revisions

from the forbidden post-revocation event. Authority-expiry coverage starts

its short-lived grant only after nonessential fixture setup is complete.

repository-wide guard so text-source corruption fails tests immediately.

and `.rpm` packages and `bibcode-server-SHA256SUMS`

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

without Authenticode. Tauri updater payloads are independently signed and

verified by BiBCode before publication.

Full changelog: v0.4.2...v0.5.0

BiBCode v0.4.2 makes desktop updates easier to understand and recover from,

while keeping Codex and Claude terminal interfaces readable across app-theme

changes.

current protection stage, elapsed time, and active mutation count while

BiBCode drains work, quiesces the runtime, checkpoints SQLite, creates a

verified backup, and stops the backend.

read subscriptions do not block an update, while unknown methods still fail

closed as mutations.

Installing without a backup is available only after a real protection

attempt fails and the user explicitly acknowledges the risk; the native host

rejects forged first-attempt bypasses.

desktop host still snapshots and stops the running native and WSL backends,

restarts that same set if installation fails, and reports each environment

as skipped instead of protected.

and the destructive no-backup action remain distinct and correctly laid out.

changing the BiBCode app theme cannot make Codex composer text disappear or

leave the terminal half-repainted on macOS, Linux, or Windows.

terminals, including the OSC foreground, background, cursor, and Windows

console markers that terminal applications snapshot at spawn.

broken fullscreen light path inside the embedded xterm host, while retaining

dark-scheme and OSC color support.

unless the launch explicitly opts out, and advertised true-color support so

agent TUIs do not silently lose their ANSI colors.

Always dark remains available for users who prefer a fixed terminal

palette.

while server configuration is still partial, so opening a local draft cannot

fail during configuration bootstrap.

continues to exercise unresolved-versus-completed recovery after the

production 30-day completed-activity retention window advances.

updater progress and skipped-protection fields are additive and decode with

safe defaults.

x64 AppImage, and a Windows 10/11 x64 NSIS installer, plus signed updater

payloads and the four-platform `latest.json` manifest.

without Authenticode. Tauri updater payloads are independently signed and

verified by BiBCode.

Full changelog: v0.4.1...v0.4.2

BiBCode v0.4.1 is a reliability release for Git/worktree coordination, the

Files surface, provider error reporting, and embedded terminals. It replaces

poll-heavy or ambiguous state with lifecycle-owned observation, keeps UI state

honest across races and failures, and restores the intended Create Worktree

flow.

observation. Native worktree and Git-metadata watches coalesce bursts, retain

one trailing read, and use a bounded 60–300 second safety read when native

observation is unavailable or misses an event.

epochs, publication fences, deterministic shutdown, and clean reattachment.

A slow remote fetch, provider lookup, or cancelled caller can no longer delay

or publish over newer local state.

share the default 180-second fetch, exact remotes are fetched once, failures

use bounded backoff, and `0` still disables automatic fetch.

provider data publishes independently from pull-request enrichment; a prior

matching PR may be retained for only one stale cycle, and provider failures

no longer make the repository appear clean or unavailable.

only for areas that exist, and setting `GIT_OPTIONAL_LOCKS=0` on background

reads. Added native measurement tooling for Git-process rate and foreground

mutation queue latency.

can reuse trusted worktree inventory between mandatory five-minute Git

reconciliations. Unknown, changed, malformed, replaced, or over-limit inputs

fail open to a real inventory scan.

mutations so their status/catalog invalidation settles after the actual

filesystem, Git, and durable ownership result—even when the requester

disconnects, cancellation races, or a panic occurs.

Smart/GitHub/Branch sources. Exact local and remote refs no longer appear as a

duplicate result, free local branches enable Reuse branch by default, and

edited names remain stable.

reuses that free local branch. A branch already checked out by another

worktree retains the safe suffixed-branch fallback, including concurrent

creation races.

when publishing repositories, including protection against option-shaped

remote names.

action. External file/folder creates, renames, and removals rescan without

collapsing expanded folders; watcher startup now closes the initial-snapshot

race with an explicit resync.

plus bounded directory walks. Ignored trees and empty directories remain

visible, cold callers share one build, and ordinary warm reads start no Git

work.

parent paths, `.gitignore`, and `.git` classification controls while keeping

ordinary existing-file content saves inexpensive.

parent selection, open-tab path updates after rename/move, and close-on-delete

behavior.

optimistic tree back to server truth instead of leaving duplicated or stale

rows. Refresh failures preserve the existing tree and remain retryable.

chains, so actions and paths always target the directory the user sees.

now distinguish a provider-reported failure from a BiBCode transport,

permission, or validation failure without guessing who is at fault.

Codex, Cursor, Grok, and OpenCode. Fixed healthy Codex turns with `error: null`

being reported as failures and mapped documented refusal, output-limit, and

content-filter outcomes truthfully.

derived atomically from the durable outbox. Retry, dismissal, or successful

delivery clears it without overwriting provider-session identity or state.

clean EOF, chunk failures, and explicit stop all publish their terminal state

and close the provider stream. Supervisors no longer wait forever on a sender

retained by a completed runtime.

ownership across shutdown and reattachment so cancellation-ignoring work is

still awaited and cannot publish into a replacement lifecycle.

Always light, or Follow app theme. Terminal OSC colors and xterm's

extended grayscale palette now match that choice, avoiding dark TUI panels on

an otherwise light terminal.

intermediate PTY size. Every requested resize is retained and the worker

coalesces only to the newest dimensions.

unresolved-delivery, worktree, provider, or availability state.

delivery projection fields. Existing stores upgrade through the normal

verified pre-migration backup path.

unknown. No intentional breaking API change is documented.

cross-platform validation documentation. Added implementation plans and

reference screenshots for the future full Git Manager UI; those planning

documents do not claim that the complete planned Git Manager interface ships

in v0.4.1.

smoke, Rust formatting, workspace Clippy with warnings denied, the full Rust

workspace test suite, and the production desktop build passed with Rust

1.97.1.

including the single-editor Create Worktree dialog and the checked/unchecked

Reuse branch behavior.

DMGs, a Linux x64 AppImage, and a Windows 10/11 x64 NSIS installer, together

with signed updater payloads and the four-platform `latest.json` manifest.

without Authenticode. Tauri updater payloads are independently signed and

verified by BiBCode.

use Refresh for an immediate rescan. An arbitrary custom Git

`core.excludesFile` also requires manual Refresh after it changes.

is future work; this release ships its VCS coordination, summaries,

measurement, and reliability foundations.

Full changelog: v0.4.0...v0.4.1

Full changelog: v0.3.13...v0.4.0