Skip to content
Back to search

lcu

MarketplaceWorks with Claude CodeGitHub

Codex computer use, decoupled from the app, for usage inside any harness.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/amontlabs/lcu with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/amontlabs/lcu'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/amontlabs--lcu/badge.svg)](/listings/amontlabs--lcu)

HTML

<a href="/listings/amontlabs--lcu"><img src="/api/listings/amontlabs--lcu/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Copy this into your agent:

Install and configure LCU for this harness using the latest release.
Follow https://raw.githubusercontent.com/amontlabs/lcu/main/docs/INSTALLATION.md
Check my OS, architecture, and prerequisites, then guide me through any required permissions.

In Claude Code on an Apple Silicon Mac, two commands do the same through its plugin manager; see [Claude Code plugin](docs/INSTALLATION.md#claude-code-plugin):

claude plugin marketplace add amontlabs/lcu
claude plugin install lcu@lcu

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "lcu",
  3. "owner": {
  4. "name": "LCU"
  5. },
  6. "metadata": {
  7. "description": "LCU for Claude Code: Codex computer use through the locally installed ChatGPT desktop app."
  8. },
  9. "plugins": [
  10. {
  11. "name": "lcu",
  12. "source": "./adapters/claude-plugin",
  13. "description": "Codex computer use in Claude Code. Installs LCU from its latest release when it is missing, then registers it with `lcu setup --agent claude-code`."
  14. }
  15. ]
  16. }
