Known Working Agents

May 13, 2026 ยท View on GitHub

This matrix tracks agent and harness compatibility with the local Akephalos passport bundle.

Keep updates small and factual. Do not add secrets, local auth paths, or private machine details.

Agent/harnessOSInstall methodMCP supportSync supportStatusCaveats
CodexWindowsLocal CLI from source/packageYesYesknown-workingReads the local bundle and can use Git sync through .akephalos.
CursorWindowsLocal CLI from source/packageYesYesknown-workingCursor may need its MCP config reloaded before it sees resources.
Pi IDEPi/LinuxLocal CLI from source/packageNot confirmedYesknown-workingScheduled sync has been tested at a 15-minute interval with a private passport.
HermesTBDManual CLI setup; see Hermes integrationTBDTBDunknownNext harness test. Keep status below known-working until read, memory append, sync, and pull-back are confirmed.
Claude CodeTBDTBDTBDTBDunknownNot tested yet.
OpenClawTBDTBDTBDTBDunknownNot tested yet.

Updating The Matrix

Use a fictional or non-sensitive passport for public reports. Then add or update the structured entry:

akephalos harness add "Hermes"
akephalos harness mark "Hermes" --status configured

Update this markdown table with the OS, install method, MCP support, sync support, status, and caveats.

Run:

akephalos harness check
akephalos doctor
akephalos scan
akephalos sync-status

Use known-working only after the harness has completed a full read, memory append, sync, and pull-back check.

Valid statuses are:

  • unknown
  • detected
  • configured
  • known-working
  • broken
  • unsupported