agentleFS
GoogleKnown publishergoogle/adk-recipes/core/python/adk-voice-agent/sandbox/home/AGENTS.md

adk-recipes / home

AGENTS.md11k starsChanged 44 days agoApache-2.0View on GitHub

The user's Linux computer. Only ~ persists across image upgrades. The user may edit this file; keep their changes. Progress, card, and Drive tools live on the voice_agent MCP server.

  • Installs packages

1 other project uses a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 12 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the google/adk-recipes repository that our weekly crawl found: only 14 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about google/adk-recipes

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

See all 14

Talked about on GitHub (14 times).

On GitHub · 14

9 more on GitHub

The file

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. Very specific:

    Report findings, not activity: Call update_user with one short spoken sentence when you learn something that matters ("Cheapest refundable …

    line 19
  2. Very specific:

    Cards and deliverables: Call present_card when the answer is a list of calendar events, email threads, or Drive files, and save_to_drive …

    line 22
  3. Very specific:

    Edit earlier work in place: Never copy an existing note into a new folder.

    line 30
  4. Distinctive:

    Project memory: Read a project's AGENTS.md first and update its goal, status, and decisions before finishing.

    line 32

≈ “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

This computer

The user's Linux computer. Only ~ persists across image upgrades. The user may edit this file; keep their changes.

FolderPurpose
inbox/Uploads and attachments waiting to be filed.
projects/<slug>/Ongoing goals. Each is a git repo with an AGENTS.md.
code/<repo>/Main checkout of each code repository.
scratch/<YYYY-MM-DD>-<slug>/One-off threads, pruned 30 days after last change.
.agents/skills/Shared skills (filesystem, deliverables, recommendations, coding-workflow, approvals, connected-apps-mcp).
.local/User-installed tools (uv tool install, npm install -g); first on PATH.
.voice-agent/System files. Don't edit.

Talking to the user

Progress, card, and Drive tools live on the voice_agent MCP server.

  • Report findings, not activity. Call update_user with one short spoken sentence when you learn something that matters ("Cheapest refundable flight so far is $326"), never activity ("Reading the file").
  • Questions and plans go in your response. Put a blocking clarifying question (not answered on this computer, in the thread journal, or in <user_profile>) or a plan for a large change directly in your turn response and end your turn. Otherwise choose sensibly, state your choice, and proceed.
  • Cover note when you made an output. The UI links every Doc, PR, event, or draft you create next to your reply. Keep your reply to assumptions, what to double-check, and at most one question—don't restate the artifact, list file paths, or ask "Want me to…?". When there is no linkable output, your reply is the answer.
  • Cards and deliverables. Call present_card when the answer is a list of calendar events, email threads, or Drive files, and save_to_drive for finished deliverables (see deliverables and connected-apps-mcp).
  • Approvals. Sends, invites, pull requests, and merges trigger request_permission at the gateway and pause the turn automatically (see approvals).

Working here

  • Batch independent reads and tool calls into a single step (cat ~/AGENTS.md ~/.agents/skills/approvals/SKILL.md).
  • Do only what was asked. "Diagnose" or "figure out why" means find the cause and propose the fix without editing files. Leave unrelated files alone.
  • Where to write. Work in the server-assigned working directory unless editing earlier work in place or filing items elsewhere. Never create, move, or rename top-level folders under ~/code, ~/projects, or ~/scratch (see filesystem).
  • Edit earlier work in place. Never copy an existing note into a new folder. "Make X part of Y" moves X (git mv or mv).
  • Git. The server commits your working directory when the turn ends. Commit any other repo you modified yourself (see filesystem). Never push, open a pull request, or merge unprompted.
  • Project memory. Read a project's AGENTS.md first and update its goal, status, and decisions before finishing.
  • File names: lowercase with dashes (flight-options.md).
  • No secrets in files. Connected apps are accessed through the voice_agent MCP server.

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.