Skip to content
Back to search

jev-browser-use

SkillWorks with Claude CodeGitHub

Fast browser actions with Jev and independent verification with Codex. Requires Computer Use and your Jev API configuration.

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wy-coliney--jev-browser-use/badge.svg)](/listings/wy-coliney--jev-browser-use)

HTML

<a href="/listings/wy-coliney--jev-browser-use"><img src="/api/listings/wy-coliney--jev-browser-use/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

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

**Codex — one command:**

npx skills add wy-coliney/jev-browser-use -g -a codex -y

Then [configure your Jev API](skills/jev-browser-use/references/provider-configuration.md) and start a new Codex task.

**Update a Skill installed this way:**

npx skills update jev-browser-use -g

Start a new Codex task after updating to load the new Skill instructions. The update does not change your `~/.config/jev-browser-use/config.json` or credential file.

Choose the provider that issued your API key. A TypeSafe key goes with `provider: "typesafe"` and `TYPESAFE_API_KEY`; an OpenRouter key goes with `provider: "openrouter"` and `OPENROUTER_API_KEY`. These keys are not interchangeable, even though both providers offer Jev. Put the key in the dotenv file named by `envFile` in `~/.config/jev-browser-use/config.json`.

You need **Node.js 22+**, **Codex with Computer Use connected to Chrome or its in-app browser**, and **Jev access through TypeSafe or OpenRouter Decisions**. Installing this Skill does not install the browser connection.

<details> <summary><strong>Prefer the native Codex plugin?</strong></summary>

codex plugin marketplace add wy-coliney/jev-browser-use && codex plugin add jev-browser-use@jev-browser-use

Requires a Codex CLI with `codex plugin` support. Restart Codex after installation. Alternatively, add the marketplace with the first command, then select **Jev Browser Use** in the desktop plugin directory.

This repository supplies the community marketplace. Choose the plugin **or** the standalone Skill to avoid duplicate instructions; both use the same Jev configuration.

</details>

<details> <summary><strong>Have your agent install and configure it</strong></summary>

Paste this into Codex:

Install Jev Browser Use following this guide:
https://raw.githubusercontent.com/wy-coliney/jev-browser-use/main/INSTALL.md
Preserve existing configuration. Ask for my chosen provider and local
credential file path if needed. Never ask me to paste an API key in chat.

</details>

<details> <summary><strong>Claude Code and other agents</strong></summary>

npx skills add wy-coliney/jev-browser-use

Choose an agent, or install directly into Claude Code:

npx skills add wy-coliney/jev-browser-use -g -a claude-code -y

**Claude Code browser support is coming soon.** The Skill can be installed now; browser execution currently requires the Codex Computer Use runtime.

</details>

<details> <summary><strong>Manual installation / ZIP</strong></summary>

git clone https://github.com/wy-coliney/jev-browser-use.git
cd jev-browser-use
node scripts/install.mjs

Or extract the repository ZIP and run the same Node command. The installer asks for your provider, model, and local credential file path. Existing settings are preserved; credentials stay outside the Skill.

</details>

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.

plugin.json · Manifest · 6 lines

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

  1. {
  2. "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  3. "name": "jev-browser-use",
  4. "version": "0.1.0",
  5. "description": "Fast browser actions with Jev and independent verification with Codex. Requires Computer Use and your Jev API configuration."
  6. }
