How KOS connects to AI tools and other systems
There are several kinds of connection. Each has its own support status, and “compatible” never implies a bundled subscription or a partnership.
Connection types
| Type | What it means | Status |
|---|---|---|
| Provider instruction adapters | Optional Codex, Claude, and Gemini adapters in Starter Kit 1.2.0. | Validated in v1.2.0 |
| Local Skills and Power-Ups | Local package validation, installation, enable/disable, updates, rollback and uninstall. Not a hosted marketplace. | Included in v1.2.0 |
| API transports | Programmatic exchange between KOS and a provider’s API | Not yet verified |
| MCP connections | Model Context Protocol servers that expose KOS files to compatible clients | Not yet verified |
| Markdown portability | Read and edit the files with compatible tools; no automatic external import service is established by this release. | File-based workflow |
| Linked sources | References to material that stays in another system | Not yet verified |
| Synchronization | Keeping KOS context consistent across devices or people; see Open Sync | Vision |
Release evidence covers the named adapters and local package lifecycle. API transports, MCP services, and external connectors are separate capabilities; they are not implied by adapter support.
You bring your own AI tools
Using KOS with an AI tool requires your own access to that tool. Compatibility does not include a provider subscription, automatic import of chat history, or a partnership with the provider.
Check a specific tool
The compatibility matrix lists each environment and how support was verified.
Local packages
Skills and Power-Ups can run on Community without Pro. Each package declares compatibility, permissions, and licensing; entrypoints do not execute automatically.
Read the v1.2.0 package guide