Integrate the Android client with native desktop pairing, remote terminal and SSH/SFTP sessions, keyboard controls, file reading and Agent conversations. Preserve authenticated connection ownership and per-device input permissions.
Validation: all ten required GitHub checks passed, including five native test platforms and both macOS release workspace checks.
Reanchor only uniquely matched content after complete synchronized Pi redraws. Preserve standard clearing and cancel stale anchors on user actions or interrupted updates.
Related to #159.
Keep DECSET 2031 enable/re-enable silent while retaining reports for actual palette changes. Cover repeated subscriptions and byte boundaries.
Fixes#283.
Synchronize product crate versions, local dependency constraints, lockfiles, Windows resources and installer defaults. Add bilingual changes and verified contributor credits before CI packaging.
Preserve the committed memory and scrolling work from local main together with
update recovery and the default font rollback. Resolve terminal initialization
at its new lifecycle owner and keep native WSL lookup in the platform layer.
Document the seven history limits, wheel-speed settings, allocation tradeoffs
and connection-specific completion behavior in both release-note languages.
Synchronize package versions and bilingual notes with verified issue references.
Allow releases without PR contributors to omit that section, with positive and
negative format coverage as requested by the maintainer.
Keep native update process operations and default-shell resolution inside the
platform boundary. Preserve transaction authority in the updater and tighten
the platform condition budget to the measured 484.
Persist native AI recovery targets and per-pane launch contexts without treating
command submission as provider confirmation. Keep window partitions and the
active window in the durable session snapshot for immediate and scheduled updates.
Coordinate draft approval, snapshot writes, helper readiness, process exit and
installation with a committed transaction. Reverify packages and retain recovery
state on failure. Isolate acceptance installers from production integrations and
reject same-version setup that leaves the executable unchanged.
Validation: Windows GPUI suite 1552 passed; settings 55 passed; i18n 20 passed;
9 native helper scenarios; 77 installer migration checks and 41 static invariants.
Full interactive packaged upgrade acceptance remains separate.
Preserve the current main updates together with active SSH/WSL completion
ownership and native PowerShell predictions. Renumber the completion ADR
after the existing font ownership decision.
Track completion history, candidates and async directory results by the active
SSH/WSL connection, and restore the parent shell when the connection returns.
Use shared ownership rules in both UI adapters and report expanded arguments
from shell execution hooks. Preserve user PSReadLine prediction settings.
Add regression coverage for context transitions, stale results and actual
Windows ConPTY transport. Validate native SSH, WSL, local PowerShell and SSH
from PowerShell, including cross-environment negatives and native predictions.
History deletion and migration remain outside this change.
Combine custom themes, updater proxies and native resource fixes with the published release source. Preserve independent interface and CJK fonts, selection visibility, saved-session startup and all existing release checks. Remove the retired terminal-view size exception after the capability extraction brought it below the standard limit.
Persist the pending ConPTY lifetime, process snapshot and native font ownership fixes. Keep lifecycle regression tests and the Windows memory stress tool together with the ownership contracts.
Add Frappe and Macchiato, unify themed pane surfaces, and default to opaque
backgrounds without blur while preserving explicit appearance settings.
Keep default dividers one physical pixel wide at high display scaling.
Align rounded box strokes with adjacent cells and preserve modern Grok
console rendering for new local Windows terminals unless overridden.
Include the regression coverage and synchronized bilingual release notes.
Consolidate the existing active-mode flag helper in term/keyboard.rs without changing its logic. Tighten the term module allowance to 2713 lines, preserving the stricter peer baseline and all keyboard state regressions. Verified 209 core tests and architecture checks against a3d25c9.
Honor negotiated key modifiers and report the current keyboard flags.
Keep completion navigation and pointer scrolling aligned with visible rows.
Deliver completion and attention notifications to the live source pane,
with request-bound binary confirmation actions that reject stale input.
Synchronize bilingual changelog and release-note entries.
Keep the Antigravity detection rules and add the shared official icon catalog. Preserve negotiated Enter modifiers and restore native Windows Enter characters discarded by GPUI.
Keep keyboard mode updates in the active stack frame, preserve independent screen stacks, and bound keyboard pushes without changing saved titles. Isolate native input and notification delivery from their UI and policy callers.
Include the reviewed localization, SSH lifecycle, settings, completion, session, and notification updates. Local validation: 1062 GPUI tests, 209 terminal tests, translation allocation contracts, architecture and packaging checks. Native platform CI and the actual Antigravity input symptom remain under verification.
Repair platform-specific tests and Windows manifest resources, separate
completion snapshots, and split oversized modules without raising budgets.
Include the reviewed display-brand, icon-picker, and file-index changes.
Keep release asset compatibility and require explicit Preview publication.
Capture cross-platform startup, SSH credentials, preview packaging gates, and current SSH, answer-reader, math, and icon work. Remove unrelated product comparisons from public source comments.
Preview helper and shell tests pass locally. Native macOS/Linux build, test, and package validation remain pending in CI. Local Windows-only hooks cannot execute under WSL; content and workflow checks were run separately.
The legacy VT path emitted a bare 0x08 (plain backspace), and even the
kitty keyboard protocol path ignored it entirely, so terminals apps saw
Ctrl+Backspace as an unmodified backspace: pi/Claude Code deleted a
single letter instead of a word.
- kitty keyboard protocol active + Ctrl -> CSI u `CSI 127;5u` (127 is
the kitty Backspace keysym), so kitty-aware apps (pi) recognise the
exact key combination.
- Legacy VT path + Ctrl -> 0x17 (Ctrl+W); the managed PowerShell prompt
now binds Ctrl+w to BackwardKillWord.
- Alt prefix and plain 0x7f backspace behaviour are unchanged.
The user's $PROFILE was loading fine -- pwsh runs profiles before the
`-Command` dot-source, verified with a temporary profile -- but the
integration script then rendered Nebula's powerline over whatever the
profile had installed and discarded that prompt's return value. An
oh-my-posh or starship prompt therefore vanished, which reads exactly like
"Nebula does not load my profile".
Classify the captured prompt instead: PowerShell's built-in body always
references $executionContext.SessionState.Path.CurrentLocation, while
prompts installed through Invoke-Expression carry no ScriptBlock.File, so
the body is the only usable evidence. A user prompt keeps the visual and
Nebula contributes only OSC 133;A/D plus the NEBULA| title; a stock prompt
still gets the powerline. The ReadLine wrapper re-wraps prompt when someone
replaces it mid-session, so re-sourcing $PROFILE no longer silently ends
command-state reporting.
Git Bash had the same defect in PROMPT_COMMAND: a PS1 set by ~/.bashrc, or
rewritten each prompt by starship, was overwritten every cycle. Both
snapshots (rc load, saved-hook run) now hand the visual back.
Tests run the embedded scripts for real: three PowerShell cases through
powershell.exe (also replayed under pwsh 7.6.4) and two Git Bash cases.
Note: --no-verify again; the local line-budget hook stays red at HEAD.
REG_EXPAND_SZ values referencing variables from a later registry hive
(e.g. TEMP referencing USERPROFILE stored in Volatile Environment) kept
literal %VAR% text, so shells auto-created a %USERPROFILE% folder in the
working directory. Fall back to the process environment when the
referenced variable is not loaded yet, and add a regression test using
the real USERPROFILE so it passes on any machine.
Kuddev