ghostty-fleet / macos
AGENTS.md1 starsChanged 8 months agoMITView on GitHub
- Use swiftlint for formatting and linting Swift code. - If code outside of macos/ directory is modified, use zig build -Demit-macos-app=false before building the macOS app to update the underlying Ghostty library. - Use macos/build.nu to build the macOS app, do not use zig build (except to build the underlying library as mentioned above). - Build: macos/build.nu [--scheme Ghostty] [--configuration Debug] [--action build] - Output: macos/build/<configuration>/Ghostty.app (e.g. macos/build/Debug/Ghostty.app) - Run unit tests directly with macos/build.nu --action test - The…
3 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- steventsvik/Tellurionword for word, first seen Oct 15, 2026
- ghostty-org/ghosttyword for word, first seen Oct 8, 2026
- steventsvik/GhosttyEXTREMEword for word, first seen Mar 14, 2026
Other versions3 projects use a version of this.
Word for word · 3
- ghostty-org/ghostty★ 64k100% same
- steventsvik/GhosttyEXTREME★ 141100% same
- steventsvik/Tellurion★ 141100% 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 31,542 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- example/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- peekaboo-fork-uiSkill
- swiftui-componentsSkill
- writing-commit-messagesSkill
- xcodebuildmcpSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use swiftlint for formatting and linting Swift code.
- Very specific: line 4
If code outside of macos/ directory is modified, use zig build -Demit-macos-app=false before building the macOS app to update the …
- Very specific: line 7
Use macos/build.nu to build the macOS app, do not use zig build (except to build the underlying library as mentioned above).
- Very specific: line 11
Run unit tests directly with macos/build.nu --action test
≈ “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.
Files
macOS Ghostty Application
- Use
swiftlintfor formatting and linting Swift code. - If code outside of
macos/directory is modified, usezig build -Demit-macos-app=falsebefore building the macOS app to update the underlying Ghostty library. - Use
macos/build.nuto build the macOS app, do not usezig build(except to build the underlying library as mentioned above).- Build:
macos/build.nu [--scheme Ghostty] [--configuration Debug] [--action build] - Output:
macos/build/<configuration>/Ghostty.app(e.g.macos/build/Debug/Ghostty.app)
- Build:
- Run unit tests directly with
macos/build.nu --action test
AppleScript
- The AppleScript scripting definition is in
macos/Ghostty.sdef. - Guard AppleScript entry points and object accessors with the
macos-applescriptconfiguration (useNSApp.isAppleScriptEnabledandNSApp.validateScript(command:)where applicable). - In
macos/Ghostty.sdef, keep top-level definitions in this order:- Classes
- Records
- Enums
- Commands
- Test AppleScript support:
(1) Build with
macos/build.nu(2) Launch and activate the app via osascript using the absolute path to the built app bundle:osascript -e 'tell application "<absolute path to build/Debug/Ghostty.app>" to activate'(3) Wait a few seconds for the app to fully launch and open a terminal. (4) Run test scripts withosascript, always targeting the app by its absolute path (not by name) to avoid calling the wrong application. (5) When done, quit via:osascript -e 'tell application "<absolute path to build/Debug/Ghostty.app>" to quit'
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
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.

