Skyvern-AI/rustwright：README 來源編輯指南

Skyvern-AI/rustwright 的 README 將專案描述為「Playwright's API on a Rust CDP engine , Chromium browser automation for Python & Node, no driver subprocess. (Alpha)」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「README」下寫到：A Rust rewrite of Playwright, a popular browser automation library. Rustwright is interoperable with Playwright but runs on an in-process Rust CDP engine , 2.55× faster, with no Playwright automation fingerprint. Alpha; Chromium-only.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「Why Rustwright?」與相關條目，可以先判斷它是否處理你的實際問題：Raw CDP, in Rust. A from-scratch async CDP client , not a wrapper around another automation library.。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：No Node driver subprocess. playwright-python launches and pipes to a bundled Node driver. Rustwright's engine is native , the browser-control code runs in-process.。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「Quickstart」等段落。可確認的線索包括：Rustwright is interoperable with Playwright , install it, change one import, and your existing code runs on the Rust engine.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： pip install rustwright python -m rustwright install chromium 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「Quickstart」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「Quickstart」段落提到：The Node binding drives an existing Chromium/Chrome , point Rustwright at it with RUSTWRIGHTCHROMIUM, CHROME, or CHROMIUM. Prefer to build from source? git clone the repo and run npm install && npm run build in node/.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：No Playwright automation fingerprint. The driver never loads, so its signatures never appear. See Automation detection.。