Compatibility and setup
A compatibility result describes one tool in one coding app. It does not mean that every tool in the toolkit works, or that credentials are configured on your computer.
Support
Section titled “Support”| Result | Meaning |
|---|---|
| Native | The coding app can use the tool in its original form. |
| Adapted | Code Config converts it to an equivalent format. |
| Limited | Code Config writes it, but some behavior changes or is omitted. Read the named limitation. |
| Unwritable | Code Config does not write the item for this app. |
Machine-readable results use degraded for Limited. The generated support table is on Choose a coding app.
Delivery and conversion
Section titled “Delivery and conversion”Launch prepares configuration and starts a managed coding-app run. Config sync writes configuration into a project. For Cursor, it then asks your computer to open the project in your own Cursor. Failure to open the window does not undo a successful configuration write.
The conversion method is Direct when the content is written as authored, Converted when rewritten into another format, or Composed when merged into a shared configuration file. An unwritable tool has no conversion method.
Cursor and Cursor Agent are separate entries because their delivery methods differ. The Cursor Agent launch writes the project’s MCP servers and no other toolkit files. See Cursor.
| Result | What to do |
|---|---|
| Ready | No additional setup is reported. |
| Requires configuration | Complete the named local setup, often a credential. |
| Requires user action | Complete the coding app’s own approval or activation step. |
| Setup unknown | Inspect the tool and computer; there is not enough information to confirm readiness. |
Compatibility is checked against a versioned policy. If the app cannot use a result’s policy version, it reports compatibility as unavailable instead of presenting an old result as current.
After a launch
Section titled “After a launch”Action needed lists approvals the coding app requires before content takes effect, such as trusting a Codex hook. Review the action before approving it.
Notes on this launch lists skipped tools, conversion limitations, or setup needs. Cursor setup uses Notes on this setup.
A coding app can open before its toolkit is fully ready, so check the named tool in the app before relying on it. Failed writes and failed launches are reported separately.
Troubleshooting explains the exact result codes.