agentsmd
Question: Why does AGENT.md redirect to new AGENTS.md with stripped content?
Problem Description
The website https://ampcode.com/AGENT.md now redirects to https://agents.md, but the new site appears to have stripped substantial content compared to the original. This wouldn't be concerning if it were just a stylistic or location change, but the new page seems to lack meaningful content that was previously available.
Expected Behavior
The redirect should maintain the same level of content and technical detail that was available on the original AmpCode site.
Actual Behavior
The new https://agents.md site appears to have reduced or "stripped" content compared to what was previously available at https://ampcode.com/AGENT.md.
Additional Information
Question: Will this content discrepancy be fixed, or was this an intentional action/project takeover?
The redirect appears to be related to the standardization effort between AGENT.md vs AGENTS.md naming conventions, but the content quality difference raises concerns about whether this was properly coordinated or if content was lost in the transition.
Environment
- Original URL:
https://ampcode.com/AGENT.md - Redirect target:
https://agents.md - Issue observed: Content appears reduced/stripped on the new domain
This seems to be a question for the AMP folks. If there is something specific you’d like to see added to this spec, it would probably be best to request it.
I would like to see some definition of what the AGENTS.md file is, and what is (the minimum) required to be considered to support it.
I am very biased as, independently, I also put up a standarisation site https://agent-rules.org/ that was a bit more casual in tone (similar to SemVer).
As a specification the AMP version needed some work -- it used RFC format/kind of claimed to be an RFC, but wasn't.
And the terms it used for the specification needed some work (from memory it only said "SHOULD use AGENT(S).md", not "MUST", i.e. you could technically comply with their rules and not support the file).
Their examples were also mostly how to set up symlinks, with no actual details on which applications did or didn't support the file.
Overall I think it is better to standardise with a lightweight minimum baseline, then work out the details. I'm planning to redirect my site (and project) to here as well, and I think AMP did the right thing.
As per the prevoius response, if there is something specific you think needs to be included, create a specific issue for that thing (or multiple things if you want multiple changes).
@sgryphon @jsit
I want to offer my sincere apologies for suggesting there had been a surreptitious takeover of the AGENTS.md project. I let the RFC-style wording and trend-setting tone mislead me into thinking this was an “official” change or realignment, and I treated the original AMP article as an infallible source of truth. In reality, AMP simply redirected its page to what appears to be richer, more focused content.
I regret any offense my misunderstanding may have caused. Going forward, I will look for guidance in the places you’ve pointed me to, and I’m grateful for agent-rules.org —I plan to review it thoroughly.