Hermes Connect; login/home aliases; work MCP; process runs; coworker channels
What shipped.
- Hermes is on the landing Connect strip with a paste-ready YAML MCP snippet and
clients/hermes.md, same pattern as OpenClaw. /app/loginredirects to/loginand/app/homerenders Home (they were 404).work_update/work_getMCP responses validate again so agents can complete and read work items.- Capture inventory distinguishes Grok Bot and Cloud Agent writers from plain Desktop Cursor when Connect-inherit clients identify themselves.
- Process runs let Board Pickup create and advance Scan → Claim → Launch → Notify (MCP +
/v1). - First-party coworker channels store append-only transcripts on the org plane (session JWT only; no console UI yet).