README.md · README · 180 lines

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

  1. # Jev Browser Use
  2. **Jev clicks. Codex thinks and verifies.**
  3. A browser Skill powered by [TypeSafe’s Jev](https://docs.typesafe.ai/introduction). Hand off navigation, clicks, toggles, and scrolling; keep Codex in charge of text input, visual judgment, and the final check.
  4. [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
  5. ![Jev Browser Use](assets/hero.png)
  6. **~5–10× faster browser operations in our EZCollegeApp workflows.** Your existing browser connection. No extra driver or npm dependencies.
  7. [Install](#install) · [Try it](#try-it) · [How it works](#how-it-works) · [Real-world use](#built-for-ezcollegeapp) · [Cost](#cost) · [Official guides](#official-guides) · [Stars](#star-history)
  8. ## Install
  9. **Codex — one command:**
  10. ```sh
  11. npx skills add wy-coliney/jev-browser-use -g -a codex -y
  12. ```
  13. Then [configure your Jev API](skills/jev-browser-use/references/provider-configuration.md) and start a new Codex task.
  14. **Update a Skill installed this way:**
  15. ```sh
  16. npx skills update jev-browser-use -g
  17. ```
  18. Start a new Codex task after updating to load the new Skill instructions. The update does not change your `~/.config/jev-browser-use/config.json` or credential file.
  19. Choose the provider that issued your API key. A TypeSafe key goes with `provider: "typesafe"` and `TYPESAFE_API_KEY`; an OpenRouter key goes with `provider: "openrouter"` and `OPENROUTER_API_KEY`. These keys are not interchangeable, even though both providers offer Jev. Put the key in the dotenv file named by `envFile` in `~/.config/jev-browser-use/config.json`.
  20. You need **Node.js 22+**, **Codex with Computer Use connected to Chrome or its in-app browser**, and **Jev access through TypeSafe or OpenRouter Decisions**. Installing this Skill does not install the browser connection.
  21. <details>
  22. <summary><strong>Prefer the native Codex plugin?</strong></summary>
  23. ```sh
  24. codex plugin marketplace add wy-coliney/jev-browser-use && codex plugin add jev-browser-use@jev-browser-use
  25. ```
  26. Requires a Codex CLI with `codex plugin` support. Restart Codex after installation. Alternatively, add the marketplace with the first command, then select **Jev Browser Use** in the desktop plugin directory.
  27. This repository supplies the community marketplace. Choose the plugin **or** the standalone Skill to avoid duplicate instructions; both use the same Jev configuration.
  28. </details>
  29. <details>
  30. <summary><strong>Have your agent install and configure it</strong></summary>
  31. Paste this into Codex:
  32. ```text
  33. Install Jev Browser Use following this guide:
  34. https://raw.githubusercontent.com/wy-coliney/jev-browser-use/main/INSTALL.md
  35. Preserve existing configuration. Ask for my chosen provider and local
  36. credential file path if needed. Never ask me to paste an API key in chat.
  37. ```
  38. </details>
  39. <details>
  40. <summary><strong>Claude Code and other agents</strong></summary>
  41. ```sh
  42. npx skills add wy-coliney/jev-browser-use
  43. ```
  44. Choose an agent, or install directly into Claude Code:
  45. ```sh
  46. npx skills add wy-coliney/jev-browser-use -g -a claude-code -y
  47. ```
  48. **Claude Code browser support is coming soon.** The Skill can be installed now; browser execution currently requires the Codex Computer Use runtime.
  49. </details>
  50. <details>
  51. <summary><strong>Manual installation / ZIP</strong></summary>
  52. ```sh
  53. git clone https://github.com/wy-coliney/jev-browser-use.git
  54. cd jev-browser-use
  55. node scripts/install.mjs
  56. ```
  57. Or extract the repository ZIP and run the same Node command. The installer asks for your provider, model, and local credential file path. Existing settings are preserved; credentials stay outside the Skill.
  58. </details>
  59. ## Try it
  60. Give Codex a browser task:
  61. ```text
  62. Use Jev Browser Use on the settings page. Open the filters, switch views,
  63. scroll through the results, and restore the original state.
  64. Independently verify the result.
  65. ```
  66. Or prepare something for your review:
  67. ```text
  68. Use Jev Browser Use to help prepare a post in my open Chrome tab.
  69. Use the draft and image I provide. Check both, then stop before publishing.
  70. ```
  71. Jev handles the controls. Codex enters text, handles images, and checks the outcome. When a step needs help, Codex takes over and Jev resumes afterward.
  72. ## How it works
  73. ![Codex plans, types, and verifies; Jev clicks, navigates, and scrolls](assets/teamwork.png)
  74. **Goal → observe controls → Jev chooses an action → browser → repeat → Codex verifies.**
  75. The action loop stays inside the existing Computer Use connection, avoiding a new host-model turn for every click. Sessions retain progress across handoffs and check fresh page state before acting. Jev’s completion signal brings Codex back for verification.
  76. Jev receives accessibility text, not screenshots. Codex handles typing, visual interpretation, and unsupported controls. Use it for dashboards, settings, reports, and browser checks—not just writing tasks.
  77. ## Built for EZCollegeApp
  78. We built this while testing **[EZCollegeApp](https://ezcollegeapp.com)**, our college application product. Reviewing an essay feature meant repeatedly opening evaluations, expanding notes, scrolling reports, and returning to the editor.
  79. Jev handles that navigation; Codex checks whether evaluation feedback and inline annotations agree. The same split works anywhere repeated browser operations slow down your agent.
  80. ![Approximate browser-operation speedup](assets/speed.svg)
  81. *~5–10× is our approximate browser-operation speedup, varying by task. Server-side processing is excluded; the chart illustrates the ratio.*
  82. ## Cost
  83. Put repetitive decisions on Jev and reserve Codex for the work that needs it.
  84. | Model | Input / 1M tokens | Output / 1M tokens | Input price vs. Jev |
  85. | --- | ---: | ---: | ---: |
  86. | **Jev 1.13** | **$0.042** | **Free** | **1×** |
  87. | GPT-5.6 Terra | $2.00 | $12.00 | 48× |
  88. | GPT-5.6 Sol | $4.00 | $20.00 | 95× |
  89. | GPT-6 Astra | $10.00 | $50.00 | 238× |
  90. At 100,000 input tokens, that's **$0.0042 for Jev**, versus $0.20, $0.40, or $1.00 before output charges. Send repetitive action decisions to Jev and reserve Codex for the work that needs it.
  91. Standard uncached API rates, checked September 18, 2026: [TypeSafe pricing](https://docs.typesafe.ai/models), [OpenAI model pricing](https://developers.openai.com/api/docs/models/compare). These compare token prices; total workflow cost also includes Codex and depends on usage.
  92. ## Setup and updates
  93. - **Configuration:** [Choose your provider and connect your API](skills/jev-browser-use/references/provider-configuration.md). All installation methods share `~/.config/jev-browser-use/config.json`.
  94. - **Plugin updates:** refresh with `codex plugin marketplace upgrade jev-browser-use`, reinstall with `codex plugin add jev-browser-use@jev-browser-use`, then restart Codex.
  95. - **Manual updates:** pull the repository and run `node scripts/install.mjs --no-config`.
  96. Browser workflows were exercised on macOS. Page text goes to your selected provider; only delegate data you authorize it to process. Keep credentials and private page content out of public issues. See the [full Skill](skills/jev-browser-use/SKILL.md) for runtime requirements and handoffs.
  97. ### Troubleshooting
  98. If Codex says the browser tool is missing, check the [direct `mcp__cua_repl.js` discovery steps](skills/jev-browser-use/SKILL.md#discover-the-browser-tool-correctly--required-before-declaring-it-unavailable). The tool is not listed inside `functions.exec`'s deferred tools. Installing the Skill alone does not add Computer Use to a task.
  99. If Chrome connection fails before Jev runs, check the [browser connector guidance](skills/jev-browser-use/references/provider-configuration.md#diagnose-failures-by-stage). When the task allows either browser, the in-app browser may work even if Chrome attachment does not. If a Jev request fails with `ENOTFOUND`, use the [credential-free CUA network probe](skills/jev-browser-use/SKILL.md#check-provider-transport-inside-cua); a successful shell request does not prove network access inside CUA.
  100. ## Official guides
  101. [Jev introduction](https://docs.typesafe.ai/introduction) · [Jev API quick start](https://docs.typesafe.ai/introduction/quickstart) · [Codex plugins](https://developers.openai.com/plugins/build/plugins) · [Skills CLI](https://github.com/vercel-labs/skills)
  102. Also worth exploring: [Browser Use’s Jev Ultrafast](https://github.com/browser-use/jev-ultrafast), a standalone browser-agent project using Jev.
  103. [MIT licensed](LICENSE). An independent integration, not an official OpenAI or TypeSafe product.
  104. ## Star history
  105. If this saves you a few hundred clicks, give it a star.
  106. <a href="https://www.star-history.com/?repos=wy-coliney%2Fjev-browser-use&amp;type=date&amp;legend=bottom-right">
  107. <picture>
  108. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=wy-coliney/jev-browser-use&amp;type=date&amp;theme=dark&amp;legend=bottom-right" />
  109. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=wy-coliney/jev-browser-use&amp;type=date&amp;legend=bottom-right" />
  110. <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=wy-coliney/jev-browser-use&amp;type=date&amp;legend=bottom-right" />
  111. </picture>
  112. </a>

Ratings and comments

Sign in to rate this skill.

Sign in

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