Integrate harness
Skill a5c-ai/babysitter/packages/adapters/skills/integrate-harness
Use when adding a new agent harness (CLI-based coding agent) adapter to adapters. Covers capability audit, adapter scaffold, session parsing, auth detection, hooks/plugins wiring, tests, and docs.From its SKILL.md
npx -y skills add a5c-ai/babysitter --skill integrate-harnessAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.3 KB, 768 tokens by cl100k_base, as published. Nobody here has run it
integrate-harness
Goal: produce a production-quality XAdapter extends BaseAgentAdapter with full test coverage and documentation, matching the level of the existing 11 adapters (claude, codex, cursor, gemini, opencode, openclaw, copilot, hermes, pi, omp, adapters-remote).
Checklist
- Capability audit — read the harness's CLI docs. Fill in every
AgentCapabilitiesfield. Unknown? Set conservatively (false) and note in PR. - Create
packages/adapters/src/<name>-adapter.tsextendingBaseAgentAdapter. Required:agent,displayName,cliCommand,minVersion,hostEnvSignals,capabilities,models[],defaultModelId,configSchema,buildSpawnArgs,parseEvent,detectAuth,getAuthGuidance,sessionDir,parseSessionFile,listSessionFiles,readConfig,writeConfig. - Session parsing — if the harness stores JSONL sessions, delegate to
parseJsonlSessionFile; otherwise write a custom parser and unit-test each event shape. - Hooks — if the harness supports native hooks, override
writeNativeHookand mirror intoHookConfigManager. If not, rely on the base class's virtual hooks. - Plugins — if it supports MCP servers under
mcpServersin its config JSON, flipsupportsPlugins: true, addpluginFormats: ['mcp-server'], and delegate tomcp-plugins.ts(see cursor/gemini/opencode/openclaw for the pattern). - Register — add to
packages/adapters/src/index.tsexports and to the default registry inpackages/core/src/client.ts(if applicable). - Tests — in
packages/adapters/tests/<name>-adapter.test.ts:- capability shape
buildSpawnArgsfor a few representativeRunOptionsparseEventfor each JSONL type the harness emitsdetectAuthfor authenticated + unauthenticated states- session file parsing from a real fixture (redacted)
- If plugins: add the adapter to
mcp-plugins-parity.test.ts.
- CLI audit test — ensure
packages/cli/tests/commands-audit.test.tspasses (it exercises every adapter via the built CLI). - File-size limit — each source file must stay under 400 effective lines (
local/max-file-lines). Split helpers into sibling modules if you're close. - Docs — add a row to the README capabilities matrix and a paragraph in
docs/02-agents/<name>.md. - Changeset —
npm run changeset, pickminor(new adapter), summarize.
Verification
npm run typecheck
npm run lint
npm test
npx vitest run packages/adapters/tests/<name>-adapter.test.ts
All existing tests must continue to pass — no regressions in commands-audit.
Common pitfalls
- Forgetting to add the adapter to the default registry →
commands-audit.test.tswon't exercise it. - JSONL parsers that assume a single event per line — some harnesses emit arrays.
- Auth detection that reads env vars synchronously at construction time instead of
detectAuth()— breaks testability. buildSpawnArgsreturning the string"undefined"for missing options — always gate withif (options.X != null).- Hook writers that overwrite rather than merge — use
appendJsonHookorappendYamlHook.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.