agentleFS
Sign inStart free
devswhadevswha/ovis/server/AGENTS.md

ovis / server

AGENTS.md1.8k starsChanged 10 days agoMITView on GitHub

- Never let an attachment outlive its last client, and never resize from an attach that asked to keep_size or from an observer. - Never refresh an OAuth token in usage.ts: the CLIs rotate refresh tokens, so our refresh signs the user's CLI out. Report expired and leave it to the CLI. - Revoking every paired device must never reopen the LAN, and a devices.json that will not parse is not a first installation. - Only proof says herdr is…

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:

    Never let an attachment outlive its last client, and never resize from an attach that asked to keep_size or from an observer.

    line 3
  2. Very specific:

    Never refresh an OAuth token in usage.ts: the CLIs rotate refresh tokens, so our refresh signs the user's CLI out.

    line 5
  3. Distinctive:

    Only proof says herdr is gone: on Windows a dead daemon's pid is reused by the next process.

    line 9
  4. Very specific:

    Only Vite's fingerprinted /assets/ may be cached long.

    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

server/

  • Never let an attachment outlive its last client, and never resize from an attach that asked to keep_size or from an observer.
  • Never refresh an OAuth token in usage.ts: the CLIs rotate refresh tokens, so our refresh signs the user's CLI out. Report expired and leave it to the CLI.
  • Revoking every paired device must never reopen the LAN, and a devices.json that will not parse is not a first installation.
  • Only proof says herdr is gone: on Windows a dead daemon's pid is reused by the next process.
  • The user's API keys go upstream only; no response or error message carries one.
  • Only Vite's fingerprinted /assets/ may be cached long; sw.js, the manifest and the app shell must revalidate, or an installed PWA is pinned to an old build.

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 devswha/ovis

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

See all 7

Talked about on GitHub (7 times).

On GitHub · 7

2 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. devswha/herdr-web-ui★ 1.5k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 28,693 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 repository4 other files it gives its agents.

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