Add temporary clipboard paste and lifecycle validation
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 12/100
Direzione di ricerca
Start with the linked architecture doc (docs/architecture.md, the team section) and the earlier clipboard work in githubnext/ace2#122, #135, #139, #142 and #147, which this issue summarizes. The remaining scope is temporary image/file paste, image export, and Stop, disconnect and shutdown cleanup, built on Peekaboo's native clipboard transaction gate. Done means the clipboard is restored only when no paste was dispatched and the generation is still current, and hosted and local validation pass.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Status (Oct 6): persistent text, image and file-reference read/write are complete through githubnext/ace2#122, githubnext/ace2#135, githubnext/ace2#139, githubnext/ace2#142 and githubnext/ace2#147 (merge note). Remaining here: safe temporary image/file paste, image export, and the lifecycle (Stop, client death/disconnect, graceful shutdown) and hosted validation below. Draft githubnext/ace2#75 was closed as superseded; its timed 150 ms restoration must not ship. Unresolved-paste ownership validation is githubnext/ace2#78.
Complete the clipboard part of githubnext/ace2#8's input slice through Ace's embedded native bridge, under the channel owner's desktop-tools setting (see githubnext/ace2#8 and the current architecture).
Progress: Plain-text read/write landed in githubnext/ace2#122 (2c36c49). Bounded image reads landed in githubnext/ace2#135 (9c561ba): generation-consistent PNG/JPEG/TIFF previews, explicit orientation/transparency/size metadata, and the existing tool image result. Both have real native and model/durable-reopen proof. Image validation covered ten native cases (including rotation direction, transparent PNG, resizing, white JPEG fallback, absence and bounded refusals), exact persisted text/image results without new calls or usage, and private clipboard restoration with complete owned-runtime cleanup. Persistent text writes use githubnext/ace2#67’s existing unresolved-paste reservation gate; they do not preserve or restore prior contents. Literal text insertion’s temporary paste already landed in githubnext/ace2#67. Read-only file-list access landed in githubnext/ace2#139 (aa48e892): desktop_clipboard_read({format: "files"}) returns at most 32 ordered advertised local file URLs and decoded paths in a complete 24,000-byte JSON result, without opening files, checking existence, canonicalizing paths, or fetching resources. Nine actual native cases and one real model/durable-reopen check passed with private clipboard restoration and full owned-runtime cleanup. macOS filtered three unsupported URL forms before Ace could see them; these correctly returned absent and do not count as native guard coverage. AppKit rejected the legacy-format fixture before a product read, so that guard has source review only. Persistent image writes landed in githubnext/ace2#142 (a8417c9), validated at exact head 86e0c1e: one bounded execution-host image file, GUI validation, original PNG/JPEG/TIFF bytes and UTI, and the existing unresolved-paste reservation gate. Four exact-byte native cases and nine refusals passed, plus one real Claude Opus 5.5 write/read with distinct-worker durable reopen and one actual delayed-paste reservation refusal followed by admission after the exact receiver exited. All phases restored the original clipboard privately and cleaned every owned runtime. File-reference writes landed in githubnext/ace2#147 (f24257b). Safe temporary paste (including temporary image/file paste), image export, and the remaining lifecycle/hosted validation below stay open.
Expose explicit clipboard read/write and targeted temporary paste for text, images, and real file URL items. The clipboard belongs to the execution host. Keep clipboard access and the full temporary-paste lifecycle in Ace's long-lived GUI process, where OS clipboard permission applies; a short-lived native client cannot own reliable cleanup after Stop or disconnect.
Reuse Peekaboo's native clipboard transaction gate and generation claim. Capture all prior items/representations within a bounded preservation budget before writing, retain the exact focused-target receipt and snapshot lease, dispatch the guarded paste, and clean up even after caller cancellation. Restore prior contents only when both hold: no paste input was dispatched or meaningful consumption was observed, and the temporary generation is still current. Otherwise keep the replacement and its unresolved ownership (#78); a current generation alone is not enough, because a delayed paste may still be pending. Preserve a newer human update. Report delivery uncertainty and cleanup outcome separately, and verify the resulting target rather than claiming that dispatch proves consumption. A crash/force-kill cannot promise restoration; never restore stale persisted clipboard contents on a later launch.
The typed text clipboard extension added in githubnext/ace2#122 uses the existing authenticated Bridge transport and operation coordination. Extend that same boundary for images and files. Do not create another clipboard authority, authentication scheme, agent approval, or parallel message/history store. File-content payloads are not file-reference clipboard support: implement real multi-item file URLs. Return bounded text/image previews and file metadata; keep prior clipboard contents out of history unless explicitly read.
Done when real native and pi workflows read/write/copy/paste text, images, and files; temporary paste preserves previous multi-item contents and newer human changes; Stop, client death/disconnect, and graceful Ace shutdown exercise cleanup; local and hosted workspace behavior is verified. Handle native clipboard access refusal through Ace's existing OS permission experience. Keep unverified routes and inevitable cross-process clipboard races explicit.
- Lingua principale
- Swift
- Stelle
- 0
- Fork
- 0
- Merge medio
- 19m
- PR unite (30g)
- 107
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di githubnext/desktop-tools
-
ace documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
githubnext/desktop-tools#104 ·
I maintainer di solito rispondono entro 1 giorno
-
Linux support (meta)Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
githubnext/desktop-tools#136 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Select text in a PDFAperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
githubnext/desktop-tools#130 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
githubnext/desktop-tools#129 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
githubnext/desktop-tools#117 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di githubnext/desktop-tools
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
openwatersio/slackwater-ios#736 ·
I maintainer di solito rispondono entro 1 giorno
-
agent/sec-check help wanted security stage/010-actionable
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
hivecommons/hotshot#235 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Ranchero-Software/NetNewsWire#5495 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
Emanuele-web04/remodex#203 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 92/100
I maintainer di solito rispondono entro 1 giorno