agentleFS
pdparchitectpdparchitect/noodle/Computer/AGENTS.md

noodle / Computer

AGENTS.md259 starsChanged 35 days agoApache-2.0View on GitHub

Keep Computer app changes in Computer/CHANGELOG.md and image changes in Computer/Images/CHANGELOG.md. Noodle-side integration changes belong in the main CHANGELOG.md; preserve unrelated entries. Public releases require explicit user approval and the checks in Computer/RELEASING.md. Computer shares Noodle's repository but releases independently: use Computer/VERSION, Computer/CHANGELOG.md and computer-vX.Y.Z tags, with its own update feed. A mainline Noodle release does not release Computer. Integration compatibility depends on protocol capabilities, not matching app versions; coordinate releases when a change requires both apps. See Computer/RELEASING.md. The…

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

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

    Keep Computer app changes in Computer/CHANGELOG.md and image changes in Computer/Images/CHANGELOG.md.

    line 3

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

Noodle Computer release notes

Keep Computer app changes in Computer/CHANGELOG.md and image changes in Computer/Images/CHANGELOG.md. Noodle-side integration changes belong in the main CHANGELOG.md; preserve unrelated entries. Public releases require explicit user approval and the checks in Computer/RELEASING.md.

Independent versioning

Computer shares Noodle's repository but releases independently: use Computer/VERSION, Computer/CHANGELOG.md and computer-vX.Y.Z tags, with its own update feed. A mainline Noodle release does not release Computer. Integration compatibility depends on protocol capabilities, not matching app versions; coordinate releases when a change requires both apps. See Computer/RELEASING.md.

Build

The Xcode project is generated by Tuist from Project.swift; change that, never the generated project.

README.md is for people using Computer; do not document code in it. Follow the no-code-docs skill.

Engine and app

Sources/ComputerEngine runs computers: the library, every kind of computer, their displays, files and terminals, and the provider that serves them to Noodle. It is a library so other apps can host computers too. Sources/NoodleComputer is Noodle Computer's own app: its windows, settings, updater and launch checks. Put what a computer does in the engine and what the app shows around it in the app; the engine never depends on the app.

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.