README.md · README · 151 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="docs/assets/lcu-icon.svg" width="120" height="120" alt="LCU logo">
  3. </p>
  4. <h1 align="center">LCU</h1>
  5. <p align="center"><strong>Codex computer use, decoupled from the Codex app.</strong></p>
  6. https://github.com/user-attachments/assets/bd9d0809-8a6c-4931-a51c-b98daf05cb5f
  7. LCU exposes Codex's original computer-use runtime to your harness without requiring Codex authentication. The official ChatGPT desktop app must still be installed locally: it supplies the runtime and instructions, while LCU handles setup and harness integration.
  8. ## Quick start
  9. Copy this into your agent:
  10. ```text
  11. Install and configure LCU for this harness using the latest release.
  12. Follow https://raw.githubusercontent.com/amontlabs/lcu/main/docs/INSTALLATION.md
  13. Check my OS, architecture, and prerequisites, then guide me through any required permissions.
  14. ```
  15. In Claude Code on an Apple Silicon Mac, two commands do the same through its plugin manager; see [Claude Code plugin](docs/INSTALLATION.md#claude-code-plugin):
  16. ```sh
  17. claude plugin marketplace add amontlabs/lcu
  18. claude plugin install lcu@lcu
  19. ```
  20. ## Features
  21. - **Desktop apps:** read windows, click, type, and take screenshots.
  22. - **Chrome, when enabled:** read and control tabs through the official extension, with site approval.
  23. - **In your harness:** adapters are available for Pi, Codex CLI, and Claude Code, with experimental Oh My Pi, Hermes, DeepSeek Harness and Junie integrations. With Junie, app approvals are permanent until revoked: Junie cannot show LCU's per-app prompt, so it runs `lcu apps allow <App>` itself and each approval lasts until `lcu apps revoke <App>`. See [setup and verification limits](docs/ADAPTERS.md).
  24. ## Approve apps from Claude, natively
  25. The first time an agent controls an app (Zed, Notes, Safari), the computer-use runtime asks you to allow it. The Claude app's Code tab used to fail that request with "Computer Use was not approved". `lcu setup --agent claude-code` now installs a small Claude Code mod, `lcu-approve`, that asks the question natively: as a question card in the Claude app, which flags the session as needing input, and as a **Computer use approval** pane in the terminal.
  26. <p align="center"><img src="docs/assets/approval-demo.gif" width="720" alt="The Computer use approval pane in Claude Code: Allow this conversation, a high-risk app with its warning, and the Approved apps panel"></p>
  27. - **Allow this conversation** for the current chat only.
  28. - **Always allow** to remember the app (offered only when the runtime allows it).
  29. - **Deny** to refuse.
  30. The `/computer-use-apps` command opens an **Approved apps** panel in the same place: one line per always-allowed app with Revoke (macOS asks for Touch ID or your password), apps that are no longer installed grouped below, this conversation's grants, and an Allow field.
  31. Only you can answer: the model cannot see, press or fake the pane. High-risk apps show the runtime's own warning (reworded to say "computer use" and "the agent"), and the app hosting the agent is never approved. Needs the Claude app or Claude Code 2.1.287+. [How it works](docs/ADAPTERS.md#native-app-approvals-in-claude-code-and-the-claude-app), [how to remove it](docs/INSTALLATION.md#uninstall).
  32. In the Claude app, register LCU through Claude Code (`lcu setup --agent claude-code`), not through Settings > Connectors; see [installation](docs/INSTALLATION.md#native-approvals-in-the-claude-app).
  33. ## Manage approved apps with Touch ID
  34. "Always allow" is remembered. Review and change that list from the terminal (macOS), without opening the Codex app:
  35. ```sh
  36. lcu apps # what is always allowed today
  37. lcu apps allow Zed # Touch ID (or your password), then Zed is allowed
  38. lcu apps revoke Zed # take it back
  39. ```
  40. <p align="center"><img src="docs/assets/approved-apps.png" width="720" alt="The Approved apps panel opened with /computer-use-apps"></p>
  41. - Pass an app name, a bundle identifier or an `.app` path.
  42. - Listing is free; `allow` and `revoke` need you at the machine, so an agent running them is stopped by the prompt.
  43. - Running sessions pick the change up immediately.
  44. - Browsers, password managers and other high-risk apps come with a warning; apps Computer Use refuses outright (Terminal, iTerm2) are declined.
  45. [Details](docs/INSTALLATION.md#manage-approved-apps).
  46. ## Keep Computer Use across turns (Claude Code)
  47. In Claude Code, Computer Use normally ends with the turn that started it. A background subagent still working after that turn ended, or a turn that reuses an ended turn id, is told "Computer Use is unavailable because the current turn ended." An opt-in setting keeps it available for every turn of the session:
  48. ```sh
  49. lcu cross-turn # status
  50. lcu cross-turn on # Touch ID (or your password) on macOS
  51. lcu cross-turn off # no prompt
  52. ```
  53. - Off by default. `lcu setup --cross-turn on|off` sets it too; interactive setup asks once.
  54. - It affects only the Claude Code relay; Codex, Pi, Oh My Pi and Hermes ignore it. Per-app approvals (macOS and Windows) and your harness's tool approvals still apply.
  55. - A foreground subagent finishing no longer ends the parent's Computer Use, with the setting on or off.
  56. - A guard against accidents, not a security boundary: anything running as your account can edit the file or pass `--unattended` (for disposable sandbox machines, where nobody can answer the prompt).
  57. [Details](docs/INSTALLATION.md#cross-turn-computer-use).
  58. ## Permissions
  59. Your harness decides whether the agent may call LCU's tools (Claude's "don't ask again" on the first card, Codex's tool approval, and so on). LCU decides, per app, whether that agent may touch it, in every permission mode. `lcu setup --approval auto` is optional and meant for unattended machines (VMs, CI): it pre-allows LCU's two model tools in the harness, and leaves per-app approval in force. See [approval mode](docs/INSTALLATION.md#approval-mode).
  60. ## Requirements
  61. Install [the official ChatGPT desktop app](https://chatgpt.com/download/) and your harness first. LCU needs nothing else: no Python on any platform. It runs on the Node that ships inside the app, checks the installed app for compatibility and uses its original runtime. For Codex CLI, [update before setup](docs/ADAPTERS.md#codex-cli) to get the required hook support.
  62. | Platform | Requirements |
  63. | --- | --- |
  64. | Linux ARM64 or x86-64 | Ubuntu 24.04-compatible glibc system, an active X11 desktop, and D-Bus |
  65. | macOS on Apple Silicon | The signed ChatGPT app, with Accessibility and screen-recording permissions approved during first use |
  66. Windows 11 x64 remains a [candidate](docs/INSTALLATION.md#windows-11-x64-candidate-deferred-from-this-delivery). Intel Macs, native Wayland, and musl Linux are unsupported. See [verification and limits](docs/PARITY-STATUS.md) for tested behavior.
  67. ## Install manually
  68. Download the archive and matching `.sha256` file from the [latest release](https://github.com/amontlabs/lcu/releases/latest):
  69. | Platform | Archive |
  70. | --- | --- |
  71. | macOS on Apple Silicon | `lcu-<version>-darwin-arm64.tar.gz` |
  72. | Linux ARM64 | `lcu-<version>-linux-arm64.tar.gz` |
  73. | Linux x86-64 | `lcu-<version>-linux-x64.tar.gz` |
  74. Follow the [installation guide](docs/INSTALLATION.md) to verify the checksum, extract the archive, and register LCU in your harness. Setup offers an agent chooser and desktop-readiness guidance. Chrome and computer-audio recording are opt-in.
  75. For development, see [building from source](docs/DEVELOPMENT.md#building-from-source).
  76. ## Enable Chrome
  77. Ask your agent:
  78. ```text
  79. Enable Chrome control in my LCU setup using the installation guide:
  80. https://raw.githubusercontent.com/amontlabs/lcu/main/docs/INSTALLATION.md#desktop-and-browser
  81. ```
  82. Enable the official extension in your Chrome profile and restart your harness. Then restart Chrome, or turn the ChatGPT extension off and on in `chrome://extensions`; an extension that was already connected keeps the original native host until it reconnects. Then ask your agent to use LCU to list Chrome tabs. Sites still require approval. Claude Code's Chrome support remains experimental because some interruptions do not trigger tab cleanup; see [adapter limitations](docs/ADAPTERS.md). If Chrome calls fail with `requires caller identity`, see [Chrome troubleshooting](docs/INSTALLATION.md#chrome-extension-fails-with-requires-caller-identity).
  83. ## Enable computer-audio recording
  84. Pass `--audio` when setting up a maintained harness, for example:
  85. ```sh
  86. ~/.local/share/lcu/current/bin/lcu setup --agent pi --audio
  87. ```
  88. The installer does not add `lcu` to your `PATH`; run its installed path (`/opt/lcu/current/bin/lcu` on Linux). See [the `lcu` command](docs/INSTALLATION.md#the-lcu-command).
  89. This enables the installed original runtime's optional computer-audio recording API and its original approval flow. LCU does not add audio-specific instructions, and a saved recording is not audio delivered to the model. See the [audio opt-in verification record](docs/verification/audio-opt-in-2026-09-27.md).
  90. ## Pi commands
  91. In interactive Pi, `/lcu stop` requests original Computer Use Stop for a selected app during the active LCU turn (macOS only). `/lcu pick` selects an original app or browser target and appends it to the editor draft while Pi is idle; review and submit the draft yourself. See [adapter command behavior and limits](docs/ADAPTERS.md#pi-extension).
  92. ## Documentation
  93. - [Installation](docs/INSTALLATION.md): downloads, harness setup, permissions, sessions, and upgrades. Update with `lcu update`; [update notices](docs/INSTALLATION.md#update-notices) can be turned off with `LCU_NO_UPDATE_CHECK=1`.
  94. - [Harness adapters](docs/ADAPTERS.md): custom clients, approvals, lifecycle, and result handling.
  95. - [Verification](docs/PARITY-STATUS.md): tested behavior and remaining gaps.
  96. - [Development](docs/DEVELOPMENT.md): source builds and isolated desktop tests.
  97. LCU is [MIT licensed](LICENSE). Release archives contain LCU and third-party setup dependencies. The OpenAI app and its instructions come from your local installation and retain their own terms; see [dependency provenance](docs/PROVENANCE.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.