agentleFS
Sign inStart free
VercelKnown publishervercel/eve/packages/eve-agent-desktop/AGENTS.md

eve / eve-agent-desktop

AGENTS.md5.8k starsChanged 11 days agoApache-2.0View on GitHub

This published package is the @eve/agent-desktop extension: accessibility-based desktop tools backed by the agent-desktop CLI, plus the @eve/agent-desktop/sandbox helpers that install and start the desktop. Before writing code, read the installed eve package docs for extensions, tools, and sandboxes as applicable. Tests run against the built dist/, so there is no unit tier. Tiers are set by directory: Run typecheck, build, both tiers, lint, and package-scoped formatting before completion.

Adopted by

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

Week 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 projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 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 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub and Bluesky (56 times).

On GitHub · 49

44 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

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

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 extension/lib/sandbox.ts and extension/lib/process.ts free of other extension imports.

    line 11
  3. Very specific:

    Keep shared implementation under extension/lib/.

    line 12
  4. Distinctive:

    Run typecheck, build, both tiers, lint, and package-scoped formatting before completion.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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/agent-desktop Extension Package

This published package is the @eve/agent-desktop extension: accessibility-based desktop tools backed by the agent-desktop CLI, plus the @eve/agent-desktop/sandbox helpers that install and start the desktop.

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

Boundaries

  • Each tool wraps one agent-desktop command; the CLI's argument surface is the contract, checked by test/scenario/conformance.test.mjs.
  • Install only in the consumer's sandbox prepare through installAgentDesktop. Tools never install at tool time; they probe the version, restart a desktop a resumed sandbox lost, and fail with setup guidance otherwise. Bump AGENT_DESKTOP_REVALIDATION_KEY inputs when the install changes.
  • Keep extension/lib/sandbox.ts and extension/lib/process.ts free of other extension imports; they are published as @eve/agent-desktop/sandbox.
  • Keep shared implementation under extension/lib/; filesystem paths define tool names.

Tests

Tests run against the built dist/, so there is no unit tier. Tiers are set by directory:

  • test/integration/: tools and helpers with in-memory fake sandboxes.
  • test/scenario/: real subprocesses. conformance.test.mjs needs the agent-desktop CLI (AGENT_DESKTOP_BIN or on PATH) and live.test.mjs needs AGENT_DESKTOP_LIVE=1 on Ubuntu 24.04+ with sudo; both skip otherwise.
  • test/support/: shared helpers, not tests.

Run typecheck, build, both tiers, lint, and package-scoped formatting before completion.

Download now (ZIP)

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