Skip to content

Sync CE Personal Agent computer use and device synchronization - #227

Merged
Luhaozhu merged 4 commits into
mainfrom
sync/ce-20261112-computer-use
Nov 13, 2026
Merged

Luhaozhu merged 4 commits into
mainfrom
sync/ce-20261112-computer-use

Conversation

@Luhaozhu

@Luhaozhu Luhaozhu commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Purpose and behavior

  • Before: Personal Agent used screenshot-oriented computer controls, and chat read positions could differ between clients. Linked devices could not sync local chat changes or capability updates. Some hybrid knowledge searches lost result payloads.
  • After: Personal Agent can inspect a linked desktop, request approval for an action batch, and show per-step receipts. Linked devices sync chat changes and capability selections. Conversation updates appear in the live feed, and hybrid search retains dense and sparse result payloads. Sending returns the Personal Agent conversation to its latest message. Replies taller than the viewport open at their first line. The conversation router can identify plugins available to background tasks from the current grants. Page-triggered downloads on macOS show the system Save As panel.

Change walkthrough

  • Flow: src/backend/personal_agent/device_link/ dispatches operations through the desktop loopback API. capability_sync/ applies capability changes. conversation/live.py feeds the Personal Agent panel. core/chat/read_state.py records read positions for reminders. The follow-up derives the conversation scroll hook, per-turn router context, and the Tauri download handler from the upstream source.
  • Decisions: Use the existing local API for authorization and persistence. Keep operation receipts and device contract metadata so callers can detect stale clients and uncertain outcomes. Handle IME Enter at the window boundary so composing text does not submit chat input.

Risk and compatibility

  • Risk: high
  • Boundaries: Device operations use linked-device authorization. CE revisions ce_0043 through ce_0045 cover session claims, chat read state, and device link metadata. Element-level controls require the supported macOS driver.
  • Human review: Review device and account ownership, approval scope, receipt replay, and migration behavior on existing installations.

Verification

  • Evidence: The CE derivation passed required-file, forbidden-artifact, asset, brand, and license gates. The isolated CE import, OpenAPI, ORM, release regression, and frontend build checks passed. The SQLite migration check retained an existing row, ran the upgrade twice, and passed downgrade. The incremental diff passed git diff --check. At the current head, the CE API import and OpenAPI generation passed, and the CE production frontend built with Node.js 22. The upstream Personal Agent router, prompt, and capability suites passed 98 tests. All five LibreOffice archive entries match the existing pinned sizes and SHA-256 hashes.
  • Limits: The migration check used a synthetic row. Live desktop input and external tool effects were outside the CE migration check. Native Save As interaction and the replacement of an existing download target require manual review.

Recovery

  • Steps: Revert the sync commits and redeploy the previous revision if required. Review the database migration state before restoring data. Code rollback cannot undo an external desktop action.

Review follow-up

  • Disposition: This update extends the existing generated sync with device chat changes, capability sync, the live feed, and CE link metadata migration. The generated follow-up changes 13 files relative to the previous PR head. Human review is pending.

Community checklist

  • This is an allowed contribution or a maintainer-reviewed generated sync.
  • Public bilingual documentation is updated in both languages where applicable.
  • Links/code snippets were checked and CONTRIBUTING.md was read.

@Luhaozhu Luhaozhu changed the title Sync CE Personal Agent computer use and chat reliability Sync CE Personal Agent computer use and device synchronization Nov 12, 2026
@Luhaozhu
Luhaozhu merged commit 1d1b4b4 into main Nov 13, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant