Implementations
Agents that read your HUMANS.md, and how to set each one up. Every entry links to the documentation it relies on.
| Agent or tool | How it reads HUMANS.md | Status |
|---|---|---|
| Claude Code | Add @~/.humans/me.md to ~/.claude/CLAUDE.md. Claude Code expands @path imports (docs). | Works today |
| Codex | Codex has no import syntax for AGENTS.md (docs). A SessionStart hook that prints ~/.humans/me.md adds it as context (docs). | Works today |
| HUMANS.md skill | Compiles your free text into fields, shows you a preview, and applies the profile of the person you are writing to. | In progress |
| HUMANS.md MCP server | Returns the profile of a person, or the merged profile of a group, to any agent with an MCP client. Serves the fields only. | In progress |
| Slack | A custom profile field named HUMANS.md holds the fields, so an agent reading Slack can find them. | Specified, not built |
| Humanload | Humanload will read your HUMANS.md, if you have one, and count whether your agents keep to it. Made by cmdAI, like this format; HUMANS.md never requires it. | Planned |
Codex: the SessionStart hook
The hook prints your profile; Codex adds plain text from a SessionStart hook to the session as developer context. The exact hook file format is in the Codex hooks documentation; the command itself is:
cat ~/.humans/me.mdAdd your implementation
Your agent, editor or tool reads HUMANS.md? Open an issue on the HUMANS.md repository with a link to your documentation, and we add a line to this page. Implementations follow ยง 6 of the spec: serve the fields, never the free text, and never let a profile grant a permission.