agentleFS
Sign inStart free
VercelKnown publishervercel/eve/packages/eve-computer-use/AGENTS.md

eve / eve-computer-use

AGENTS.md5.6k starsChanged 30 days agoApache-2.0View on GitHub

This private package is the source of the eve/computer-use extension. It contributes the computer_use tool and the sandbox helpers that install and start the desktop and driver. Before writing code, read the installed eve package docs for extensions, tools, and sandboxes as applicable. The eve build copies extension/ into packages/eve/src/computer-use/extension and compiles it into the eve package; public entry points are declared in packages/eve/package.json and packages/eve/src/computer-use/. Do not publish this package or add it as an eve dependency (it depends…

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing code, read the installed eve package docs for extensions, tools, and sandboxes as applicable.

    line 5
  2. Very specific:

    Keep this extension free of coding tools.

    line 9
  3. Very specific:

    Keep shared implementation under extension/lib/.

    line 10
  4. Very specific:

    Keep the sandbox exports in extension/lib/sandbox.ts.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

@eve/computer-use Extension Package

This private package is the source of the eve/computer-use extension. It contributes the computer_use tool and the sandbox helpers that install and start the desktop and driver.

Before writing code, read the installed eve package docs for extensions, tools, and sandboxes as applicable.

Boundaries

  • Keep this extension free of coding tools; those belong in @eve/code.
  • Keep shared implementation under extension/lib/; filesystem paths define contribution names.
  • Keep the sandbox exports in extension/lib/sandbox.ts; @eve/code re-exports them for compatibility.

Build and publish

The eve build copies extension/ into packages/eve/src/computer-use/extension and compiles it into the eve package; public entry points are declared in packages/eve/package.json and packages/eve/src/computer-use/. Do not publish this package or add it as an eve dependency (it depends on eve). Import only public eve/* APIs from extension/; third-party imports are bundled into eve's dist. Keep tests under test/scenario/, outside the discovered extension tree. Run typecheck, the scenario tests, eve's build, lint, and package-scoped formatting before completion.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about vercel/eve

The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 55

Talked about on GitHub and Bluesky (55 times).

On GitHub · 48

43 more on GitHub

On Bluesky · 7

2 more on Bluesky

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free