Epic: macOS desktop backend
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
- 20/100
Direzione di ricerca
This is a tracking epic; start with crates/desktop-api/src/backend.rs and compare crates/desktop-linux/src/pure.rs with crates/desktop-windows/src/pure.rs. Comment first to agree on design and claim a sub-issue; a Mac is required for the backend work. Done means the sub-issues deliver macOS desktop control, permission handling, CI coverage, and updated crate map and install docs.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
size: L (epic) · first-timer: no
Please comment before starting so we can agree on the design and on who takes which piece. This is a tracking issue: most of the work happens in the linked sub-issues. You need access to a Mac.
Summary
Make Praxi's desktop control work on macOS: a bot can take a screenshot, read the accessibility tree and click/type in apps, with the OS permission prompts handled cleanly, and the macOS backend is built and tested in CI.
Why it matters
macOS is the second most requested platform. Today the daemon and UI are expected to build there, but desktop control, the part that makes Praxi an agent for your computer, does not exist. The pieces are small enough to be contributed separately, but they need one plan so they fit together.
Current state
crates/desktop-apidefines the OS-agnosticDesktopBackendtrait (backend.rs), snapshot/action types, the act guard (guard.rs) and the live-view contract (live_view.rs).crates/desktop-windows(UI Automation,SendInput, capture, live view, guard glue) andcrates/desktop-linux(X11/XTest, AT-SPI, live view) are complete references. Both keep OS-independent logic in apure.rsthat tests run without a display; do the same.crates/desktop-macosis a stub: itslib.rsis a four-line doc comment ("Accessibility API, CGEvent input, and screenshot capture"). ItsCargo.tomlsetsunsafe_code = "warn", whereas the workspace default isdenyanddesktop-windowsuseswarntogether withundocumented_unsafe_blocks.- The workspace is not built on macOS in CI (
CONTRIBUTING.md). The bundler target is NSIS only (apps/desktop/tauri.conf.json).
Sub-issues
- #172 macOS desktop backend: screenshots
- #173 macOS desktop backend: accessibility tree
- #174 macOS desktop backend: keyboard and mouse input
- #175 Build and publish Linux and macOS desktop bundles
- #179 Homebrew cask or formula
Work that has no issue yet (claim it here)
- Design note and crate scaffold. Choose the bindings (for example the
objc2family or thecore-graphics/accessibilitycrates versus hand-written FFI), and the capture API (ScreenCaptureKit versus the older window-list capture, given the macOS versions you support). Keep allunsafein one small, documented module with safe wrappers; the project denies unsafe elsewhere. - Permissions. Detect missing Screen Recording and Accessibility permission, return a typed error with a human-readable hint, and add the matching cards to the desktop app (both locales).
- Capabilities and guard. Implement
Capabilities, window/app listing and launch, and wire the act guard the way the Windows backend does. - Live view. Implement the
live_viewcontract for macOS after the basics work. - CI. A
macos-latestjob that builds the crate and runs the pure tests; later, the daemon and UI build.
Acceptance criteria for the epic
- On a supported macOS version a bot can: list windows, take a screenshot, read the accessibility tree of the frontmost app, click and type, and stop on the permission-denied path with a clear message.
cargo test -p desktop-macosand clippy pass on a macOS CI runner; the pure logic has fixture tests that run without a display or permissions.- The crate map in
CONTRIBUTING.mdand the install docs no longer call the backend a stub.
Out of scope
Notarization and signing (belongs to the bundles issue), Apple Silicon-specific performance work, iOS.
How to get started
Compare crates/desktop-linux/src/pure.rs with crates/desktop-windows/src/pure.rs, read the trait in crates/desktop-api/src/backend.rs, then comment here saying which sub-issue you take.
- Lingua principale
- Rust
- Stelle
- 0
- Fork
- 1
- Merge medio
- 6h 54m
- PR unite (30g)
- 152
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
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 emreocell/Praxi-Bot
-
area: desktop-ui enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Add an LLM provider presetApertaarea: daemon enhancement good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
Contribute example skillsApertadocumentation enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
emreocell/Praxi-Bot#168 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di emreocell/Praxi-Bot
Issue simili
-
priority middle
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
KATO-Hiro/AtCoderClans#13029 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
RustCrypto/formats#2544 ·
I maintainer di solito rispondono entro 1 giorno
-
bug ui
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
userFRM/egui-charts#3363 ·
I maintainer di solito rispondono entro 1 giorno
-
ada documentation mobile report
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
physicsdolphin/nv-uefi-unlocker#254 · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
kindraywind/rustnarok-client#1382 ·
I maintainer di solito rispondono entro 1 giorno