Supported Platforms

Comet installs Skills, Rules, and Hooks in each target platform’s standard directory. Choose one or more platforms in comet init. Comet currently supports 37 AI coding platforms.

A comprehensive overview of all platforms

The following table lists all platforms, platform ids (for CLI --platform <id>), project-level Skill directories, global Skill directories, and the capabilities supported by each.

Complete capabilities (Skill + rules + hooks

”Platform	Platform id	Project Catalogue	Global directory	Rule format	Hooks	Explanation
Claude Code	`claude`	`.claude`	`.claude`	`md`	✅ `claude-code`	Reference platform, supporting PreToolUse hooks
Codex	`codex`	`.agents`	`.agents`	`md`	✅ `claude-code`	Skill uses `.agents/skills`; The configuration, rules and hooks are retained in `.codex`
Amazon Q Developer	`amazon-q`	`.amazonq`	`.amazonq`	`md`	✅ `claude-code`	Reuse the claude code hook format
Devin Desktop (formerly Windsurf)	`windsurf`	`.devin`	`.devin`	`md`	✅ `windsurf`	Write `pre_write_code` hooks; legacy projects are auto-detected under `.windsurf`
GitHub Copilot	`github-copilot`	`.github`	`.github`	`copilot`	✅ `copilot`	Use `.github/instructions/*.instructions.md`
Gemini CLI	`gemini`	`.gemini`	`.gemini`	None (GEMINI.md	✅ `gemini`	The only platform without a regular directory but supporting hooks
Qwen Code	`qwen`	`.qwen`	`.qwen`	`md`	✅ `qwen`
Qoder	`qoder`	`.qoder`	`.qoder`	`md`	✅ `qoder`	Share PreToolUse processing with qwen
Kiro	`kiro`	`.kiro`	`.kiro`	`md`（steering）	✅ `kiro`	The rule is in `.kiro/steering/`, and the hook is an independent `.kiro.hook` file
Grok	`grok`	`.grok`	`.grok`	`md`	✅ `claude-code`	The Skill is in `.grok/skills/`, the rule is in `.grok/rules/`, and the hook is written to `.grok/hooks/comet.json`. The OpenSpec output is generated by Codex and mirrored to `.grok`
Oh My Pi	`oh-my-pi`	`.omp`	`.omp/agent`	`mdc`	✅ `omp`	The Skill is in `.omp/skills/`, the rule uses always-apply MDC, and the Hook uses the `.omp/hooks/pre/comet-hook-router.ts` extension module
CodeBuddy	`codebuddy`	`.codebuddy`	`.codebuddy`	`md`	✅ `codebuddy`	The rule is written into `.codebuddy/rules/`; The PreToolUse hook is merged into `settings.json` to retain the user’s existing configuration
DeepSeek Harness	`dsh`	`.dsh`	`.dsh`	`dsh`	✅ `dsh`	Use Claude compatible OpenSpec integration; Rules are written to the managed `AGENTS.md` block, and Hook configurations are written to `hooks.json`
Trae	`trae`	`.trae`	`.trae`	`md`	✅ `trae`	Write the Hook to `.trae/hooks.json` and use the versioned `PreToolUse` grouping
Trae CN	`trae-cn`	`.trae-cn`	`.trae-cn`	`md`	✅ `trae`	Skill uses `.trae-cn`; Project-level hooks are written to `.trae/hooks.json`, and global hooks are written to `.trae-cn/hooks.json`

Skill + hooks (Random)

“Platform	Platform id	Project Catalogue	Global directory	Hooks	Explanation
WorkBuddy	`workbuddy`	`.workbuddy`	`.workbuddy`	✅ `codebuddy`	Merge the PreToolUse hook into `.workbuddy/settings.json` to retain the existing configuration of the user

Skill + Rules (Without hooks

”Platform	Platform id	Project Catalogue	Global directory	Rule format	Explanation
Cursor	`cursor`	`.cursor`	`.cursor`	`mdc`	The only platform that uses the Cursor MDC frontmatter format
OpenCode	`opencode`	`.opencode`	`~/.config/opencode`	`md`	The OpenCode-style slash command is different for the global directory and the project
Cline	`cline`	`.cline`	`.cline`	`md`	The rule is within `.clinerules/` at the root of the project, not within `.cline/`
RooCode	`roocode`	`.roo`	`.roo`	`md`
Continue	`continue`	`.continue`	`.continue`	`md`
Kilo Code	`kilocode`	`.kilocode`	`.kilocode`	`md`
Auggie	`auggie`	`.augment`	`.augment`	`md`	Augment CLI
Lingma	`lingma`	`.lingma`	`.lingma`	`md`
ZCode	`zcode`	`.zcode`	`.zcode`	`md`	Based on OpenCode, the OpenSpec opencode output will be mirrored to `.zcode/`
MimoCode	`mimocode`	`.mimocode`	`~/.config/mimocode`	`md`	Based on OpenCode, the OpenCode-style slash command + image OpenSpec output

Only Skill (no rules, no hooks

”Platform	Platform id	Project Catalogue	Global directory	Explanation
Kimi Code	`kimicode`	`.kimi-code`	`.kimi-code`	The OpenSpec tool id is `kimi`
Junie	`junie`	`.junie`	No global directory
CoStrict	`costrict`	`.cospec`	No global directory	The directory name is different from the id
Crush	`crush`	`.crush`	No global directory
Factory Droid	`factory`	`.factory`	No global directory
iFlow	`iflow`	`.iflow`	No global directory
Pi	`pi`	`.pi`	`~/.pi/agent`	The global directory is a subdirectory
Antigravity	`antigravity`	`.agents`	`~/.gemini/antigravity`	Projects are completely different from global directories and support CodeGraph
Antigravity 2.0	`antigravity2`	`.agents`	`~/.gemini/config`	Share project-level `.agents/` with Antigravity and run `~/.gemini/config` globally
Bob Shell	`bob`	`.bob`	No global directory
ForgeCode	`forgecode`	`.forge`	No global directory	The directory name is different from the id

Little Fish put platform cards such as Claude Code, Codex, Cursor, Devin Desktop, Gemini CLI, GitHub Copilot and OpenCode into the capability hierarchy handbook

The

platform supports layer-by-layer enhancement of

by Skill, rules, and hooks

Summary of Capabilities

Rule format

Comet supports four rule formats:

Format	Use the platform
`md`	The vast majority of platforms that support rules
`mdc`	Cursor and Oh My Pi; Oh My Pi uses alway-apply MDC
`copilot`	Only GitHub Copilot
`dsh`	Only DeepSeek Harness; Write to the managed `AGENTS.md` block

Hooks format

The 16 Hook platforms in the current list use 11 hook formats:

Hook format	Write to the file	Use the platform
`claude-code`	`settings.local.json`	Claude Code、Codex、Amazon Q、Grok
`qwen`	`settings.json`	Qwen Code
`qoder`	`settings.json`	Qoder
`codebuddy`	`settings.json`	CodeBuddy、WorkBuddy
`gemini`	`settings.json`	Gemini CLI
`windsurf`	`hooks.json`	Devin Desktop (formerly Windsurf)
`copilot`	`hooks/<id>.json`	GitHub Copilot
`kiro`	`hooks/<id>.kiro.hook`	Kiro
`omp`	`hooks/pre/comet-hook-router.ts`	Oh My Pi
`dsh`	`hooks.json`	DeepSeek Harness
`trae`	`hooks.json`	Trae、Trae CN

OpenCode is a platform

OpenCode, ZCode, and MimoCode are all based on the OpenCode runtime and support Opencode-style slash commands and image OpenSpec output

”Platform	Mirroring behavior
OpenCode	Native support
ZCode	Migrate the image of `.opencode/{skills,commands}` to `.zcode/`
MimoCode	Mirror OpenSpec output to `.mimocode/`

Special installation path

The global installation directories of the following platforms are different from the project-level directories:

“Platform	Project-level directory	Global directory
Codex Skill	`.agents`	`~/.agents`
OpenCode	`.opencode`	`~/.config/opencode`
MimoCode	`.mimocode`	`~/.config/mimocode`
Antigravity	`.agents`	`~/.gemini/antigravity`
Antigravity 2.0	`.agents`	`~/.gemini/config`
Pi	`.pi`	`~/.pi/agent`

Global installation on other platforms uses directories with the same name (for example, Claude Code is globally ~/.claude, CodeBuddy is globally ~/.codebuddy, and WorkBuddy is globally ~/.workbuddy). Junie, CoStrict, Crush, Factory Droid, iFlow, Bob Shell, ForgeCode do not support global installation.

WorkBuddy project level Skill in . WorkBuddy/skills/, user level Skill in ~ /. Workbuddy/skills/. Hook blocking only writes to the project-level . Workbuddy/Settings. Json; Global installation does not add global blocking Hook, so there is no need for Hook configuration outside the project.

The Skill discovery root of Codex is different from the configuration root: project and global skills use . Agents/skills, Codex exclusive configuration, rules, hooks and plug-ins are still located in cache .codex. update/uninstall version 0.4.0-beta.4 will migrate the old managed by Comet codex/skills installation, and leave the other Skill and the Shared directory. 0.4.0 - beta. 5 Guard hook rewriting, the Codex stage to the supported . Codex/hooks. Json. Grok Also USES Claude - code hook format, but write . Grok/hooks/comet json And additional matching Grok native write/search_replace tools.

Antigravity and Antigravity 2.0 share project-level .agents/ skills The table of contents, so comet init Both will be selected simultaneously during automatic detection. If you only want to install one of them, you can do so in the interactive installation process (without ) Manually uncheck the other one in —yes.

comet init will automatically detect the existing platform configuration directories in the project and pre-select them. You can also use --yes Skip the interaction and install automatically to all detected platforms.

Choose project-level or global

Installation scope	Suitable scenarios	Features
project	Team projects, warehouse agreements, and the need to submit configurations	The configuration is written to the current project to facilitate collaboration
global	Personal default environment, shared by multiple projects	The configuration is written to the user directory, making it more convenient to switch projects

If you’re not sure, install it at the project level first. It is the easiest for team members to see the same set of Comet behaviors.

Installation mode: Copy vs symbolic link

After comet init and comet update select the platform, they will ask for “install mode”. Starting from 0.4.0-beta.1, a new symlink mode has been added:

“Mode"	"Behavior”	Suitable
Copy (Copy, default)	Copy the skills, rules and scripts of each platform independently to the target directory	The traditional approach requires mutual isolation between platforms and cross-device synchronization (submitted to the warehouse)
“Symlink” (Symbolic link)	Link the Comet-managed skills within the existing `skills/` directory of the target platform and share the `.comet/skills/` central storage	Multi-platform development, save disk space, and want to update all platforms at once

The working mode of Symlink mode

After selecting Symlink, Comet no longer copies Comet Skill for each platform. Instead, it creates symbolic links for Comet Skill in the existing skills/ directories of each platform, pointing to the central .comet/skills/ of the project:

.comet/skills/ ← Central storage (only one copy)
├── comet-open/
├── comet-design/
└── ...
.claude/skills/comet-* →.comet/skills/comet-* (symbolic link created by Comet)
.cursor/skills/comet-* →.comet/skills/comet-* (symbolic link created by Comet)
.agents/skills/comet-* →.comet/skills/comet-* (symbolic link created by Comet)

When running comet update, only the central storage needs to be updated, and it takes effect immediately on all platforms. The terminal summary will display symlink created or symlink creation failed.

Symbolic links rely on file system support. Some Windows Configuration or synchronization tools (such as some cloud disks) may not handle symbolic links correctly. If you encounter any problems, roll back to The Copy mode is fine.

If the target platform already has its own skills/ directory, Comet The directory and the local/third-party skills within it will be retained, and only the links managed by Comet will be created or refreshed.

Which mode is chosen does not affect Comet’s behavior; it only influences how files are landed on the disk. When submitting to the repository, Copy The mode will generate real files; The Symlink pattern generates symbolic links (usually requiring each team member to ) comet init）。

General skills Registry Platform

Some AI coding platforms manage skills through the universal skills CLI registry. For these platforms (including OpenClaw, Hermes, etc.), install the Comet skill package directly using the common command:

npx skills add rpamis/comet

This command pulls the Comet skill package from the common skills registry and installs it to the location expected by the platform without the need for a global Comet installation. It can coexist with comet init without any conflict.

hooks and executable capabilities

Some platforms support hooks. Comet will non-destructively merge the hook configurations it manages and retain the existing configurations of users. If there are already plugins, hooks or other user Settings in the file, Comet will retain them. If the JSON cannot be parsed, the installation will explicitly fail and the original file will remain unchanged.

Verification after installation (not mandatory

comet doctor

If the platform directory, Skill file, script or hooks are missing, doctor will provide a diagnosis. Run when an update is needed:

comet update

Get started

Understand Comet Native

Advanced

Practical scenarios

A comprehensive overview of all platforms

Complete capabilities (Skill + rules + hooks

Skill + hooks (Random)

Skill + Rules (Without hooks

Only Skill (no rules, no hooks

Summary of Capabilities

Rule format

Hooks format

OpenCode is a platform

Special installation path

Choose project-level or global

Installation mode: Copy vs symbolic link

The working mode of Symlink mode

General skills Registry Platform

hooks and executable capabilities

Verification after installation (not mandatory

​A comprehensive overview of all platforms

​Complete capabilities (Skill + rules + hooks

​Skill + hooks (Random)

​Skill + Rules (Without hooks

​Only Skill (no rules, no hooks

​Summary of Capabilities

​Rule format

​Hooks format

​OpenCode is a platform

​Special installation path

​Choose project-level or global

​Installation mode: Copy vs symbolic link

​The working mode of Symlink mode

​General skills Registry Platform

​hooks and executable capabilities

​Verification after installation (not mandatory

A comprehensive overview of all platforms

Complete capabilities (Skill + rules + hooks

Skill + hooks (Random)

Skill + Rules (Without hooks

Only Skill (no rules, no hooks

Summary of Capabilities

Rule format

Hooks format

OpenCode is a platform

Special installation path

Choose project-level or global

Installation mode: Copy vs symbolic link

The working mode of Symlink mode

General skills Registry Platform

hooks and executable capabilities

Verification after installation (not mandatory