agentleFS
pheuterpheuter/claude-agent-desktop/AGENTS.md

claude-agent-desktop

AGENTS.md211 starsChanged 12 months agoMITView on GitHub

Electron desktop application for agentic chat with the Claude Agent SDK.

  • Reads credentials
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

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

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create .claude/skills/<skill-name>/SKILL.md with name + description.

    line 39
  2. Very specific:

    Add TypeScript tools under .claude/skills/<skill-name>/scripts/.

    line 40
  3. Very specific:

    Run bun run dev (or rerun scripts/buildSkills.js) to compile binaries into out/.claude/skills/.

    line 41
  4. Distinctive:

    After a series of code changes, always run: lint, typecheck, test, and format commands to ensure the code is working as expected.

    line 63
  5. Distinctive:

    When drafting commit messages, always follow Conventional Commits format.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

Claude Agent Desktop

Electron desktop application for agentic chat with the Claude Agent SDK.

Technology

  • Framework: Electron 39 (main / preload / renderer)
  • Build: Vite 7 via electron-vite
  • UI: React 19 + TypeScript, Tailwind CSS 4
  • Runtime: Bun (package manager, scripts, tests)

Layout

src/
├── main/       # Electron main process (app lifecycle + IPC handlers)
├── preload/    # Context bridge exposing safe IPC APIs
├── renderer/   # React UI
└── shared/     # Types shared between processes
.claude/        # Claude Agent SDK skills compiled into the app bundle
resources/      # Bundled runtime binaries (bun, uv, etc.)
scripts/        # Build hooks (preDev, beforeBuild, afterPack, runtime downloads)
static/         # Icons and static assets

Skills integration

  • Skills live in .claude/skills/<skill-name>/ (each contains SKILL.md + scripts/).
  • Built-in sample: workspace-tools with a depth-limited list-directory utility.
  • scripts/buildSkills.js compiles TypeScript tools in .claude/skills to out/.claude/skills/ using the root dependencies (no separate .claude package) and Bun --compile.
  • Skill TypeScript is checked via the root tsconfig.json; there is no package.json or node_modules under .claude.
  • scripts/preDev.js runs before bun run dev to download runtime binaries and build skills.
  • scripts/beforeBuild.js runs during production builds to download binaries, copy runtime deps to out/node_modules, and build skills.
  • scripts/afterPack.js trims unused vendor assets and confirms .claude/skills are present.
  • On launch, src/main/lib/config.ts syncs the bundled .claude directory into the workspace so skills are available at runtime.

Adding a skill

  1. Create .claude/skills/<skill-name>/SKILL.md with name + description.
  2. Add TypeScript tools under .claude/skills/<skill-name>/scripts/.
  3. Run bun run dev (or rerun scripts/buildSkills.js) to compile binaries into out/.claude/skills/.
  4. Launch the app; the workspace .claude folder will be refreshed automatically.

Commands

bun install       # Install dependencies
bun run typecheck # TypeScript checks
bun run lint      # ESLint
bun run test      # Bun tests
bun run format    # Prettier

Defaults

  • Workspace defaults to ~/Desktop/claude-agent (change in Settings).
  • Anthropic API key can be provided via ANTHROPIC_API_KEY or stored locally in Settings.
  • Bundled tools: bun + uv for runtime execution, portable Git/MSYS2 for Windows.
  • Auto-updates: packaged builds check GitHub releases for updates; set UPDATE_FEED_URL to override the feed if needed (e.g., staging).

Workflow

  • After a series of code changes, always run: lint, typecheck, test, and format commands to ensure the code is working as expected.
  • When drafting commit messages, always follow Conventional Commits format.

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.