Comet installs the same workflow into many AI coding tools, but each platform exposes different capabilities. Some support Skills, rules, and hooks. Others only support Skills or a shared skills registry.
Platform support grows layer by layer through Skills, rules, and hooks.
Full capability: Skills + rules + hooks
These platforms can receive the richest Comet installation. Hooks can run deterministic checks and help enforce workflow boundaries.
Skills + hooks
CodeBuddy Code supports Comet Skills and deterministic PreToolUse hooks without a separate rules surface.
Skills + rules
These platforms can install Skill instructions and rule files, but they do not expose a compatible hook system.
Skill only
These platforms can receive Comet Skill content, but do not provide first-class rules or hooks.
Capability summary
Comet tracks three installation surfaces:
Special install paths
Different platforms use different directories for project and global configuration. comet init handles these paths for you. It also detects existing files and asks before it replaces user-owned content.
Codex Skills and config use different roots
Codex discovers project and global Skills under .agents/skills. Codex-specific config, rules, hooks, and plugin cache remain under .codex. Update and uninstall migrate Comet-managed legacy .codex/skills content while preserving unrelated Skills and the shared directories. Starting in 0.4.0-beta.5, Codex phase-guard hooks are written to the supported .codex/hooks.json location, and Comet safely migrates its managed entries from the previously generated settings.local.json without changing user-defined hooks or settings (#199).
CodeBuddy hooks preserve existing settings
Project-level and global CodeBuddy installs merge the Comet PreToolUse hook into the corresponding .codebuddy/settings.json. Existing plugins, hooks, and other user settings remain intact. If the JSON is invalid, installation reports the failure and leaves the original file unchanged.
Project-level or global
Use project-level install when the workflow should travel with the repository and be visible to collaborators.
Use global install when you want Comet available across many local repositories on the same machine.
For team projects, prefer project-level install first.
Copy or symlink
Copy mode writes a snapshot of Comet assets into the target platform directory.
Symlink mode creates links for Comet Skills inside the platform’s existing skills/ directory and points them to the shared .comet/skills/ store. It preserves the directory and any local or third-party Skills. The mode is useful for development and fast upgrades, but it depends on platform and filesystem support.
Hooks and executable capability
Hooks can make Comet stricter, but they also execute local commands. Comet documents executable behavior during install and keeps the workflow usable even when a platform only supports Skills.
Verify after install
Run:
Then open your AI coding tool and call:
Last modified on July 16, 2026
