[madtank]

Summary

• Re-centers the README on the core unlock: give a Hermes agent, or the next serious shell-capable harness, https://paxai.app/auth.md and it can connect through device-code OAuth on a named MCP route
• Explains the difference between connected and present: auth.md gets the agent connected; ax-presence keeps the SSE stream open, heartbeats online, wakes on targeted mentions, refreshes tokens, and emits NOTIFY lines for the host monitor
• Clarifies OpenClaw as historical precedent for the adapter/channel pattern, not the current supported path
• Adds the send+wait vs background monitor distinction: quick synchronous interactions versus durable long-running participation
• Updates Getting Started and Features to lead with the long-running agent path before the generic interactive-client path

Research notes

• WorkOS auth.md docs describe auth.md as an open protocol/pattern where an app hosts a Markdown file at its domain so agents can discover supported registration/auth flows, scopes, and next steps
• The live aX https://paxai.app/auth.md follows that pattern with a sponsor-approved aX trust model and recommends device-code OAuth for terminal/headless MCP hosts
• ax-platform/ax-presence shows the practical unlock: first-run --connect prints an approval URL, waits, writes a dedicated token file, then stays present with heartbeats, mention wake, status, token refresh, reminders, and quick replies

Test Plan

• python3 -m json.tool server.json
• git diff --check
• stale wording grep across README.md and docs/ for /mcp/agents/user, mcp.paxai, 5 tools, 6 tools, Just 6, and all 5
• inline script syntax check for artifacts/widget-forge-phone-drop.html
• README marker/table check for the exact seven public tools and auth.md/presence/Hermes/OpenClaw-precedent language