mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-21 15:55:58 +00:00
0a3fed0643f482ec4d5fc287f83fa4568120abc8
799
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
fd2f885afd |
Restore a host's workspaces when its cached directory is evicted (#10318)
* fix(app): restore a host's workspaces after its cached directory is evicted A host could keep a current directory checkpoint in the replica cache with none of the rows it described. The daemon then answered "no changes" since that cursor, and the sidebar had no projects to place cached workspaces under, so every workspace for that host vanished and stayed missing across restarts. The cache already refused mutations for an evicted host, but it checked at the moment a mutation was queued. Eviction happens later, inside the serialized write, so anything queued before the eviction ran was still written, checkpoint included. The check moves into materializePendingChanges so it runs in the same serialized step that evicts, which also covers an eviction that lands while an earlier persist is still indexing the store. Checking at queue time was also losing good data: once a host was invalidated, every mutation was dropped, including updates accepted between a reconnect's baseline replacement and its write. Those are kept now, because the baseline is in the same pending batch. Version 1 checkpoints could have been written by that path, so they are no longer trusted. A reader discards them and keeps the cached rows, so the sidebar still paints from cache and each host re-syncs its directory once. Later launches resume incrementally. Both the race and the recovery live in the shared cache, so this covers iOS, Android, web, and Electron. It does not address two tabs or windows sharing one IndexedDB database, where another connection evicts the host. * fix(app): hold workspace updates that arrive while the directory cache loads A project update received while the cached directory was being read went straight into the replica. It advanced the project cursor before any refresh had established a baseline, and saved that cursor to the cache. On an install damaged before the eviction fix, that write replaced the version 1 checkpoint with a version 2 one before the reader could reject it. The refresh then asked for project changes after the live update, the daemon had none, and projects missing from the cache stayed missing across restarts. Agents already open a transaction before the cache load, so their updates are recorded and applied over the refreshed snapshot. Workspaces now do the same. An update during the load also stops the cached cursors being adopted, so the refresh fetches full snapshots, which is the recovery a damaged cache needs. * fix(app): advance directory cursors from live updates only after a refresh A live update moved the directory cursor whenever no refresh was in flight, including when no refresh had ever completed on the current subscriptions. If the first sync after discarding a version 1 checkpoint failed, the next project update saved a cursor at its own sequence with only that project stored. The retry asked for changes after it, the daemon had none, and the other projects stayed missing across restarts. The previous commit closed this window during the cache load only; a failed refresh reopened it. A live event's sequence covers everything before it only when a refresh completed on the subscriptions that delivered it, which is what satisfiedDemandSource already records. Live events now update rows either way but move the cursor only in that state, so a cursor never skips changes the client did not receive. Once a refresh completes, live updates advance the cursor as before. The sidebar recovery e2e fixture unwrapped the checkpoint only when it was version 1, so the version 2 writer made it abort before damaging the cache. It now reads either envelope and stores the damage as version 1, the format this branch stops trusting, so the test fails against the previous cache module and passes here. * fix(app): apply the eviction rule to malformed-row repairs Repairing a malformed directory row reads the checkpoint, drops the affected cursor, and writes the rest back. That write went straight to the row store through queueOperation, outside the eviction check in the regular persist path. If a write evicted the same host while the repair was reading, the repair stored a checkpoint for a host with no directory rows, the state this branch exists to prevent. All three repair writes now go through one helper that runs in the serialized writer and drops the checkpoint upsert when the host has been evicted since. The deletes still apply. * fix(app): record a host eviction only after its delete commits Eviction marked the host as evicted before deleteHost ran. If storage aborted that delete, the rows stayed stored but the mark remained. A malformed-row repair running behind it trusted the mark: it skipped the checkpoint update yet still deleted the row, leaving a workspace cursor with no workspace. The next refresh then resumed past that workspace. The mark is now set after the delete commits, so it always matches storage. A failed eviction leaves no mark, and the repair updates the row and its cursor together. |
||
|
|
d78cc90e4d |
Install bundled orchestration skills for Antigravity (#10273)
* feat(skills): install bundled orchestration skills for Antigravity Antigravity CLI (`agy`), App, and IDE do not scan `~/.agents/skills` or `~/.claude/skills` globally; they discover global skills one level deep from `~/.gemini/config/skills/<skill>/SKILL.md`. Gemini CLI already discovers `~/.agents/skills`, so targeting `~/.gemini/config/skills` only (instead of `~/.gemini/skills`) avoids duplicate skill entries in both Gemini CLI and `agy`. Appends `antigravityDir` at root index 3 in skill transactions so any in-flight pre-upgrade transaction manifest retains its existing backup indices, and includes `antigravityDir` in legacy Codex alias checks so symlinked roots are not retired. * fix(skills): unify install roots and keep rollback/updates resilient to unwritable targets - Replace separate per-target fields on SkillTargets with an ordered `installDirs` list plus `codexDir`, deriving status, sync, removal, legacy Codex alias checks, and transaction root indexing from one source while preserving pre-upgrade backup indices 0–2 (`codexDir` at index 2, additional install roots at index 3+). - Skip unreadable `add` entries with no backup during transaction rollback so an ENOTDIR/EACCES parent under `~/.gemini` does not fail rollback and leave a stuck transaction blocking later skills calls. - Ignore `ENOTDIR` in `removeSkill` (a skill cannot exist below a regular file). - Continue syncing remaining skills and install roots in `syncSkills` before throwing the first error so an unwritable `~/.gemini` does not block startup auto-updates from reaching `~/.agents` and `~/.claude`. * fix(skills): finish removing reachable skills during uninstall when one root is unreadable Continue across every target root in `removeSkill` and every managed skill in `uninstallSkills` before throwing the first error (matching `syncSkills`), while still reporting `EACCES` rather than ignoring it. * test(agent): synchronize stale-session retry before checking cleared run Replace the racy `setTimeout(0)` in `agent-manager.test.ts` with a deferred gate on `resumeSession`. Under CI load, `setTimeout(0)` could fire after the immediate retry had already resumed and started its new in-flight run, causing `hasInFlightRun(agent.id)` to read `true`. |
||
|
|
d5d385afa7 |
Show each provider's state in the list and open one provider page everywhere (#9661)
* fix(app): leave providers that are not installed out of the model picker An agent's own provider stays in its selector, labelled Unavailable. * feat(app): open a provider's detail as a Settings page or a sheet Settings → Providers now pushes a provider page, like Projects and Plugins; the model picker gear and setup keep a sheet. Both frame one body, ordered error, Enabled, Installation, Models, Troubleshooting, Danger zone, so the old sheet's sticky footer and Retry button are gone. Refresh lives once, in the Troubleshooting status row. The page header (back link, icon, title) moves into the shared settings kit so projects, plugins and providers line up on the same rails. * feat(app): show each provider's version, updates and faults in the list Each row now says how its provider is: version and model count, Update available, a spinner while an update runs, a red dot with the error, or Not installed / Disabled. Only a broken provider gets a dot, and a provider that is not installed has no switch, since the model picker already leaves it out. The kebab is gone; Remove lives on the detail. Rows read the same installation and update queries as the detail, so opening a provider costs no new requests. Hosts without providerInstallation still get a correct list from the snapshot alone. Add provider is a "+ Provider" button in the header and a muted last row; both open one sheet with search and catalog rows, replacing the tile grid. After Add, the new provider's detail opens. The row is the settings kit's detail row, which gains a leading icon, a hint status (spinner, error dot, or a held line) and a control before the chevron. The Unistyles test stub now applies withUnistyles theme mappings, so browser tests render components that read colours through the theme. * feat(app): open setup's provider pages over the setup card The detail and Add provider sheets take the setup card's frame and a back arrow, so they read as pages of setup instead of a sheet over it. The step is renamed "Your providers" to match the list it shows. * docs: describe the provider list and pages as they are now * fix(app): keep settings rows one height and on one icon rail on phones On touch layouts a switch reserves a 44px control, so in the provider list rows with a switch stood 10px taller than "Not installed" rows without one. Card rows now reserve a default control's height, the rule nested rows already follow. A compact SettingsRow wrapped with a full `gap`, which added 12px on top of the leading slot's margin: catalog icons sat 24px from their labels instead of 12px. The wrap only needs space between lines, so it uses `rowGap`. * fix(app): keep a provider row's error to one line A long or multi-line error wrapped the hint to two lines with the dot centred between them. The row cuts it to one line; the provider's page shows it in full. * fix(app): title a provider's Settings page like a project's The page title and the detail header both named the provider. The screen now titles it "Providers" and the page names the provider once, the way a project's page does. * fix(app): keep a settings row's switch out of the row's button The provider row's switch rendered inside the row's <button>. That is invalid markup, and keys reached both: Enter on the switch toggled it and also opened the provider's page, and Space on it opened the page without toggling. SettingsRowHeader now lays its press target under the row's content as a sibling of the control. The content lets presses through to the button and stays out of the accessibility tree, where the button's label already names the row. Hover is tracked on the row, so it holds over the switch. * fix(app): reserve a control's height only on rows that open something The previous change gave every card row a control's minimum height and the design doc said so, but rows built directly on settingsStyles.row (66 uses) never got it: a single-line row was 48px or 64px depending on which code path built it. The minimum now belongs to SettingsRowHeader, the row with an optional control slot, so a list where only some rows carry a switch keeps one height. SettingsRow and hand-built rows take their content's height again, as on the base branch, and the doc states the narrower rule. * test(app): give the Unistyles stub the light theme's full colours Since the stub started applying withUnistyles theme mappings, a mapping reading a colour the stub's theme lacked crashed: the markdown styles read colors.terminal and failed the plan card disclosure tests. The stub's colours now start from the light theme, with its own values pinned on top. * test(app): find the provider page's buttons in the compact sheet On compact layouts AdaptiveModalSheet puts its testID on the header only, so buttons in the page body cannot be found inside it. The spec looks them up on the page, as it did before the page moved into the sheet. * fix(app): let screen readers read a settings row's state line The row's button carries the row's name as its label, so only the title is hidden from assistive tech now; the hint below it (a provider's version, error or Not installed) is read again. The Enter-on-switch test now dispatches its key events synchronously inside one act. An awaited keyboard call let the Switch's animation run a frame after the test, which Vitest reported as an unhandled error and failed the run. * fix(app): don't open a provider's page after its Add sheet was closed Adding a provider waits for the daemon to probe it. If the user closed the sheet during that wait, the completed add still navigated to the provider's page. The add now remembers which sheet session started it and only opens the page if that session is still current. * fix(app): say Not installed for a disabled provider that is not installed A disabled provider's snapshot status is unavailable, so the row said Disabled even when the binary was missing. The installation inspection is checked first, so Not installed wins over Disabled. * fix(app): keep a saved provider choice visible when it is not installed The provider picker drops unavailable providers. A schedule or metadata-generation setting saved against such a provider then showed Select model. The picker now keeps the saved provider, labelled Unavailable, so the user sees what is set and can change it. * test(app): wait for an added catalog provider's probe before continuing Adding a provider opens its page only after the daemon probes it, which can outlast the default expect timeout on CI. * refactor(app): name the provider picker's connection and saved-choice options Callers passed a bare true to reach the saved-choice argument. * fix(app): show a provider page's loading and not-found states A provider page opened from its URL (a reload, a cold start, a shared link) rendered its title over nothing until the host's providers arrived, and forever when the id named a provider the host doesn't have. The page body now says Loading..., that the host is offline, that the providers couldn't be read, or that the provider isn't on this host, in the same notice card the provider list uses when it is offline. The page and both sheet frames share the body. * fix(app): don't call a just-removed provider missing while its page closes The daemon can publish the provider list without the removed provider before it answers the config patch, so the page said "This provider isn't on this host" until the answer arrived and it navigated away; in a sheet, through the exit animation as well. A page that has shown its provider now shows nothing once it leaves the list. The not-found notice is for a page that never found its provider. The removal e2e holds the config answer so it always sees that order. * fix(app): show the not-found notice when a provider is removed elsewhere The page hid the notice for any provider it had shown before, to cover its own Remove. A removal from another client, the CLI or a plugin then left the page blank with no way to tell why. The page now owns its Remove: while that runs and once it succeeds the body shows nothing, and any other absence says the provider isn't on this host. The removal e2e routes only the e2e daemon's socket, so the fixture's port-6767 guard stays in force. * fix(app): show progress on the provider page's in-flight buttons Remove, Add model and the diagnostic re-run now show their work on the pressed control, like the page's Refresh and Update: a spinner, no further presses and, on a labelled button, "Removing..." or "Adding...". Remove kept its label and only disabled itself, and the page went blank mid-removal: the daemon publishes the provider list without the removed provider before it answers the config patch, so the body had nothing to show and each frame's title fell back to the raw id. The removal now keeps the entry the user confirmed, and one hook feeds the frame's title and the body, so both keep showing the provider until the page closes. The in-flight state also starts after confirmation, not while the dialog is open. The diagnostic sheet's header icon buttons had lost the base branch's spinner and dimming; SheetHeaderIconButton now takes loading and disabled, the way Button does. * fix(app): don't leave a re-added provider's sheet stuck on Removing... The setup step and the model picker's gear keep a provider's sheet mounted after it closes, keyed by provider. A finished removal stayed set in that sheet, so adding the same provider back reopened it with Remove spinning and disabled. A finished removal now ends when the host lists the provider again. * fix(app): keep the composer's remembered provider in its picker The picker leaves out providers that aren't installed, except the one holding the picker's current choice. The schedule form and metadata page passed that choice; the new-agent composer didn't, so a remembered provider not installed on this host vanished from the picker and the trigger read "Select model" with no reason given. The builder now requires every caller to say what its current choice is, or null. * fix(app): guide a missing catalog provider's install and keep custom models while one fails A provider added from the Add provider catalog runs through the generic ACP client, which reports no installation, so its page said nothing when the CLI was missing. The page now shows the Installation section's Not installed row with Install opening the catalog's guide. A link the host supplies still wins. Custom models live in config, so the page lists them and offers Add model whenever the provider is enabled and installed, including while it fails. The provider's own models, and the search over them, still show only while it runs. * fix(app): make settings rows pressable on iOS and Android React Native 0.86 no longer exports StyleSheet.absoluteFillObject, and Unistyles' native StyleSheet copies it from React Native, so the spread was empty there. The row's press target then had no size: on Android, tapping a provider row or a Voice row did nothing. Web was unaffected because Unistyles' web StyleSheet still defines the key. Use StyleSheet.absoluteFill, as the rest of the app does. * fix(app): let setup's provider sheets leave out the close button again The base's sheet header rewrite dropped SheetHeaderView's showCloseButton, which the provider page and Add provider sheets pass when setup's back arrow is the only way out. Restore it on the header. * test(app): prove a refresh clears a failed update from the provider's row The update-failure journey now also walks the provider list: after Refresh on the page the row reads its version and model count with no error dot, and a refresh from another client clears a row that is open in the list. Without the provider.installation.update.cleared handling both row checks fail. The helper's Refresh now uses the page's Troubleshooting button, since Settings opens the provider as a page, not a sheet. * fix(app): show a catalog provider's install guide on hosts that cannot report installations A host without providerInstallation returns an unsupported installation, which the page passed through, so a catalog provider whose CLI is missing showed no Installation section and no guide anywhere. The guide is the app's own catalog data, so the page builds the same Not installed row from it on those hosts. |
||
|
|
4d29ee415a |
Show provider versions and run provider updates from provider settings (#9568)
* feat(providers): show installed version and install link in provider settings Providers can now declare `installation`: install and update links plus an `inspect` callback that reports installed state and an opaque version string. Built-in clients and plugin providers share one contract; plugins receive the daemon-resolved launch with `resolved: false` when the executable is missing, so they can report not installed instead of failing. The daemon calls `inspect` only on the new `provider.installation.inspect.request` RPC, never from availability probing, discovery or session creation, so a slow version probe cannot delay agents. Results are cached per client for 30s, deadlined at 20s, and links survive a failed probe. The app gates the provider sheet's Installation row on `server_info.features.providerInstallation`, so older hosts show nothing new. * feat(providers): show available updates in provider settings Providers can now declare `installation.checkForUpdates`, returning `current`, `available` with opaque `versions` and `message`, or `unknown`. The provider decides what counts as newer; Paseo shows its answer as written and never parses or compares versions. The check is its own RPC, `provider.installation.check_updates`, so the installed version never waits on a network lookup. The daemon caches a conclusive answer for an hour and an inconclusive one for 30s, shares in-flight calls, and deadlines the call at 25s, below the plugin RPC timeout. A throw or timeout comes back as `error`, which the app shows as inconclusive, never as up to date. The sheet's Refresh bypasses the cache. Codex and Claude Code read the release source their own updaters use: the Homebrew cask for cask installs, otherwise the GitHub latest release for Codex and the configured `autoUpdatesChannel` for Claude Code. `codex doctor --json` reports the same answer but scans local state and took close to a minute, so it is not used. Muse compares its build with the launcher's channel manifest, the same rule the launcher updates by. The install link now shows whenever the provider declares `installUrl` and is not reported installed: the Install button for `not_installed`, a quieter "Install instructions" link when the check failed or the provider only links to a guide. * feat(providers): run provider updates from provider settings Providers can declare `update(context)`, and the Installation section shows an Update button when an update is available. The daemon owns the operation: one per provider, joined by later requests, kept in memory past client disconnects, streamed to subscribers through an owned subscription, and aborted only when the daemon stops. The provider's answer is the outcome; the daemon adds no verification. After success it drops the cached inspection and update check and refreshes discovery, without restarting agents. Codex and Claude run their own `update` subcommand and pass the output through. Muse has no update subcommand, so it does not declare one. Updater output is capped at 64 KiB per update so a chatty updater cannot grow daemon memory. Starting an update requires daemon.manage because it runs commands on the host. * feat(providers): report installation for the remaining providers Copilot, OpenCode, Pi, Oh My Pi, Antigravity and Hoplite now show an install link and the installed version in provider settings. Each one declares only what its CLI offers: - Update checks ask the source the CLI's own updater reads: Pi's latest-version endpoint, `omp update --check`, and Hoplite's latest.json. Copilot and OpenCode resolve their release inside the binary, so they declare no check. - Updates run the CLI's own command: `copilot update`, `opencode upgrade`, `pi update --self` (leaves Pi packages alone), `omp update`. Antigravity and Hoplite document no self-update. OpenCode's success message asks for a daemon restart, because all OpenCode agents share one server that keeps running the old version. * docs(providers): document the provider installation contract Plugin authors get the contract in the provider guide, with a worked example that reports a version, checks for an update and runs the CLI's own updater, and every field, deadline and cache in the reference. The internal provider and plugin docs record why the three callbacks are separate, that versions are opaque, that Paseo adds no verification to an update, and how the plugin bridge carries and cancels each request. * chore(protocol): mark provider installation as shipping in v0.17.0 main is on the 0.16 beta series, and a promotion ships the tested beta's content without pulling from main, so this lands in the next minor. * fix(app): bound update output and show refresh failures in provider settings The screen appended every progress chunk with no limit while open, so a noisy updater grew memory and never showed the truncation note that a reopened screen shows. Progress now folds with the daemon's 64 KiB limit. A manual refresh stored its result and failure outside the queries the screen reads, so a failed refresh brought back the old answer with no warning. Refresh now runs through those queries. It passes staleTime 0 because the app's default staleTime of Infinity would otherwise answer from the cache. The not-connected error uses the translated string the i18n check requires. * fix(providers): keep update checks in step with the installed version A conclusive check is cached for an hour and was not tied to the version it answered for. After a CLI updated outside Paseo, settings showed the new version and still offered Update to it. When an inspection reports a different version, the cached check is dropped. Versions are compared for equality, so they stay opaque. The release comparison dropped prerelease suffixes, so Codex 0.200.0-alpha.1 looked current against 0.200.0. A prerelease now comes before the release with the same numbers. Two different prereleases of the same release are reported as unknown. * docs(providers): say when Update instructions shows * fix(providers): reuse a cached update check only for the version it answered The previous fix dropped the cached check after an inspection settled with a new version. On reopen the app sends inspect and check together, so the check answered from the stale entry before the inspection settled. A cached check now records the installed version it was computed against and is reused only when the current inspection, shared if in flight, reports the same version. * fix(app): refresh provider version after an update settles while disconnected The installation and update queries were invalidated only by a live succeeded progress event. A connection dropped mid-update delivered the settled operation as a snapshot on reconnect, which left the old version and Update on screen. A success the view saw running now rereads them whether it arrives as progress or as a snapshot. * fix(providers): keep update checks within their own deadline Tying a cached check to its version made every check wait for a fresh inspection, which could add the 20 s inspect deadline to the 25 s check deadline. A check now never starts an inspection. It waits on one only when the inspection is cached or already running and the check would reuse a cached answer. When it asks the provider, it records the version afterwards. * test(app): assert provider installation states are visible * fix(providers): share one update check when two clients reopen after a version change * fix(muse): report the build the update check compares Paseo reuses a cached update check while inspect reports the same version string. Muse reported 1.4.18 but compared its build (1.4.18-R8600.1), so a new build of the same release kept the stale "Update available" for up to an hour. The contract docs now say to include everything the check compares in the reported version. * test(app): scroll custom model rows into view before checking them The provider sheet now shows an Installation section above the model lists. At 390x1000 the custom model row sits under the sheet footer until scrolled. The spec checks that a long model id leaves its Remove button reachable. It had assumed the row needed no vertical scroll. * test(app): keep the custom model check sensitive to a Remove button pushed off the sheet scrollIntoViewIfNeeded on the Remove button scrolled the overflow-hidden model card sideways too, so the check passed with the long-id layout fix undone. Scroll only the Custom models heading into view, which moves the sheet vertically and leaves the card at scrollLeft 0. With the layout fix undone the spec now fails at 1200px and 390px again. * feat(app): offer provider updates whether or not an update check answers Update and Update instructions lived inside the row that appeared only after checkForUpdates answered, so Copilot and OpenCode, which declare update but no check, never offered either. A check is a convenience: the Updates row now shows for an installed provider that offers an update, keeps Update or Update instructions in place in every check state (none, checking, up to date, available, couldn't check), and shows what the check knows as a hint beside it. A provider that offers no update still shows the check's answer once it has one. The daemon already ran update without a check; a test now says so. * fix(app): let update output scroll inside the provider sheet on Android The output box is a ScrollView nested in the sheet's scrolling body. Android hands the drag to the outer ScrollView unless the inner one sets nestedScrollEnabled, so only the last 240px of a long update's output was readable. The tool-call detail views set the same flag. * fix(app): show one progress indicator per provider update and refresh While an update ran, the Update button and the update's row each showed a spinner. The button's spinner also widened it, and the row's leading spinner shifted the title when the update settled. The update's row now owns progress from the tap until the update settles: it shows the update starting before the host answers, so the indicator never moves, and the Update button only disables. Refresh blanked the Installation rows while the provider was asked again, then moved "Checking…" from the Version row to the Updates row. The rows now keep their last answers until the new ones arrive, and the Refresh button shows the refresh until both the models and the installation are read again. * fix(app): show a provider update's progress on its Update button The pressed button carries an action's progress everywhere else in Settings: Button's own loading state with a present-participle label, as Browser data's Clear and Project settings' Save do. Update now does the same, reading "Updating..." from the tap until the update settles, and the update's row holds only the output while it runs, then the result. This replaces the row-owned spinner from the previous commit, which no other surface uses. The installation's in-flight labels use three dots like their siblings. * fix(app): keep a running update's progress visible whatever the inspection reads Update carries the update's progress, but its row rendered only while the inspection read "installed". An inspection that ran during the update (on reopen or Refresh) could read loading, not installed or failed while the binary was replaced, and the sheet then showed nothing about the running update. The Updates row now stays while an update runs. * fix(server): show and update the provider CLI its agents launch The installation contract found the CLI on the daemon's PATH, while agents spawn the bare command with the provider's environment. A provider whose env sets PATH could launch one copy and show and update another, so an update succeeded while new agents kept the old version. The CLI is now resolved with the provider's environment. The section test's check-state table now always names the text it expects, so no case can skip its assertion. * test(server): name the provider PATH test for what it shows The availability check that gates a Copilot spawn still looks on the daemon's PATH, so the copy on the provider's PATH is not always the one agents launch. * test(antigravity-provider): read the version from the CLI, not its acp subcommand Antigravity now launches `agy acp --disable-telemetry`, so the launch the installation receives ends with the ACP subcommand. The version read drops it, since `agy acp --version` starts the ACP server. * feat(plugin): pass the inspected version to checkForUpdates checkForUpdates now receives installedVersion, the version inspect reported, and the daemon keys the cached answer on it. Before, each provider read its version a second time and the daemon recorded which version a cached check answered for, so a check could compare a different version than the one shown, and a plugin had to put everything its check compared into the reported version. An update check now waits for the provider's inspection (shared with a concurrent inspect, refreshed with it), answers Not installed or the inspection's error without asking the provider, and is asked again once the inspection reports a different version. * fix(server): clear a failed provider update when the provider is refreshed The daemon kept a provider's last update for its whole lifetime, so a failed update stayed the current update until a later update succeeded or the daemon restarted, and the provider looked broken after the user fixed it. A refresh of the provider's installation or update check now drops a failed result. A running update is never dropped. * docs(server): say which agents look up the provider CLI on its PATH * fix(server): tell open provider views when a refresh drops a failed update A refresh deleted the failed update on the daemon but sent nothing, so a view already observing the provider's updates, in this client or another one, kept showing the failure until it observed again. The daemon now pushes provider.installation.update.cleared with the dropped operation's id to every subscriber, and the app clears the update it shows when the ids match. |
||
|
|
69c6bd7464 |
Keep the model tooltip closed when opening the picker
Pressing the model picker shortcut now focuses search without opening the button tooltip. Attach picker hints to the shared trigger button so focus inside the picker stays independent. |
||
|
|
120df507a9 |
Start a workspace in an existing worktree, and branch off or check out any branch or pull request (#10190)
* feat(server): branch off a pull request and list every git worktree A workspace.create worktree source with action "branch-off" and a checkoutSource used to check the pull request out, because core took any change request as a checkout. Branch-off now fetches the pull request's head into a remote-tracking ref (origin/<head> for a same-repo head, paseo-pr-<N>/<head> otherwise) and starts the new branch there, with no upstream and no remote added. A request with no action still checks the pull request out, as older clients expect. checkout.worktrees.list returns all git worktrees of the repository, not only the ones Paseo created, so the New workspace screen can offer any of them. Bare and prunable entries are left out. Hosts advertise both through server_info.features: worktreeRefActions and checkoutWorktreeList. Older hosts ignore the branch-off action on a pull request, so the app must gate on the flag. * feat(app): pick an existing worktree, and branch off or check out a ref Isolation now offers Project directory (was "Local"), New worktree, and Existing worktree. Existing worktree is a local workspace at the chosen worktree's path, not a third isolation value, so plugins, preferences, and the create request still see "local". The list comes from checkout.worktrees.list, so it includes worktrees Paseo did not create. The ref picker gains Branches / Pull requests pills and a Branch off / Check out toggle with a tooltip per action. Branches default to Branch off and pull requests to Check out. On a host without worktreeRefActions the toggle is hidden and the defaults apply. Git keeps a branch in one worktree at a time. Picking a held branch in Check out mode moves to the worktree that holds it, and creating from a held branch that was never picked fails with an explanation. Without this the server would silently check out a "<branch>-1" copy. * docs: describe Existing worktree and Branch off / Check out * fix(server): give a fork pull request branch-off a base the repository has A branch off a fork's pull request stored the fork's head as its base, under refs/remotes/paseo-pr-<N>. Create PR then asked for a pull request into a branch the base repository does not have, and the ref piled up in base branch pickers because no remote owns it. The new branch now starts at the fetched head, kept under refs/paseo/change-requests/<N>, and its base is the pull request's base branch. A same-repository branch-off still stacks on the pull request's branch. A routed create_workspace with a prNumber and no mode checks the pull request out again, as before branch-off could start from a pull request. The worktree list skips a locked worktree whose directory is gone, since it cannot be opened. * fix(app): start an existing worktree's agent in that worktree Existing worktree created the workspace at the worktree, but the composer and terminal still used the project directory, so the daemon rejected the first agent as outside the workspace. The screen now derives one working directory from the isolation and uses it for the workspace, the composer, and the terminal. A worktree that left the list is no longer a choice. The ref picker names change requests the way the project's forge does, so a GitLab project shows Merge requests. The schedule form uses the isolation labels Project directory and New worktree. * fix(server): compare a fork pull request branch-off against the remote base The base was stored as the bare branch name, which resolves to the local branch first. A local main behind origin/main put upstream commits in the workspace's changes for its whole life, and a base branch the clone never fetched failed creation. The base branch is now fetched from origin and stored as its remote-tracking ref. * fix(server): take a pull request's base and a checked-out branch from the remote that has them A fork branch-off fetched its base from origin. In a clone whose base repository is upstream, origin is the user's fork or missing, so the base was stale or the create failed. The base now comes from the remote that served the pull request, and a failed base fetch falls back to the bare branch name. Check out of a branch that only a remote other than origin has failed with an unknown branch. The local branch is now created from the one remote-tracking ref with that name, tracking it, as git does. The fork branch-off test passes a git identity to commit-tree, which CI runners do not have. * fix(server): branch off a pull request from the remote that serves it A same-repository pull request's head was fetched into refs/remotes/origin. In a fork clone, upstream serves the pull request and origin is the fork, so the base refresh replaced the head with the fork's branch of the same name and the new branch started from code that is not the pull request. The head now lands under refs/paseo/change-requests/<N>, the branch starts there, and the base is fetched from the remote that served the head. A routed create_workspace that branches off a pull request is refused, as it is on the local host. * fix(app): branch off a plugin's base ref whatever the branch action setBaseRef chose the base but kept the user's Check out switch, so a plugin's base became a checkout or a held-branch error. A base is what a new worktree starts from, so setBaseRef switches branches back to Branch off. |
||
|
|
68cfad2c8a |
Add interactive permissions and session history to Antigravity (#10193)
* feat(antigravity): run sessions through the shared ACP provider Use Antigravity’s ACP server for workspace sessions, mode changes, approvals, and conversation history. Keep existing conversations importable and migrate saved Full access sessions to Default. * fix(acp): finish delayed history replay before sessions become ready Keep delayed load updates on the history side of the readiness boundary. Reuse the ACP catalog and configuration mapping to translate legacy Antigravity selections and document the approval requirements for scheduled runs. * fix(antigravity): preserve Full access in ACP sessions Keep unattended Antigravity runs working through the shared ACP permission policy. Commit a Full access change only when the session is idle and retire unanswered approvals when a turn ends. * fix(acp): cancel pending approvals when stopping a turn Send the approval cancellation when the client asks the agent to stop. Agents that wait for the approval response can then finish the turn, and late replies to closed approvals leave the session usable. |
||
|
|
808766ed7f |
Acknowledge workspace taps promptly and reduce destination mount work (#9887)
* fix(app): acknowledge accepted workspace taps before navigation Short taps finish before the delayed hold feedback paints, then navigation occupies JS. Paint accepted feedback on the native UI thread while retaining the existing press cancellation and delay rules. * fix(app): avoid persistent tint on selected docked workspace rows * perf(app): reduce workspace mount work and narrow panel subscriptions |
||
|
|
51baa2beb8 |
feat(claude): give Ultracode its own toggle (#10150)
Keep Ultracode independent of effort in the Claude composer and retain support for saved Ultra Code choices. Co-authored-by: fivetaku <zipsanyang.ai@gmail.com> |
||
|
|
50b2c7f9d9 |
Give every natively supported provider a docs page (#10114)
Supported providers is now an index: one list of natively supported providers and one list of ACP agents from the in-app catalog. Each natively supported provider has a setup page under /docs/supported-providers/, and the docs sidebar shows those pages as one collapsible item. /docs/claude-code, /docs/codex, and /docs/muse-code redirect to the new location. Also adds landing pages for fx and Hoplite, lists fx in the 0.16.0 changelog highlights, lists every docs page in llms.txt, and gives the plugin sidebar views page its frontmatter. |
||
|
|
2a10550a02 |
Paste copied reply text as displayed in plain-text targets (#10079)
* fix(app): preserve literal text in selection copy * fix(app): keep literal angle brackets in copied selection HTML Unwrapping a recognized URL left displayed text such as `<http://localhost:3000>` in the Markdown that feeds text/html. Turndown does not escape `<`, so the clipboard renderer turned it into an autolink and dropped the brackets. Escape `<` in the Markdown flavor. Describe the renderer/copy link contract in docs/markdown-renderer.md instead of restating the code. Co-authored-by: Dan Berindei <dan.berindei@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(app): keep recognized web links and table pipes in rich and plain copy Unwrapping recognized links in the shared copy DOM removed them from both clipboard flavors, so a copied `#12` lost its forge URL in rich paste. The renderer now marks recognized links with their own attribute: text/plain carries them as the text the reply showed, and text/html keeps them as links when they point to a web page. Workspace paths stay plain text in both. text/plain still emits tables as GFM syntax, so keep the cell-pipe escape in both flavors. Co-authored-by: Dan Berindei <dan.berindei@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(app): copy recognized Windows drive paths as text in rich paste The rich-paste link check accepted any URI scheme, so `C:\repo\x.ts` kept a link with an unopenable `C:` href. Keep recognized links in text/html only for http and https URLs. Co-authored-by: Dan Berindei <dan.berindei@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(app): keep split line-start Markdown literal in copied selection HTML Selecting from the `#` in `**C#**` to the end of the paragraph left `#` and ` for ...` as separate text nodes after unwrapping, so Turndown did not escape the heading marker and rich paste showed a heading. Merge the text nodes before serializing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Dan Berindei <dan.berindei@gmail.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
59ca1f5f77 |
Replace Desktop's own daemon on update after Desktop relaunches (#10067)
An in-app update and the startup version check again use the desktopManaged flag in paseo.pid, while Manage built-in daemon is on. A daemon that an earlier Desktop session launched is now replaced on update. A daemon that the user started through the CLI is still never stopped automatically. Closes #6385. |
||
|
|
f1f2509c12 |
Keep Android composer taps working after zooming a chat image (#10057)
* fix(android): keep composer taps working after pinching an image React Native counted two touches at the start of a pinch but received a native takeover cancellation for just one. Typing could then claim the responder and consume the first toolbar tap. Cancel the active contacts when the gesture handler takes over. * docs(android): describe the chat image fixture for the pinch regression |
||
|
|
f81bc2b5a3 |
Keep the prompt and whole reply when an empty chat reconnects mid-reply (#9723)
Recover missing timeline rows when a chat was empty before disconnect and live reply rows arrive before history catch-up. Keep the replica cache at schema version 1. Closes #9650. Supersedes #9626. Co-authored-by: Okan YILDIRIM <63511519+ragokan@users.noreply.github.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> |
||
|
|
3815e72359 |
fix(desktop): refuse browser screenshots with no painted pixels (#9807)
Viewport and full-page browser screenshots wait for a frame with non-transparent pixels. When the page does not paint within the existing capture budget, the tool returns screenshot_no_frame. Fixes #9810. Co-authored-by: monarchmaisuriya <monarchmaisuriya7600@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
91e7293773 |
Hide historical PR badges on the default branch (#10053)
Hide closed and merged requests on the origin repository’s default branch. Keep branch-based status matching for feature workspaces. Closes #9908. |
||
|
|
576d0320c8 |
Keep Android text at the window's density on Samsung DeX (#9995)
React Native 0.86 converts between px and dp with the density of the phone's built-in display, while Fabric lays out at the window's density. In a DeX window (240 dpi on a 360 dpi phone) every text box came out at two thirds of the height its text needed, so the text was clipped. Backport the rule from react/react-native#59087: right after React Native reads the display (when it creates the root view and on each configuration change), restore the window's density and keep only the display's size. Remove once the app runs React Native 0.89 or later with useWindowDensityForDisplayMetricsAndroid on. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
e5352c9890 |
fix: size controls by the primary pointer, not any touch screen (#9909)
* feat(desktop): size controls by the primary pointer, not any touch screen The desktop app gave touch-sized controls to every machine with a touch screen, including Windows laptops driven by a trackpad. In Electron, ask whether a mouse-like primary pointer drives the UI instead: Chromium reports a fine primary pointer for those laptops and a coarse one for a tablet with no mouse or trackpad attached. Browsers and native keep the touch-screen check, so an iPad keeps touch sizes with a trackpad attached. Swipe gestures still follow the touch-screen capability. Refs #9892 * feat(app): size controls by the primary pointer on every platform Replace the Electron-only check with one rule everywhere: touch-sized when touch is the primary input, `(pointer: coarse)`, rather than when a touch screen exists at all. WebKit keeps touch primary on an iPad with a trackpad attached, so iPad Safari stays touch-sized; Chromium reports a fine primary pointer for a touch-screen laptop driven by its trackpad, in the browser and the desktop app. Native is always touch-sized. `hasTouchScreen()` and its `maxTouchPoints` fallback had no other caller and are removed. Swipe gestures still follow the touch-screen capability. Refs #9892 * test(app): exercise pointer sizing through the media source * test(app): cover touch laptops with a primary pointer --------- Co-authored-by: Mohamed Boudra <boudra.moha@gmail.com> |
||
|
|
a8cadae0ee |
fix(app): keep saved hosts when one entry can't be read (#9847)
The host registry was parsed with a strict array schema, so one host or connection this build couldn't read failed the whole array. The loader then removed @paseo:daemon-registry, and every saved host and password with it. That happens after a downgrade, or once a newer build saves a connection kind this build doesn't know. - Hosts and connections are read one at a time. One this build can't read is skipped, and the other hosts load. - Skipped entries are written back on every save, so the build that wrote them still finds them. Removing a host also drops what this build couldn't read for it. - A value that isn't a JSON array is copied to @paseo:daemon-registry:unreadable instead of being removed. - The stored-password migration still moves a connection password to its host when that host also has an unreadable connection. |
||
|
|
33259746db |
Stop timed-out watcher setups from rescanning large repos every 5 minutes (#9828)
* fix(server): abort timed-out watcher setups and back off their retries A watcher subscription that missed WORKSPACE_GIT_WATCHER_SUBSCRIBE_TIMEOUT_MS was abandoned but its startup scan kept walking the tree to completion, and recovery retried every five minutes forever, repeating the full scan each time. On a CPU-starved host that kept dozens of directories rescanning. - FileObserver.subscribe accepts an abort signal that stops the startup scan and rejects; WorkspaceGit aborts setups at the deadline and on dispose. - Consecutive setup timeouts extend the recovery delay past the 5-minute ladder cap, doubling up to one hour; an accepted subscription resets it. Degraded polling keeps its 5-60 s cadence meanwhile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(file-observer): keep an aborted observation's backend from starting Aborting a subscription closes its observation, which can happen while start() is still reading the root. The backend then started after its close had finished, and the native backend opened a root watcher that nothing would close. Co-authored-by: Spencer Shulem <1703265+Spshulem@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(file-observer): abort a subscription mid-scan in the abort test The test aborted before the backend started, so it passed with the abort listener removed. A tree past the Linux directory limit makes a scan that keeps walking fail on the limit instead of rejecting with the reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Spencer Shulem <spshulem@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: Spencer Shulem <1703265+Spshulem@users.noreply.github.com> |
||
|
|
41c294c785 |
Queue agent messages until the current turn ends (#9757)
* fix(server): queue agent messages until the current turn ends Steering refusal could replace a running turn and cancel compaction. Hold agent-originated messages and notifications together until the recipient settles, retaining explicit interruption and acknowledging finish subscriptions only after dispatch succeeds. * fix(server): wake queued delivery at turn and permission checkpoints A pending follow-up must not hide the permission needed to finish the current turn. Wake ready batches on recipient state changes, let completion waits report permission checkpoints, and preserve admission order and session-mode boundaries when busy dispatches retry. * fix(server): publish autonomous readiness after run settlement Idle snapshots emitted while the autonomous run record still existed could not wake queued delivery. Publish terminal state after clearing that run, and keep already debounced busy retries ready for the next turn boundary. * fix(server): apply queued modes only after run admission Preparing a later mode group could change the running turn before busy admission rejected it. Carry the requested mode into the reserved run and apply it immediately before provider startup, leaving earlier and concurrently started turns untouched. * fix(server): keep later mode groups queued until turn end Dispatching every mode group at once prepared later modes against the preceding turn. Keep later groups pending and reject busy sends before changing mode, leaving mode validation outside run startup. * fix(server): deliver provider commands during queued turns Offer waiting messages individually through the provider-owned out-of-band path while a recipient runs. Recognized commands retain their existing behavior, while ordinary messages keep waiting without starting their dispatch observers. * fix(server): offer queued commands once while running Remember provider declines so timer retries do not repeat side effects or reinterpret a waiting message after provider state changes. * fix(server): defer commands that request a session mode An explicit mode belongs to a later turn. Keep those commands on the normal idle dispatch path so an out-of-band offer cannot ignore the requested mode or change the running turn. |
||
|
|
ade3817a45 |
fix(server): fall back to the next socket directory when the bind is refused (#9214)
A PASEO_HOME on AFS passes the socket directory checks, then refuses the Unix socket bind with EPERM, and the terminal worker failed to start. The worker now binds each eligible candidate in turn and moves on when the filesystem refuses the socket (EPERM, EACCES, EOPNOTSUPP, ENOTSUP). Other listen errors still fail the start. Fixes #9213 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
39db933e6b |
Keep submitted prompts scrolling down through existing momentum (#9806)
* fix(app): preserve submit scroll through existing momentum A prompt sent during an active gesture requested the bottom, but the older gesture cancelled that request when momentum ended away. Honor the still-sticky pending request on release while allowing a newer gesture to take ownership. * fix(app): keep delayed navigation behind user scroll intent |
||
|
|
ef146bc62d |
Browse, install and manage plugins from a built-in gallery (#9752)
* feat(app): browse, install and manage plugins from a built-in gallery Settings → Host → Plugins becomes a gallery with two tabs. Installed lists the host's plugins with on/off switches and pending updates. Browse lists the plugin directory with featured cards, categories, sorting and search. Each plugin has its own page with its screenshots, overview, details, install or on/off controls, and its own settings screens inline. Every install asks first, in a sheet naming the source and version, because installing runs the plugin's code on the host. Uninstalling also asks first; its confirm says what is deleted. The daemon fetches the directory from its configured registry (plugin.registry.list/get, gated by server_info.features.pluginRegistry). The app never fetches from the registry itself, so a host with a private registry shows that registry. README overviews render with the registry's overview contract (the same one the website uses): only https links and images work, and nothing is read as a workspace file. Before this, a word like "Node.js" became a broken relative link. * fix(app): refresh plugin failures and leave Settings cleanly from a plugin page The Installed row read the app-side evaluation error without subscribing to the registry, so a plugin fixed by Reload kept its "failed" badge. Rows and the plugin page now subscribe through usePluginEvaluationError. Leaving Settings with no remembered workspace replaced only the top stack entry; with a plugin page pushed on top, the Plugins list stayed mounted underneath and reopening Settings stacked a second copy. Dismiss the Settings entries first. * fix(app): keep Browse working as the registry grows, and test it end to end Registry listings now reach apps through an open wire schema (plugin.registry.list/get carry PluginListing*), and the daemon drops a listing it cannot read instead of failing the whole index. A registry that adds an artifact kind or bumps schemaVersion no longer breaks Browse on older apps. The gallery picks its opening tab once, so installing the first plugin keeps the user on Browse. README links open only https: the parser still autolinks bare http, www and email text, so a press checks the URL again. Adds a Browse e2e test against a local registry and Git repository: install from a row through the confirm sheet, stay on Browse, open the listing page, uninstall from it. * test(server): give the oversized-sibling diff refresh the same time budget as its siblings expect.poll defaults to one second, which a Windows git diff refresh can exceed. * test(server): wait as long as the other observer tests for native watcher events expect.poll defaults to one second; macOS FSEvents can deliver later than that on CI. * fix(app): keep a listed plugin's page usable after uninstalling it, and fetch the directory less An installed plugin's page finds its listing through the plugin, so uninstalling a directory plugin from the Installed tab left "not installed or listed" with no way back. The page now becomes the listing's page, offering Install again. Updates are re-checked when the host's plugins change and after a failed update, whose proposal named a revision that no longer exists. The directory, listing and update queries refetch on mount only once stale, so opening a plugin's page no longer refetches the whole directory and every update check. * test(app): install the plugin before opening Plugins in the busy-queue reload test Plugins opens on Browse when the host has no plugins and stays there after the first install, so a plugin installed through the daemon after the page opened never showed on Installed. * test(website): wait for hydration before scrolling to the hero in a short window The router resets the scroll position when the page hydrates. Scrolling to the mockup before that left it below the window, so its start line never came on screen and the opening scene never played. It failed 7 of 10 runs on webkit. * fix(server): show the registry setup error on Browse instead of asking to retry The registry's request headers were built inside the try around fetch, so a setup error such as credentials over plain HTTP came back as "Could not reach plugin registry. Retry later." Install already built them first. * fix(app): show plugin errors without the request details meant for logs A daemon RPC error's message ends with requestType=… code=…; the daemon's own text is in userMessage. Gallery alerts and toasts now show that text. * fix(app): show why an update failed on the plugin's page The update operation's failure was recorded under the plugin ID, but the page only read it to show the spinner, so a failed update looked as if nothing happened. The page now shows the error in its own alert, without the plugin's Failed badge, because the installed version keeps running. While an update is still available the button reads Retry. * fix(app): show a plugin page's update error only while the update is offered The failed update stayed in the operations store after the plugin was updated elsewhere or uninstalled, so the page kept saying the update failed. The page now shows it with the Update button it belongs to, as the Installed tab's Updates row does, and uninstalling forgets it. |
||
|
|
781cb8d5b0 |
fix(server): reject plugin timeline kinds the app cannot register (#7677)
timeline.append accepted any string as the row kind, but the app registers renderer kinds with /^[a-z][a-z0-9-]*$/. A plugin that appended a kind such as repro.card got a successful append, then its client setup threw in addTimelineRenderer and the whole plugin client failed to load. The daemon now rejects an append whose kind breaks that rule and names the rule in the error. The wire schema stays a plain string. Document the rule in the plugin docs. Fixes #7326 Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> |
||
|
|
a5015dba80 |
Pick the Usage host in Usage settings, and name it under the title (#9740)
* Share the host menu row, a plain sheet subtitle, and settings rows on a menu's rail - HostMenuItem: a host as a menu option (status dot, check), extracted from the sidebar Display menu so other host pages reuse it. - SheetHeaderSubtitle: one muted, truncating line under a sheet title. - MenuSettingsRows: settings rows that share a menu surface with menu rows put their labels on the menu rows' label rail (menuLabelInset). * Pick the Usage host in Usage settings, and name it under the title The host picker leaves the top of the Usage modal body. With more than one connected host, the cog's options lead with a Host row showing the current host; it opens a page of the same surface (a flyout when wide, an in-place page with Back in the compact sheet), so no sheet opens over another. The modal names the shown host in the header subtitle, muted and truncating, so a long host name never crowds the title. With one host, neither shows. Picking a host on a phone no longer dismisses Usage: only the body is keyed by host, so the compact sheet no longer remounts (and dismisses) on a switch. * A Usage host switch shows the new host loading, not the old host's cards The host's reports list was read with a list shape, which keeps the previous key's data while the next loads. Its key differs only by host, so after a switch the old host's cards showed under the new host's name until its reports arrived. Read it as a value. The title-row controls are keyed by host too, so a failed setting change on one host never shows on another. * Put menu settings rows on the menu's existing content rail menuRowContentInset already names the menu row's label rail next to the style it mirrors; drop the duplicate menuLabelInset. |
||
|
|
41d6dc9cd7 |
Reorder and turn off Usage cards, with matching sheet header and host picker controls (#9660)
* feat(app): reorder and turn off usage cards Usage cards default to alphabetical order. Drag a card by its handle to reorder it; the handle shows on hover on web and is always visible on native and compact layouts. A card's switch turns it off: the card collapses to its header and its windows leave the sidebar summary. Order and off state are device-local usage preferences. Inside a native bottom sheet, a drag gesture can now keep the touch: the sheet's content pan waits for the list's drag pan (react-native-draggable-flatlist gains `dragGestureRef`), and the sheet scroll stops while a drag is active. * feat(app): one icon button for every sheet header The sheet header's back arrow, close X and actions now render through SheetHeaderIconButton, which takes the header island chrome CompactHeader uses: 26pt frame and 16pt glyph on pointer, 44pt and 20pt on touch, muted colour, hover fill and tooltip. Edge buttons hang into the row padding so their glyphs sit on the content rail; the row keeps its 64pt height and the trailing actions shrink before the title collapses. Migrates the diagnostic, import session, model browser, changelog, plugin logs and sheet pane actions, and moves the tool-call and tool-call overview sheets onto SheetHeaderView. The Usage refresh and options buttons size their glyph from the header scope. adaptive-modal-sheet and the migrated sheets leave the raw-pressable burn-down list. * feat(app): host picker trigger and Usage host placement HostFilter renders the shared ComboboxTrigger, as in Settings, and truncates long host names. Sessions, Schedules, plugin surfaces, the labels manager and Usage pick this up together. The Usage modal puts the host picker at the top of its body on every form factor. The header is title, Refresh all, Settings, X, so the title stays whole on a phone. |
||
|
|
6f685d37be |
Command center tabs, recent workspaces, and archived workspace search (#9689)
* feat(app): command center tabs, recent workspaces, and agents in workspace search
The command center gets All · Workspaces · Files · Actions tabs under the search
field. Tab and Shift+Tab rotate them on web, a tab keeps the query and starts at
its top, and Backspace on an empty field returns to All. ⌘P opens on Files in
place of the Files scope chip.
All leads with the three most recent workspaces other than the open one. Agent
rows are gone: an agent's title now finds its workspace, which shows the agent on
a third line and opens that agent's tab.
The selection now follows the first result until the user moves it, so rows that
load above it do not leave it on the row below.
* feat(app): archived workspaces in command center search
A query in All or Workspaces now also finds archived workspaces through
agent history, appended after the active matches. Archived rows show the
archive time and an Archived badge, and open the workspace's latest agent
where it can be unarchived. Hosts without history search contribute
nothing. History's archived badge moves into a shared ArchivedBadge.
* fix(app): put the command center divider between the field and the tabs
The tabs belong to the results, not the search field, so the rule now
separates the field from the tab bar. The tab-rotation test also pins the
list's top, since the tabs no longer live inside the header it measured.
* fix(app): rank agent matches by quality, keep background workspaces out of Recent, explain Files off-workspace
- Score each agent together with its workspace's title and subtitle, so a
query split across them ("payments login") finds the row, and pick the
workspace's own match only when it is as good as its best agent match.
Across workspaces, match quality now ranks before own-versus-agent.
- Carry the workspace's background flag through the project summary and
leave background workspaces out of Recent workspaces, as the sidebar
does. A query still finds them.
- The Files tab outside a workspace says "Open a workspace to search
files" instead of "No matches".
* fix(app): settle command center selection, name agents only for loose matches, drop Files off-workspace
- Name a workspace's agent only when the workspace's own text does not match
contiguously and the agent does; a change-request hit is always an own match.
- Follow the first row only until every source for the query and tab has
loaded, then keep the selection by ID so reorders do not move it.
- Projects stay loading until an online host's workspaces have arrived; the
agent directory reports ready first.
- Outside a workspace there is no Files tab and All lists no files; the All
placeholder names only what the available tabs search.
- The unqueried Workspaces list follows the sidebar's Show background setting.
* fix(app): keep Projects loading honest, rank own-name matches by their agents too, refresh archived search after archive
- The command center waits for online hosts' workspaces itself instead of
through useProjects. useProjects held isLoading until workspaces
hydrated, but a failed workspace request never hydrates, so the
Projects screen could spin forever.
- A workspace that matches on its own name is ranked by the better of
that match and its agents', so typing into an agent title shared with
another workspace no longer drops it below that workspace and back.
- Archiving a workspace marks agent history stale. Archived search reused
a cached page that still listed the agents as active, so a workspace
archived in the last 30 seconds matched in neither list.
* fix(app): decide command center agent matches by match class
One rule now picks both what a workspace row shows and how it ranks. A
match falls in a class: every word at a word boundary, a word inside a
word, or scattered/misspelled. A row names its agent only when the agent
matches in a closer class than the workspace's own text, never on a
change-request hit. Rows rank by class, then own text ahead of an agent,
then score, then recency.
The previous rules chose the ranking candidate and the displayed
candidate separately, so each fix moved the edge case: positional tier
gaps named agents mid-word, and ranking by a hidden agent let a mid-word
name outrank a word-boundary one with nothing on screen to explain it.
* style(app): format command center workspace search import
* fix(app): settle archived search when no history host is reachable
With no searchable host online, the history query is disabled under a new
key, and keepPreviousData kept serving the old key's rows as placeholder
data. Archived search read that as still waiting for results, so the
command center selection never settled and followed every re-rank.
Previous results now stand in only while the query can run.
|
||
|
|
8ff657cd4a |
Command and file popovers stay against the composer, appear sooner, and stop jumping as results change (#9657)
* fix(app): keep the command popover against the composer as it resizes The popover lives in a portal and positioned itself from an asynchronous copy of the composer's rect. Any composer layout change painted first: a wrapped line overlapped the popover, cleared text left it floating above the composer, and a window resize left it at the old width, for one frame on web and up to seconds on Android under JS load. The popover now follows the composer's live size between measurements. Native reads the anchor's height on the UI thread every frame with a Reanimated frame callback; web commits the placement from a ResizeObserver with flushSync, before paint. The keyboard translate view in the portal becomes host-sized and box-none, so the popover moves inside it without leaving its parent's bounds (Android hit-testing). * docs(app): state where the native popover's fixed-bottom tracking stops holding The native frame follows only the composer's height so it never depends on whether iOS's native-driver keyboard lift has reached the shadow tree. The centered New workspace composer and width changes still wait for the rest measurement, as before. * fix(app): stop the native popover frame measuring a composer that left the tree When the composer unmounts with the popover open, the portal removes the frame a commit later. A busy JS thread holds that commit for many frames, and every failed measure() logged a Reanimated warning: 31 to 111 per layout swap on Android. A gate written from the anchor's ref callback arrives on the UI thread only after that same JS task, so the frame now stops on its first failed measure and falls back to the rest measurement. * fix(app): close the autocomplete popover while its retained panel is hidden A workspace stays mounted with display: none while another route shows, and the popover stayed open inside it. On native its frame then failed to measure the hidden composer, stopped tracking, and kept the stale placement after the user came back. The popover now closes with its panel and reopens with a fresh measurement. * fix(app): open the autocomplete list where it rests, with only the rows it shows The list mounted every result and then scrolled itself to the composer edge. On Android the scroll command reaches the screen one or two frames after the rows, so each open and each result change painted the far end of the list, or the selection 8 px low, before the resting frame. Mounting 115 commands also held the popover's first frame for 500 ms to 1 s. The list is now an inverted, virtualized list: its resting scroll position is the composer edge, and the first commit holds the rows that fill the popover. Each result set gets its own list, so a result change starts at the composer edge with the same bounded commit. Arrow-key selection is revealed through the list's own viewability and scroll-to-index. * fix(app): rest the autocomplete list at the far end when the selection wraps there Wrapping the arrow-key selection from the best match to the far end of a long list scrolled there over several frames, because the rows in between were not mounted. The list now gets a scroller that rests at the end the selection wrapped to, so the jump is one frame and mounts only the rows it shows. * fix(app): keep the selected autocomplete row in view when the popover gets shorter The row the arrow keys selected was brought into view once. A popover that then lost height, because the composer grew or the window shrank, cut that row off while Enter still chose it. The list checks the selected row again whenever its height changes. The test that counted scroll calls through patched Element prototypes now reads the list's resting scroll position instead. * fix(app): keep the autocomplete list when the same results arrive again The composer hands the popover a new list on every keystroke and refetch, often holding the results it already showed. The list started over for each one: a second mount before the filtered results, and a list the user had scrolled returned to its rest. A result set is now its options in order. |
||
|
|
1ee13fff51 |
Open image previews without a flash (#9698)
* fix(app): open the image preview without a flash
Opening an image preview showed "Couldn't load image", then the image
stretched to the whole window, then a blank frame, before the fitted image.
- The attachment preview URL hook returned null both while resolving and on
failure, so the lightbox showed the error while the URL resolved. It now
reports loading, ready, or failed.
- ZoomableImage rendered the image unfitted until its natural size arrived.
It now renders nothing until it can fit the image, and keeps it hidden until
it has loaded, so the image appears with its toolbar instead of after it.
- On Android, React Native lays a modal out at the screen minus the system
bars for its first frames, then grows it, so the backdrop snapped down; the
Modal wrapper sizes its content to the window from the first frame. The
lightbox's own SafeAreaProvider measured the dialog window, whose bottom
inset flips 24, 0, 24; it now reads the window insets via WindowSafeArea.
* fix(app): keep a reopened attachment preview from reading its released URL
Closing a preview releases its URL (revoked on web and desktop), but the hook kept the result for that attachment. Reopening the same attachment returned the revoked URL until the new lookup landed, so the image failed to load and "Couldn't load image" showed for a frame. The result is now dropped when its URL is released. The frame test also counts an image as visible only once it is painted, so a preview that never appears fails.
* test(app): wait for the stale file-link lookup to land before asserting
The test resolved the lookup and ended. React Query delivers the result on a timer, which could fire after jsdom was torn down ("window is not defined" failed app-tests in CI), and the no-open assertion could run before the stale result arrived at all.
* fix(app): show images the browser reports no natural size for
ZoomableImage waits for the image's size before painting it. React Native Web's Image.getSize never answers for an image that loads with a natural size of 0 (an SVG without width and height in some browsers), so the preview stayed blank with no error. The web build now measures the image itself and falls back to the browser's default replaced-element size, 300x150.
* fix(app): retry a reopened failed attachment preview from loading
The hook kept a failed result after its lookup was torn down, so reopening the same attachment showed "Couldn't load image" until the retry landed. Every cleanup now drops the result for its key.
* test(app): name the wait for a file-link lookup's delivery
|
||
|
|
6e2fee462f |
fix(server): fork from a response that background work outlives (#9627)
Forking from a reply failed with "This checkpoint changed after it was created" whenever a tool call started before that reply and finished after it, the shape of background Bash, Monitor, Task and Codex terminals. The projection keeps one row per tool call from its start to its latest update, so the row spans the reply, and the fork refused any copied row that spans the checkpoint. Copy such a tool call into the fork marked running: its state at the checkpoint can't be read back. Plugin cards that span the checkpoint stay out, and a cursor from another epoch or a reply that is gone is still refused. |
||
|
|
fc36438f03 |
fix(app): keep the Android chat still when a tap or long-press lands on its text (#9693)
* fix(app): keep the Android chat still when a tap or long-press lands on its text Chat text is selectable, and Android focuses selectable text when it is touched. React Native's ReactScrollView.requestChildFocus scrolls a newly focused child fully into view, so tapping a link or a word in a reply that was partly off screen, or long-pressing it, scrolled the timeline by up to a screen. The inverted timeline had a guard for this, but the guard depended on the inversion (#4090, then #7131), and #8717 removed it with the inversion. PaseoScrollView now skips that reveal when the focused view is selectable, non-editable text in touch mode. Inputs, and focus moved by a keyboard, still scroll into view. * test(app): assert the long press selects the word under the finger * fix(app): keep the Android chat still when a tapped reply keeps streaming Touched chat text keeps focus. When a streaming reply's text is replaced, ArrowKeyMovementMethod collapses the selection to 0, and the focused text view asks its scroll parent to reveal that line, which scrolled the timeline back to the reply's first line. PaseoScrollView now drops rectangle requests while touched read-only text holds focus with nothing selected. A drag on a selection handle still reveals. The input control test now makes its EditText selectable, as React Native's TextInput does, so it covers the editor check. * fix(app): keep the Android chat still when the timeline resizes after a tap ScrollView.onSizeChanged scrolls the focused view into view when the scroll view changes height. Touched chat text keeps focus, so a composer change below the timeline (a queued message being sent, a send error appearing) realigned the tapped reply. PaseoScrollView now skips that reveal while touched read-only text holds focus. |
||
|
|
42c7b7f886 |
fix(app): show the Android ripple on sidebar row presses (#9678)
* fix(app): show the Android ripple on sidebar row presses PressHighlight owns pressed feedback. Callers pass the pressed fill as highlightStyle and stop painting it themselves. iOS and web paint the fill; Android draws the platform ripple, clipped to the row's corners, after Android's 100 ms tap timeout. Rows that knock content out of the surface follow the fill through onHighlightChange instead of tracking press state themselves. Defaults borderWidth to 0 under clipped ripples: React Native 0.86 sends NaN when a style drops borderWidth, and an overflow-hidden view then stops painting (fixed upstream in facebook/react-native#57789). * fix(app): let PressHighlight own file header press feedback Changes-tree rows on Android painted their old flat pressed fill under the new ripple. Lock the Android row's caller border and press handlers in a test. * fix(app): skip the sidebar row press fill while renaming On web the row's pressable stays the responder for clicks inside the inline rename field, so it painted the pressed fill while the title was being edited. Drop highlightStyle while editing, as the press handlers already are. * fix(app): keep a press's fill and its report on the same edges usePressFill painted from the live pressed state but reported only at press-in and press-out, so the row fill and the badge ring could disagree when highlightStyle appeared or went away mid-press. A press now keeps the fill it started with; the paint and the report both come from that one state. |
||
|
|
be487ce65f |
Keep seeded dev daemon homes from resuming agents (#9672)
* fix(dev): keep seeded daemon homes from resuming agents * fix(dev): accept BOM configs when seeding homes * fix(dev): skip existing homes before reading seed config * fix(dev): seed homes from symlinked checkout paths * fix(dev): copy linked metadata into independent seed files |
||
|
|
d30aa16beb |
Retrying a message that failed before reaching the provider delivers it (#9580)
* fix(server): let a message rejected before dispatch be retried A send_agent_message_request with a messageId wrote its pending receipt before loading the agent, setting its mode, and starting the run. When one of those steps failed, nothing reached the provider, yet every retry with the same messageId reported agent_request_outcome_unknown. The pending receipt is now written at the dispatch boundary: the send awaits beforeDispatch after the agent is loaded and its mode is set, just before the prompt is handed to a run. A failure before that point leaves no receipt, so the retry submits the message once. Failures after it stay ambiguous, as before. Closes #9297 Co-authored-by: tmad4000 <1430007+tmad4000@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(server): lock that a send failing after dispatch is never resubmitted Scope the docs/hub.md retry sentence to direct sends: agent-sourced sends still write their receipt before queueing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(hub): scope the retry promise to failures before the run starts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(hub): name run startup as the ambiguous boundary Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: tmad4000 <1430007+tmad4000@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
a6a37b568d |
fix(app): correct composer glyph and placeholder tones (#9608)
* fix(app): mute labelled toolbar glyphs to match their labels Touch-sized composer glyphs rested at foreground while the label beside them used foregroundMuted. Use the existing label/icon glyph roles: a labelled glyph takes the muted tone, while an icon-only glyph keeps the foreground header-icon treatment from #8909. * test(app): keep toolbar tone coverage in the browser journey The component-level probe asserted the color prop handed to a stub icon in JSDOM, which the testing rules forbid. The real-browser journey already checks the rendered stroke and label colors for both glyph roles. * test(app): expect the muted tone for a labelled toolbar glyph The composer layout test still asserted the old foreground tone for the label role. * fix(app): quiet the composer placeholder to extra muted The empty composer painted its placeholder with surface4, a surface token, instead of a text tone. Use foregroundExtraMuted so it sits below foregroundMuted and above the background, and document the composer-specific exception. * test(app): clean up a composer tone fixture when setup fails The helper now releases the seeded agent and repository if navigation or the readiness check throws before the test owns cleanup. |
||
|
|
93d21e5612 |
Preserve the mobile sidebar when returning from Settings (#9641)
* fix(app): preserve mobile sidebar continuity through Settings Retain the sidebar for the Settings visit so Back resumes the original navigation surface without a new drawer animation. Native screen appearance owns the handoff because pathname and layout updates precede presentation. * fix(app): keep settings navigation imports lightweight Keep the Settings visit state accessible without loading native presentation hooks, and exercise continuity with a scrolled list and complete paint capture. |
||
|
|
02d3a05d2b |
Let scrolling cancel sidebar press highlights (#9637)
* fix(app): let scrolling cancel sidebar press feedback The independent native highlight gesture painted on finger-down before a tap was recognized and competed with Pressable for mouse clicks. Use the standard Pressable lifecycle with a short activation delay so scrolling cancels pending feedback. * fix(app): show press feedback on the usage summary The summary only styled hover, leaving touch presses without visual acknowledgement. Share the standard delayed press primitive and paint its pressed state before opening Usage. * fix(app): keep floating action press feedback opaque Press styles replace the surface background. Give floating actions a solid pressed fill rather than a translucent overlay tint, and verify held feedback and release through the standard pressable. |
||
|
|
2a9395e2d1 |
Light plugin themes and Pure Black keep their selected and hovered rows readable (#9579)
* fix(app): derive theme states and plugin fills so light and Pure Black themes stay readable Hover, selected, the neutral fill and tertiary text were colors a theme picked by eye, and plugin palettes filled them by borrowing `ring` and `border`. A light plugin theme got a dark selected row under dark text, Pure Black's hover barely separated from its surface, and light terminal ANSI white was white on white. States are now fixed WCAG-contrast steps from the surface they sit on, toward the foreground, derived in styles/derive-colors.ts. Plugin themes derive their neutral fill and tertiary text instead of aliasing `ring` and `border`, and may set an optional `sidebar` color. The web focus outline follows the theme's `ring`, and light terminal white and bright white are derived to read on the background. Tokens with no consumers are removed. Existing plugin themes change look with no author action, and the composer placeholder uses foregroundMuted like every other placeholder. Co-authored-by: Nathan Green <342098+nathansgreen@users.noreply.github.com> * fix(app): accept alpha hex in plugin theme colors when deriving The plugin schema accepts #rgba and #rrggbbaa, but contrast derivation parsed only opaque hex and threw, which would crash rendering for such a theme. Derivation now reads those colors as the opaque color they sit on. * fix(app): keep derived plugin fills and tertiary text readable on low-contrast palettes A fixed contrast step for the neutral fill left text on message bubbles, secondary buttons and badges at 2.6:1 on a dark palette whose body text is 4.75:1, and the fixed fade made Solarized Light tertiary text 1.92:1. The fill step is now bounded by the text it carries and tertiary text has a floor. The plugin reference states the minimum Paseo version for sidebar and that the terminal white is derived on light themes only. * fix(app): keep the derived neutral fill visible when a theme's own text is quiet Bounding the fill by text contrast could reach a step of 1 or less on a palette whose body text is under about 3:1, returning the page background itself. The step now has a minimum. * docs(app): state the trade-off between the neutral fill step and text contrast Below about 3.8:1 body text the fill keeps its minimum step and text on it falls under 3:1. The comment now says so and a test pins both outcomes. * fix(app): leave the light terminal's ANSI white as it was ANSI white is both text and a cell background, so no single palette value is readable in both roles; making it readable as text broke black text on white cells. That needs a contrast rule in the terminal renderer, so light white and bright white return to their previous values and the derivation and its test floors are removed. * feat(plugins): make derived theme colors overridable Sidebar passive text was derived against the page even though timestamps render on hover and selected surfaces. Derive it against the resolved state surface and let contributed themes override each derived semantic role explicitly. --------- Co-authored-by: Nathan Green <342098+nathansgreen@users.noreply.github.com> |
||
|
|
85ce1aa828 |
fix(app): preserve settings scroll through appearance changes (#9605)
Preserve settings scroll and form edits across appearance changes while refreshing numeric typography at text and input leaves. Normalize displayed font sizes explicitly after commits. Closes #9600 Closes #6931 Closes #6915 Co-authored-by: Josh <joshuaamayer@gmail.com> |
||
|
|
cf9eaa8d29 |
Forge links use the daemon-resolved host and parent repository (#9576)
* fix(forge): build web links from the host and repository the daemon resolves The app built forge links by parsing the origin remote itself, so an SSH config alias (git@github.com-work:...) produced https://github.com-work/... and a fork checkout sent #123 to the fork instead of the repository that owns the numbers. The daemon now publishes `forgeWeb` { host, referenceRepository? } on the workspace descriptor and on checkout status, and the app builds every forge URL from it. The host is the ssh -G resolved cloud host. referenceRepository is the fork's parent, read through an optional ForgeService.getReferenceRepository (GitHub, GitLab, Gitea family). Branch and file links stay on the origin repository because a feature branch usually exists only on the fork. Old daemons omit the field and the app derives links from the remote as before (tagged COMPAT(forgeWeb)). * fix(forge): keep the published web location tied to its remote and retry failed parent lookups - A web location resolved for one origin remote is no longer published after `git remote set-url`; it returns when the next forge refresh resolves the new remote. - The GitHub parent lookup rejects on a gh failure instead of returning null, so a network error is retried rather than cached as "this repository has no parent". - The pull request status poll retries a due lookup, so an idle workspace recovers without waiting for a forced refresh. - Workspace snapshot fixtures now expect `forgeWeb` for github.com remotes. * fix(forge): look up a fork's parent once per remote, on any checkout - A successful parent lookup is kept for the life of the remote instead of being repeated by every forced refresh (each push, fetch and branch switch). - The lookup no longer waits on the pull request status's auth state, which is "no_remote" on a detached HEAD; a failed or signed-out lookup is retried on the next forced refresh or poll. * fix(forge): resolve the new remote's web location when origin changes `git remote set-url` reaches the daemon as a git-only refresh, which stopped publishing the old remote's forgeWeb but never resolved the new one, so links fell back to parsing the remote. A git refresh that finds the remote changed since the last forge refresh now runs a forced forge refresh, which also probes a newly seen SSH alias. * fix(forge): keep the alias-resolved host when a failed parent lookup is retried The poll's retry resolved the forge with the synchronous resolver, which reports the raw SSH alias as the host. A lookup that settled on retry then published and kept `github.com-work` as the web host. The retry now uses the async resolver, like the forge refresh, so the host means the same thing on both paths. * fix(forge): treat a Gitea or GitLab API error body as a failed parent lookup `tea api` exits 0 on HTTP errors, so an error body parsed as a repository without a parent and was cached as "not a fork". The repository schemas now require the repository's own name, so an error body rejects and the lookup is retried. The shorthand provider also keys its context on the forgeWeb strings, so unrelated workspace updates no longer re-render every Markdown message. * fix(forge): keep the parent lookup off the workspace refresh path * fix(forge): keep a parent answer that lands during a refresh * test(forge): make the parent lookup tests Windows-safe * fix(forge): drain the background parent lookup on dispose * test(forge): retry temp cleanup after the poll lookup on Windows |
||
|
|
a30b784eb2 |
feat(plugins): let plugins add items to sidebar workspace rows (#7645)
Plugins can register workspace-row badge render slots, control them from a separated Show menu group, and use the shared WorkspaceRowBadge UI. Co-authored-by: Jacek Tomaszewski <jacek@fullstack.house> |
||
|
|
8dc979ec2f |
Shift+Tab in the iPad composer no longer inserts a tab (#9561)
* Shift+Tab in the iPad composer no longer inserts a tab On iPad with a hardware keyboard, Shift+Tab in the composer cycled the agent mode and the composer also inserted a tab. The native window reports presses to JavaScript after the text control has handled them, so the shortcut pipeline cannot prevent the default. The hardware keyboard source now claims, up front, the Shift and Option shortcuts whose binding is active in the current focus scope, and recomputes the claims when the focus surface or command center changes. iOS registers them as key commands so the text control never sees them. The window still emits the press, so the shortcut runs once. Closes #9468 * Claim every step of a rebound chord shortcut A binding rebound to a chord such as Mod+J Shift+Tab only claimed its first step, so finishing the chord in the iPad composer still typed a tab. * Claim only the first step of a chord shortcut Claiming every step of a chord held keys like Shift+A for as long as the chord's binding was active, so the composer could no longer type a capital A. A later step is a shortcut only while its chord is in progress. * Expect no Option claims now that iPad tab switching uses Cmd+Shift Main moved tab switching on Apple platforms with desktop bindings to Cmd+Shift+[ / ], which text controls do not type, so the default claims are only Shift+Tab while the composer is focused. |
||
|
|
7791dcee3b |
Docs: document the public iOS TestFlight beta on the Updates page (#9553)
* Document the public iOS TestFlight beta and how to get betas on every platform * Show the TestFlight beta on the download page's Beta view |
||
|
|
536846eb60 |
fix(omp): persist the resumed session identity when importing (#8854)
OMP import listings return a session file path, and the import helper stored that path as both sessionId and nativeHandle. Records then carried a path in sessionId while runtimeInfo carried the real id, which breaks identity-based lookups and makes a later import of the same file look unrelated. Prefer the resumed session's own describePersistence() identity and keep the listed handle as nativeHandle, merging metadata so provider-specific fields survive. |
||
|
|
b5c25e5c10 |
fix(opencode): discover V2 tools from bound session catalogs (#9426)
Fetch tool definitions for the bound session instead of the global manifest so plugin-contributed tools can be registered and invoked. Preserve global discovery for legacy callers and existing session filtering and execution authorization. Cover session-only tool discovery, invocation, child inheritance, disabled and unrelated sessions, unbinding, and plugin reload. |
||
|
|
9e607a3aa3 |
fix(app): restore physical arrow keys in Android terminals (#9407)
* fix(app): send hardware arrow keys to the terminal on Android TextInput.onKeyPress is built from the IME input connection, so physical arrows never reach it and fell through to the hidden input as caret movement. The hardware module now claims arrows while the terminal input (nativeID) has focus, and the input forwards them to the PTY with their modifiers. * test(app): guard Android terminal hardware arrow delivery Exercise physical arrow ownership through a real Android window and editable, including repeats, modifiers and ordinary text-field editing. The terminal case fails on main because Left moves the hidden caret; the following typed character is then discarded as a replacement. Co-authored-by: moevis <moevery@gmail.com> --------- Co-authored-by: moevis <moevery@gmail.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> |
||
|
|
a4878656e2 |
fix(pi): track resumed pi-subagents runs and transcripts (#9261)
* 修复 Pi 恢复子任务的状态和对话跟踪
关联 #9200。
改动:
- 仅在 action:resume 确认成功启动新的 single async run 后登记独立子任务条目,按新 run ID 和 asyncDir 跟踪状态,拒绝失败及管理调用产生的假条目。
- 将对话去重从文件级调整为子任务条目与文件组合,支持恢复运行复用 session JSONL,避免旧通知结束新运行。
- 扩展原适配器回归测试,并附脱敏的命令输出、真实工具结果和 macOS Electron 截图,未改 UI、协议或共享生命周期。
实际验证:
- 原适配器下恢复条目回归为 RED;恢复旧文件级去重后共享对话回归为 RED。
- 基线
|
||
|
|
83f4ef9909 |
Restore a workspace's agents when unarchiving it (#9210)
* refactor(server): share one timestamp across workspace archive * fix(server): restore workspace agents when unarchiving workspace * fix(server): persist workspace recovery before restoring agents Remove unused undo-list tracking and pass named restore requests. A failed workspace record write leaves its agents archived for retry. |
||
|
|
97d39a0158 |
docs(release): say how changelog highlights are ranked
The highlight order of 0.16.0-beta.1 was wrong twice: first in the order the pull requests were collected, then with the maintainer's four named items on top in the order they were typed, which pushed Background tasks to fifth. The doc only said "biggest first", so there was no test to apply. Changelog ordering now owns the ranking: reach and frequency, four groups, and what to do with a maintainer correction. The entry puts Background tasks back at the top; no wording changes. |