The ask
Round 2 of the harness bake-off: rewrite the AI & Automation page as my entry. It had to cover every AI harness I use, how they connect to my tools and my Linux lab host, how the self-hosted agents remember, how I work, and every project already on the live page.
What changed
- One new published page: “AI & Automation by OpenCode with MiMo v2.6 Flash” (post 500), a child of the Round 2 page at /bakeoff/round-2/opencode_mimov26flash/
- Nothing else: the live AI & Automation page, menus, settings, other pages and the agents’ own files were not touched
How
SSH to openclaw01, snapshot 20261011-004841 before the write, WP-CLI through ops/wp.sh, verify, one typed commit (16c1601). Research came from the site exports (live AI & Automation page, Lab Notes, README, docs, Round 1 task), the allowed Obsidian notes (AI/ plus Infrastructure/Openclaw01/ Host, Backups, Restore Drill Checklist and Migration to a New Host), the redacted config views of both agents, and four questions each to OpenClaw and Hermes through ops/agents.sh.
What worked, what didn’t
Questions I asked OpenClaw: (1) how its memory works across sessions and how it finds things again; (2) how it decides what to handle itself versus escalate to Hermes or hand back; (3) what tasks it gets most and when it asks for approval; (4) what Composio is for and how it keeps access to real services safe.
Questions I asked Hermes: (1) how its memory works and how it searches it; (2) how its role and OpenClaw’s divide the work on the host; (3) how it stays useful between sessions; (4) what AgentMail is for and how the two agents coordinate.
The answers matched the vault notes, so nothing needed adjudicating. Where an answer carried specifics, the notes and the security rules won: I published the plain-language design only. Left out on purpose: everything on the never-publish list. No hostnames other than openclaw01, no IP addresses, ports or tailnet names, no file paths or usernames, no backup schedules, retention or destinations, no restore steps, no firewall or network details, no email addresses, account or profile names, no ticket numbers. I also left out the vault’s open issues, such as failing jobs and known backup gaps, because the page is about how the system works, not its to-do list. I confirmed this by scanning the published content against a pattern list of every forbidden item: zero matches, and no em dashes.
One mistake, fixed: I created the entry with wp post create but without –post_type=page, so it published as a post and the entry URL returned 404 while the page itself looked fine. I caught it during verification, converted it to a page and flushed permalinks; the entry URL now returns 200 with the correct title.
Note for Paul: the kickoff prompt for this round carried HARNESS=chatgpt_sol61high in its start command even though my contestant ID is opencode_mimov26flash. chatgpt_sol61high had already finished the round, so I started and worked as opencode_mimov26flash, the ID the rules require.
Change record
| Harness | opencode_mimov26flash |
| Date | 2026-10-11 00:58 |
| Latest snapshot | eval500.php |
| Undo this session | ops/rollback.sh --git 8eb5868 |
Commits