agent-harnesseslisted

# Agent Harnesses Operate the selected coding-agent host without conflating its configuration, permissions, or lifecycle with another host. Antigravity has its own [agy](../agy/SKILL.md) owner. ## Workflow Every host follows these steps; read only the matching guide for its specifics and required resources. 1. **Inspect the installed contract**: run the host's `--version` and `--help`; identify the surface (CLI, app, IDE, or cloud), workspace, configuration scope, and the session to start or resume. 1. **Refresh evolving details**: read the relevant official page and changelog before relying on flags, settings, models, or feature availability. Compare with installed help, which can omit supported flags; report version gaps before applying a newer recipe, and keep release-specific details upstream. 1. **Use the documented interface** for the session, configuration, or extension. Resolve configuration precedence and permission scope before changing execution behavior; hooks and extensions execute code. 1. **Verify** the result, resulting artifacts, and the host's own instruction or skill discovery. Use [agent-project](../agent-project/SKILL.md) for shared instruction layout and [mcp-setup](../mcp-setup/SKILL.md) for MCP registration. ## Workstation hooks On the `fmind/dot` workstation, managed hooks call `dot agent hook notify` for desktop notifications; `dot agent session sync` captures sessions from each harness's own store. Restart open harnesses after changing hook co