Record your screen, ship a demo. Free and open-source, GPU-accelerated, no watermarks, no subscriptions. Windows, macOS, Linux. Actively maintained.
TypeScript cross-platformelectronffmpegopen-sourceproduct-demorustscreen-capturescreen-recorderscreen-recordingscreen-studioscreencastspeech-to-texttypescriptvideo-editingvideo-editorwaylandwgpuwhisper
docs: register the MCP server with a placeholder executable, not the macOS path
EtienneLescot095332269c94
diff --git a/README.md b/README.mdindex ef31cfe08..17e10378d 100644--- a/README.md+++ b/README.md@@ -74,10 +74,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenThe skill sets everything up: it installs OpenScreen if it is missing (once youagree), connects its MCP server, then asks you to open a new session and say*"continue the OpenScreen demo"*, the one step an agent cannot do for itself.-By hand, it is these two commands, with the executable of your system:+By hand, it is these two commands, where `<executable>` is the app's executable+on your system ([where to find it](https://getopenscreen.com/docs/cli/#running-the-cli)):```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcpnpx skills add getopenscreen/openscreen --skill openscreen-demo```@@ -85,8 +86,8 @@ From then on, ask: *"Add a video of this change to the PR."* The agent plans thestoryboard, records the app, edits the take with OpenScreen's own editing tools,exports the MP4, checks it frame by frame, and attaches it to the pull request,where reviewers watch it in place. Ask for a launch demo instead and it drafts a-post for X, which it publishes only once you say yes. The executable on Windows-and Linux, and the other clients, are in [AI editing](https://getopenscreen.com/docs/ai-editing/#letting-an-agent-make-the-whole-video).+post for X, which it publishes only once you say yes. Codex and the other clients+are in [AI editing](https://getopenscreen.com/docs/ai-editing/#letting-an-agent-make-the-whole-video).## Installationdiff --git a/skills/openscreen-demo/SKILL.md b/skills/openscreen-demo/SKILL.mdindex 2bfdfb242..fcb634796 100644--- a/skills/openscreen-demo/SKILL.md+++ b/skills/openscreen-demo/SKILL.md@@ -18,7 +18,7 @@ You need the tools `startRecording`, `stopRecording`, `exportVideo` and `getFram| OS | Executable ||---|---|-| Windows | `%LOCALAPPDATA%\Programs\Openscreen\Openscreen.exe`, or `C:\Program Files\Openscreen\Openscreen.exe` |+| Windows | `%LOCALAPPDATA%\Programs\Openscreen\Openscreen.exe`, or `C:\Program Files\Openscreen\Openscreen.exe`. The Microsoft Store version has no fixed path to register: if it is the only one installed, offer the installer below || macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Linux | `openscreen` on the PATH, or the AppImage |diff --git a/website/docs/ai-editing.md b/website/docs/ai-editing.mdindex 587191f21..d61ecb570 100644--- a/website/docs/ai-editing.md+++ b/website/docs/ai-editing.md@@ -89,11 +89,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenThe skill installs OpenScreen if it is missing, once you agree, and adds its MCP server. It then asks you to open a new session and say *continue the OpenScreen demo*: an agent only gets new tools in a new session. To set it up by hand instead:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-The executable on each system is listed in [Running the CLI](./cli.md#running-the-cli).+`<executable>` is the app's executable, listed for each system in [Running the CLI](./cli.md#running-the-cli). Other clients, Cursor for one, take a stdio server with the executable as `command` and `["mcp"]` as `args`.- **No port, no token, no setting.** The agent starts the process itself, with your rights, as it would run `openscreen record`. So it can record your screen and edit without the **MCP edits** switch.- **Each take becomes a new project** in your project list, zoomed on its clicks as a recording made in the app is: clicks close in time and on screen share one zoom, and the first seconds and the end stay on the whole screen. Every edit the agent makes is saved to the project's file. Its undo is the checkpoint the agent takes, which lasts until the agent's session ends. Only the 20 most recent checkpoints are kept, so an older one can be gone sooner.diff --git a/website/docs/cli.md b/website/docs/cli.mdindex 26d0f19c9..2c4cdfbe1 100644--- a/website/docs/cli.md+++ b/website/docs/cli.md@@ -30,8 +30,9 @@ The CLI and the `.openscreen` project format can still change in breaking ways b|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Windows installer | `Openscreen.exe` in the folder chosen during setup: `%LOCALAPPDATA%\Programs\Openscreen\` for an install for the current user, `C:\Program Files\Openscreen\` for all users |+| Microsoft Store | None fixed: its folder changes with every Store update, so a script or an agent has nothing stable to point at. Use the Windows installer for the CLI || Linux `.deb`, `.rpm`, `.pacman` | `openscreen` |-| Linux AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |The examples on this page write `openscreen`. On macOS and Windows, use the full path or an alias:@@ -41,7 +42,7 @@ The examples on this page write `openscreen`. On macOS and Windows, use the full```- `openscreen help`, `--help` or `-h` prints the usage.-- Chromium switches placed before the subcommand are skipped. If Chromium's sandbox cannot start on the host, run `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`.+- Chromium switches placed before the subcommand are skipped. If Chromium's sandbox cannot start on the host, run `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`.- CLI runs do not take the app's single-instance lock, so they work while the desktop app is open.- From a source checkout, build the app and its native helpers as [Build and packaging](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md) describes, then run `npm run cli -- <command> [options]`.diff --git a/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.mdindex e1f6e6be5..79b268bca 100644--- a/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/de/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenDer Skill installiert OpenScreen, falls es fehlt, sobald du zustimmst, und fügt seinen MCP-Server hinzu. Danach bittet er dich, eine neue Sitzung zu öffnen und *continue the OpenScreen demo* zu sagen: Ein Agent bekommt neue Werkzeuge nur in einer neuen Sitzung. So richtest du es stattdessen von Hand ein:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-Die ausführbare Datei für jedes System steht unter [Die CLI ausführen](./cli.md#running-the-cli).+`<executable>` ist die ausführbare Datei der App; die jedes Systems steht unter [Die CLI ausführen](./cli.md#running-the-cli). Andere Clients, etwa Cursor, nehmen einen stdio-Server mit der ausführbaren Datei als `command` und `["mcp"]` als `args`.- **Kein Port, kein Token, keine Einstellung.** Der Agent startet den Prozess selbst, mit deinen Rechten, so wie er `openscreen record` ausführen würde. Deshalb kann er deinen Bildschirm aufnehmen und bearbeiten, ohne den Schalter **MCP-Änderungen**.- **Jeder Take wird zu einem neuen Projekt** in deiner Projektliste, mit Zooms auf seine Klicks, wie eine in der App gemachte Aufnahme: Zeitlich und räumlich nah beieinanderliegende Klicks teilen sich einen Zoom, und die ersten Sekunden und das Ende bleiben auf dem ganzen Bildschirm. Jede Änderung des Agenten wird in der Projektdatei gespeichert. Rückgängig macht sie der Wiederherstellungspunkt, den der Agent anlegt und der bis zum Ende seiner Sitzung besteht. Nur die 20 neuesten Wiederherstellungspunkte werden behalten, ein älterer kann also früher verschwinden.diff --git a/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/de/docusaurus-plugin-content-docs/current/cli.mdindex 9c87b094d..124aa1dfe 100644--- a/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/de/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ Die CLI und das Projektformat `.openscreen` können sich zwischen Versionen noch|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Windows-Installer | `Openscreen.exe` im Ordner, der bei der Einrichtung gewählt wurde: `%LOCALAPPDATA%\Programs\Openscreen\` bei einer Installation für den aktuellen Benutzer, `C:\Program Files\Openscreen\` für alle Benutzer |+| Microsoft Store | Kein fester Pfad: Der Ordner ändert sich mit jedem Store-Update, ein Skript oder ein Agent hat also nichts Stabiles, worauf er zeigen kann. Nutze für die CLI den Windows-Installer || Linux `.deb`, `.rpm`, `.pacman` | `openscreen` |-| Linux-AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux-AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |Die Beispiele auf dieser Seite verwenden `openscreen`. Unter macOS und Windows nimmst du den vollständigen Pfad oder einen Alias:@@ -41,7 +42,7 @@ Die Beispiele auf dieser Seite verwenden `openscreen`. Unter macOS und Windows n```- `openscreen help`, `--help` oder `-h` gibt den Hilfetext aus.-- Chromium-Schalter vor dem Unterbefehl werden übersprungen. Wenn die Sandbox von Chromium auf dem Host nicht starten kann, führe `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen` aus.+- Chromium-Schalter vor dem Unterbefehl werden übersprungen. Wenn die Sandbox von Chromium auf dem Host nicht starten kann, führe `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen` aus.- CLI-Läufe belegen nicht die Einzelinstanz-Sperre der App, sie funktionieren also auch, während die Desktop-App geöffnet ist.- Aus einem Checkout des Quellcodes baust du die App und ihre nativen Hilfsprogramme wie unter [Build and packaging (auf Englisch)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md) beschrieben und führst dann `npm run cli -- <command> [options]` aus.diff --git a/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.mdindex 991cc24e1..89ec324f1 100644--- a/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/es/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenEl skill instala OpenScreen si falta, una vez que aceptes, y agrega su servidor MCP. Luego te pide que abras una nueva sesión y digas *continue the OpenScreen demo*: un agente solo obtiene herramientas nuevas en una nueva sesión. Para configurarlo a mano en cambio:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-El ejecutable de cada sistema aparece en [Ejecutar la CLI](./cli.md#running-the-cli).+`<executable>` es el ejecutable de la app; el de cada sistema aparece en [Ejecutar la CLI](./cli.md#running-the-cli). Otros clientes, como Cursor, usan un servidor stdio con el ejecutable como `command` y `["mcp"]` como `args`.- **Sin puerto, sin token, sin ajuste.** El agente inicia el proceso él mismo, con tus permisos, como ejecutaría `openscreen record`. Así puede grabar tu pantalla y editar sin el interruptor **Ediciones por MCP**.- **Cada toma se convierte en un proyecto nuevo** en tu lista de proyectos, con zooms en sus clics, como una grabación hecha en la app: los clics cercanos en el tiempo y en la pantalla comparten un zoom, y los primeros segundos y el final se quedan en la pantalla completa. Cada edición del agente se guarda en el archivo del proyecto. Se deshace con el punto de restauración que toma el agente, que dura hasta que termina su sesión. Solo se conservan los 20 puntos de restauración más recientes, así que uno más antiguo puede desaparecer antes.diff --git a/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/es/docusaurus-plugin-content-docs/current/cli.mdindex 357803fe1..2565420b9 100644--- a/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/es/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ Primero [instala OpenScreen](/download/) ([Instalación](./installation.md)). Ca|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Instalador de Windows | `Openscreen.exe` en la carpeta elegida durante la instalación: `%LOCALAPPDATA%\Programs\Openscreen\` si se instaló para el usuario actual, `C:\Program Files\Openscreen\` si se instaló para todos los usuarios |+| Microsoft Store | Ninguna fija: su carpeta cambia con cada actualización de la Store, así que un script o un agente no tiene nada estable a lo que apuntar. Usa el instalador de Windows para la CLI || `.deb`, `.rpm`, `.pacman` de Linux | `openscreen` |-| AppImage de Linux | `./Openscreen-Linux-1.11.0.AppImage` |+| AppImage de Linux | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |Los ejemplos de esta página escriben `openscreen`. En macOS y Windows, usa la ruta completa o un alias:@@ -41,7 +42,7 @@ Los ejemplos de esta página escriben `openscreen`. En macOS y Windows, usa la r```- `openscreen help`, `--help` o `-h` muestra el modo de uso.-- Las opciones de Chromium colocadas antes del subcomando se ignoran. Si el sandbox de Chromium no puede iniciarse en el equipo, ejecuta `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`.+- Las opciones de Chromium colocadas antes del subcomando se ignoran. Si el sandbox de Chromium no puede iniciarse en el equipo, ejecuta `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`.- Las ejecuciones de la CLI no toman el bloqueo de instancia única de la app, así que funcionan mientras la app de escritorio está abierta.- Desde una copia del código fuente, compila la app y sus módulos auxiliares nativos como se describe en [Build and packaging (en inglés)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md), y luego ejecuta `npm run cli -- <command> [options]`.diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.mdindex e3fc85198..7ba7433e3 100644--- a/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/fr/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenLa skill installe OpenScreen s'il manque, une fois que vous avez accepté, et ajoute son serveur MCP. Elle vous demande ensuite d'ouvrir une nouvelle session et de dire *continue the OpenScreen demo* : un agent n'obtient de nouveaux outils que dans une nouvelle session. Pour tout configurer à la main à la place :```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-L'exécutable de chaque système est indiqué dans [Lancer la CLI](./cli.md#running-the-cli).+`<executable>` est l'exécutable de l'application, indiqué pour chaque système dans [Lancer la CLI](./cli.md#running-the-cli). Les autres clients, Cursor par exemple, prennent un serveur stdio avec l'exécutable pour `command` et `["mcp"]` pour `args`.- **Ni port, ni jeton, ni réglage.** L'agent lance lui-même le processus, avec vos droits, comme il lancerait `openscreen record`. Il peut donc enregistrer votre écran et faire des modifications sans l'interrupteur **Modifications par MCP**.- **Chaque prise devient un nouveau projet** dans votre liste de projets, zoomé sur ses clics comme un enregistrement fait dans l'application : des clics rapprochés dans le temps et à l'écran partagent un zoom, et les premières secondes comme la fin restent sur l'écran entier. Chaque modification de l'agent est enregistrée dans le fichier du projet. Elle s'annule avec le point de restauration que prend l'agent, qui dure jusqu'à la fin de sa session. Seuls les 20 points de restauration les plus récents sont gardés : un plus ancien peut disparaître avant.diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.mdindex ce25fc460..1fd741ad0 100644--- a/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/fr/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ Commencez par [installer OpenScreen](/download/) ([Installation](./installation.|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Programme d'installation Windows | `Openscreen.exe` dans le dossier choisi à l'installation : `%LOCALAPPDATA%\Programs\Openscreen\` pour une installation réservée à l'utilisateur actuel, `C:\Program Files\Openscreen\` pour tous les utilisateurs |+| Microsoft Store | Aucun chemin fixe : son dossier change à chaque mise à jour du Store, un script ou un agent n'a donc rien de stable à viser. Utilisez le programme d'installation Windows pour la CLI || Linux `.deb`, `.rpm`, `.pacman` | `openscreen` |-| Linux AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |Les exemples de cette page utilisent `openscreen`. Sous macOS et Windows, utilisez le chemin complet ou un alias :@@ -41,7 +42,7 @@ Les exemples de cette page utilisent `openscreen`. Sous macOS et Windows, utilis```- `openscreen help`, `--help` ou `-h` affiche l'aide.-- Les options de Chromium placées avant la sous-commande sont sautées lors de la lecture des arguments. Si le bac à sable de Chromium ne peut pas démarrer sur la machine, lancez `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`.+- Les options de Chromium placées avant la sous-commande sont sautées lors de la lecture des arguments. Si le bac à sable de Chromium ne peut pas démarrer sur la machine, lancez `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`.- Les exécutions de la CLI ne prennent pas le verrou d'instance unique de l'application : elles fonctionnent donc pendant que l'application de bureau est ouverte.- Depuis une copie du code source, compilez l'application et ses modules natifs comme le décrit [Build and packaging (en anglais)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md), puis lancez `npm run cli -- <command> [options]`.diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.mdindex 6ec2fc3af..f9f6d61ca 100644--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenこのスキルは、OpenScreen がなければ、同意を得たうえでインストールし、その MCP サーバーを追加します。続いて、新しいセッションを開いて *continue the OpenScreen demo* と伝えるよう求めます。エージェントが新しいツールを得られるのは、新しいセッションの中だけです。代わりに手動で設定するには、次のようにします。```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-各システムでの実行ファイルは、[CLI の実行](./cli.md#running-the-cli)に記載しています。+`<executable>` はアプリの実行ファイルです。各システムでのパスは [CLI の実行](./cli.md#running-the-cli)に記載しています。Cursor などほかのクライアントでは、実行ファイルを `command`、`["mcp"]` を `args` とした stdio サーバーとして追加します。- **ポートも、トークンも、設定も不要。** エージェントは、`openscreen record` を実行するときと同じように、あなたの権限でプロセスを自分で起動します。そのため、**MCP による編集**スイッチなしで、画面を録画し、編集できます。- **テイクはそれぞれ新しいプロジェクトになり**、プロジェクト一覧に表示されます。アプリで作った録画と同じく、記録されたクリックにズームが付きます。時間的にも画面上でも近いクリックは1つのズームにまとめられ、最初の数秒と最後は画面全体のままです。エージェントによる編集はすべてプロジェクトのファイルに保存されます。元に戻すには、エージェントが作成するチェックポイントを使います。チェックポイントはエージェントのセッションが終わるまで有効です。保持されるのは直近 20 個のチェックポイントだけなので、古いものはそれより前に消えることがあります。diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.mdindex 18abaedbf..b68fdb34d 100644--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ CLI と `.openscreen` プロジェクト形式には、今後もリリース間|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Windows インストーラー | セットアップ時に選んだフォルダー内の `Openscreen.exe`。現在のユーザー向けのインストールでは `%LOCALAPPDATA%\Programs\Openscreen\`、全ユーザー向けでは `C:\Program Files\Openscreen\` |+| Microsoft Store | 固定のパスはありません。フォルダーは Store の更新のたびに変わるため、スクリプトやエージェントが指し示せる安定したパスがありません。CLI には Windows インストーラー版を使ってください || Linux `.deb`、`.rpm`、`.pacman` | `openscreen` |-| Linux AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |このページの例では `openscreen` と表記しています。macOS と Windows では、フルパスかエイリアスを使ってください。@@ -41,7 +42,7 @@ CLI と `.openscreen` プロジェクト形式には、今後もリリース間```- `openscreen help`、`--help`、`-h` で使い方が表示されます。-- サブコマンドより前に置いた Chromium のスイッチは読み飛ばされます。ホスト上で Chromium のサンドボックスを起動できない場合は、`./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen` のように実行します。+- サブコマンドより前に置いた Chromium のスイッチは読み飛ばされます。ホスト上で Chromium のサンドボックスを起動できない場合は、`./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen` のように実行します。- CLI の実行はアプリの単一インスタンスロックを取得しないため、デスクトップアプリを開いたままでも動作します。- ソースのチェックアウトから使う場合は、[Build and packaging(英語)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md)の説明に従ってアプリとネイティブヘルパーをビルドし、`npm run cli -- <command> [options]` を実行します。diff --git a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.mdindex 3e5ca9c4a..7ef8864b8 100644--- a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreenA skill instala o OpenScreen se ele estiver faltando, depois que você concordar, e adiciona o servidor MCP dele. Em seguida, ela pede que você abra uma nova sessão e diga *continue the OpenScreen demo*: um agente só recebe ferramentas novas em uma nova sessão. Para configurar à mão, em vez disso:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-O executável de cada sistema está listado em [Como executar a CLI](./cli.md#running-the-cli).+`<executable>` é o executável do app; o de cada sistema está listado em [Como executar a CLI](./cli.md#running-the-cli). Outros clientes, como o Cursor, usam um servidor stdio com o executável como `command` e `["mcp"]` como `args`.- **Sem porta, sem token, sem configuração.** O agente inicia o processo por conta própria, com as suas permissões, como faria ao rodar `openscreen record`. Por isso ele pode gravar a sua tela e editar sem o interruptor **Edições via MCP**.- **Cada tomada vira um novo projeto** na sua lista de projetos, com zooms nos seus cliques, como uma gravação feita no app: cliques próximos no tempo e na tela dividem um zoom, e os primeiros segundos e o final ficam na tela inteira. Cada edição do agente é salva no arquivo do projeto. Ela se desfaz com o ponto de restauração que o agente cria, que dura até o fim da sessão dele. Só os 20 pontos de restauração mais recentes são mantidos, então um mais antigo pode sumir antes.diff --git a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.mdindex 1df0dea7f..8f375d954 100644--- a/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/pt-BR/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ A CLI e o formato de projeto `.openscreen` ainda podem mudar de forma incompatí|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Instalador do Windows | `Openscreen.exe` na pasta escolhida na instalação: `%LOCALAPPDATA%\Programs\Openscreen\` para uma instalação para o usuário atual, `C:\Program Files\Openscreen\` para todos os usuários |+| Microsoft Store | Nenhum fixo: a pasta muda a cada atualização da Store, então um script ou um agente não tem nada estável para apontar. Use o instalador do Windows para a CLI || `.deb`, `.rpm`, `.pacman` no Linux | `openscreen` |-| AppImage no Linux | `./Openscreen-Linux-1.11.0.AppImage` |+| AppImage no Linux | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |Os exemplos desta página usam `openscreen`. No macOS e no Windows, use o caminho completo ou um alias:@@ -41,7 +42,7 @@ Os exemplos desta página usam `openscreen`. No macOS e no Windows, use o caminh```- `openscreen help`, `--help` ou `-h` mostra o modo de uso.-- As opções (switches) do Chromium colocadas antes do subcomando são ignoradas. Se o sandbox do Chromium não conseguir iniciar na máquina, execute `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`.+- As opções (switches) do Chromium colocadas antes do subcomando são ignoradas. Se o sandbox do Chromium não conseguir iniciar na máquina, execute `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`.- As execuções da CLI não adquirem o bloqueio de instância única do app, então funcionam com o app para desktop aberto.- A partir de um checkout do código-fonte, compile o app e seus auxiliares nativos como descrito em [Build and packaging (em inglês)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md) e depois execute `npm run cli -- <command> [options]`.diff --git a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.mdindex 3e885fdd8..45c109145 100644--- a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreen如果缺少 OpenScreen,该技能会在你同意后安装它,并添加它的 MCP 服务器。随后它会请你打开一个新会话,并说出 *continue the OpenScreen demo*:AI 代理只有在新会话中才能获得新工具。若要改为手动设置:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-各系统上的可执行文件列在[运行 CLI](./cli.md#running-the-cli)中。+`<executable>` 是应用的可执行文件,各系统上的路径列在[运行 CLI](./cli.md#running-the-cli)中。其他客户端(例如 Cursor)以 stdio 服务器的方式添加:可执行文件作为 `command`,`["mcp"]` 作为 `args`。- **无需端口、令牌或设置**。AI 代理以你的权限自行启动进程,就像它运行 `openscreen record` 一样。因此,它无需**MCP 编辑**开关,就能录制你的屏幕并进行编辑。- **每次录制都会成为一个新项目**,出现在你的项目列表中,并且与在应用中录制的内容一样,在录制下来的点击处添加缩放:时间和位置都相近的点击共用一个缩放,开头几秒和结尾保持全屏。AI 代理的每项编辑都会保存到项目文件中。撤销它们要靠 AI 代理创建的检查点,检查点在代理的会话结束前一直有效。只保留最近的 20 个检查点,因此较早的检查点可能会更早失效。diff --git a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.mdindex 1e3ab5c93..efeefd815 100644--- a/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/zh-CN/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ CLI 和 `.openscreen` 项目格式在不同版本之间仍可能发生不兼容|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Windows 安装程序 | 安装时所选文件夹中的 `Openscreen.exe`:为当前用户安装时是 `%LOCALAPPDATA%\Programs\Openscreen\`,为所有用户安装时是 `C:\Program Files\Openscreen\` |+| Microsoft Store | 没有固定路径:其文件夹会随每次 Store 更新而变化,脚本或 AI 代理没有稳定的路径可用。请使用 Windows 安装程序版本来运行 CLI || Linux `.deb`、`.rpm`、`.pacman` | `openscreen` |-| Linux AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |本页示例中写的都是 `openscreen`。在 macOS 和 Windows 上,请使用完整路径或别名:@@ -41,7 +42,7 @@ CLI 和 `.openscreen` 项目格式在不同版本之间仍可能发生不兼容```- `openscreen help`、`--help` 或 `-h` 会打印用法说明。-- 放在子命令之前的 Chromium 开关会被跳过。如果 Chromium 的沙盒无法在主机上启动,请运行 `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`。+- 放在子命令之前的 Chromium 开关会被跳过。如果 Chromium 的沙盒无法在主机上启动,请运行 `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`。- CLI 运行时不会占用应用的单实例锁,所以在桌面应用打开时也能使用。- 如果从源代码检出目录运行,请按照 [Build and packaging(英文)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md)的说明构建应用及其原生辅助程序,然后运行 `npm run cli -- <command> [options]`。diff --git a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.mdindex efe33494d..34a714ae8 100644--- a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md+++ b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/ai-editing.md@@ -91,11 +91,11 @@ Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreen如果缺少 OpenScreen,該技能會在你同意後安裝它,並加入它的 MCP 伺服器。接著它會請你開啟一個新的工作階段,並說出 *continue the OpenScreen demo*:代理只有在新的工作階段中才能取得新工具。若要改為手動設定:```bash-claude mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp-codex mcp add openscreen -- "/Applications/Openscreen.app/Contents/MacOS/Openscreen" mcp+claude mcp add openscreen -- "<executable>" mcp+codex mcp add openscreen -- "<executable>" mcp```-各系統上的執行檔列在[執行 CLI](./cli.md#running-the-cli)中。+`<executable>` 是應用程式的執行檔,各系統上的路徑列在[執行 CLI](./cli.md#running-the-cli)中。其他用戶端(例如 Cursor)以 stdio 伺服器的方式加入:執行檔作為 `command`,`["mcp"]` 作為 `args`。- **不需要連接埠、權杖或設定。** 代理會以你的權限自行啟動程序,就像它執行 `openscreen record` 一樣。因此,它不需要**MCP 編輯**開關,就能錄製你的螢幕並進行剪輯。- **每段錄影都會成為一個新專案**,出現在你的專案清單中,並和在應用程式中錄製的影片一樣,在錄下的點擊處加上縮放:時間與位置都相近的點擊共用一個縮放,開頭幾秒與結尾保持全螢幕。代理的每項編輯都會儲存到專案檔案中。要復原,就靠代理建立的檢查點,檢查點在代理的工作階段結束前都有效。只會保留最近的 20 個檢查點,因此較早的檢查點可能會提早失效。diff --git a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.mdindex 9f74d710a..cd5fd6137 100644--- a/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md+++ b/website/i18n/zh-TW/docusaurus-plugin-content-docs/current/cli.md@@ -30,8 +30,9 @@ CLI 與 `.openscreen` 專案格式在不同版本之間仍可能出現不相容|---|---|| macOS | `/Applications/Openscreen.app/Contents/MacOS/Openscreen` || Windows 安裝程式 | 安裝時所選資料夾中的 `Openscreen.exe`:僅為目前使用者安裝時是 `%LOCALAPPDATA%\Programs\Openscreen\`,為所有使用者安裝時是 `C:\Program Files\Openscreen\` |+| Microsoft Store | 沒有固定路徑:其資料夾會隨每次 Store 更新而變更,指令碼或代理沒有穩定的路徑可用。請使用 Windows 安裝程式版本來執行 CLI || Linux `.deb`、`.rpm`、`.pacman` | `openscreen` |-| Linux AppImage | `./Openscreen-Linux-1.11.0.AppImage` |+| Linux AppImage | `./Openscreen-Linux-<version>.AppImage` || Nix | `openscreen` |本頁的範例都寫成 `openscreen`。在 macOS 與 Windows 上,請使用完整路徑或別名:@@ -41,7 +42,7 @@ CLI 與 `.openscreen` 專案格式在不同版本之間仍可能出現不相容```- `openscreen help`、`--help` 或 `-h` 會印出用法說明。-- 放在子指令之前的 Chromium 參數會被略過。如果 Chromium 的沙箱無法在主機上啟動,請執行 `./Openscreen-Linux-1.11.0.AppImage --no-sandbox export demo.openscreen`。+- 放在子指令之前的 Chromium 參數會被略過。如果 Chromium 的沙箱無法在主機上啟動,請執行 `./Openscreen-Linux-<version>.AppImage --no-sandbox export demo.openscreen`。- CLI 執行時不會取得應用程式的單一執行個體鎖定,所以桌面應用程式開著時也能使用。- 若從原始碼的 checkout 執行,請依照[建置與打包(英文)](https://github.com/getopenscreen/openscreen/blob/main/technical-documentation/engineering/build-and-packaging.md)的說明建置應用程式與其原生輔助程式,然後執行 `npm run cli -- <command> [options]`。