agentleFS
Sign inStart free
BasedHardwareBasedHardware/omi/CLAUDE.md

omi

CLAUDE.md14k starsChanged 10 months agoMITView on GitHub

Treat AGENTS.md as this repository's instruction file. Every rule for every agent (Claude Code, Codex, and any other) lives there. This file exists only because some tools look for CLAUDE.md by name — it is the one such pointer in the repo. - Start with the root AGENTS.md: cross-component rules plus an index. - When working inside a directory, also read the nearest AGENTS.md at or above it — backend/, app/, desktop/macos/, .github/, web/admin/, omi/firmware/. Those carry the detail the…

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 13 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 5 mentionsOct 2026: 40 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the BasedHardware/omi repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about BasedHardware/omi

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

See all 83

Talked about on GitHub, YouTube, Bluesky and Hacker News (83 times).

On GitHub · 50

45 more on GitHub

On YouTube · 21

16 more on YouTube

On Bluesky · 7

2 more on Bluesky

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat AGENTS.md as this repository's instruction file: Every rule for every agent (Claude Code, Codex, and any other) lives there.

    line 7
  2. Distinctive:

    Start with the root AGENTS.md: cross-component rules plus an index.

    line 11
  3. Very specific:

    When working inside a directory, also read the nearest AGENTS.md at or above it — backend/, app/, desktop/macos/, .github/, web/admin/, …

    line 12
  4. Distinctive:

    Add or change rules in the relevant AGENTS.md.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

Omi — Agent Instructions

<!-- Official guidance for writing these files: CLAUDE.md: https://docs.anthropic.com/en/docs/claude-code/memory AGENTS.md: https://developers.openai.com/codex/guides/agents-md Format spec: https://agents.md -->

Treat AGENTS.md as this repository's instruction file. Every rule for every agent (Claude Code, Codex, and any other) lives there. This file exists only because some tools look for CLAUDE.md by name — it is the one such pointer in the repo.

  • Start with the root AGENTS.md: cross-component rules plus an index.
  • When working inside a directory, also read the nearest AGENTS.md at or above it — backend/, app/, desktop/macos/, .github/, web/admin/, omi/firmware/. Those carry the detail the root file deliberately omits.
  • Add or change rules in the relevant AGENTS.md. Never add instructions here — this file stays a pointer so there is only ever one source of truth to maintain.

@AGENTS.md

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