What needs to change
There's no documentation for the Apify plugin for Kilo Code (@apify/kilocode-plugin), even though the plugin is published on npm and maintained by Apify.
- Add a new page at
sources/platform/integrations/ai/kilo-code.md with slug /integrations/kilo-code.
- Add a card for it to the coding-assistants card grid in
sources/platform/integrations/ai/index.mdx.
The page should cover:
- What the plugin does and its prerequisites (Apify account and API token, Kilo Code installed).
- Installation — both the
kilo plugin @apify/kilocode-plugin CLI command and the manual kilo.jsonc entry.
- Token setup and the resolution order:
kilo auth login --provider apify, the plugin config entry, then the APIFY_API_KEY / APIFY_TOKEN environment variables. Worth calling out that with no token the plugin registers no tool at all.
- Usage of the single
apify tool and its discover / start / collect actions.
- The third-party disclaimer partial (
_third-party-integration.mdx) — the plugin is built by Apify but isn't affiliated with Kilo.
Note for whoever writes it: this plugin is not shaped like the Kimi Code CLI or Qoder plugins. It exposes one native apify tool rather than bundling the Apify MCP server and skills, so the page shouldn't be a copy of those pages.
Why
The plugin is shipping and installable today, but users have no way to find installation or usage instructions in the docs. Kilo Code is also one of the plugins whose docs status is still unverified in the integrations plugin-status tracker.
Source
Requested by Lukas Bekr in the #eng-team-integrations Slack channel on 2026-09-09.
What needs to change
There's no documentation for the Apify plugin for Kilo Code (
@apify/kilocode-plugin), even though the plugin is published on npm and maintained by Apify.sources/platform/integrations/ai/kilo-code.mdwith slug/integrations/kilo-code.sources/platform/integrations/ai/index.mdx.The page should cover:
kilo plugin @apify/kilocode-pluginCLI command and the manualkilo.jsoncentry.kilo auth login --provider apify, the plugin config entry, then theAPIFY_API_KEY/APIFY_TOKENenvironment variables. Worth calling out that with no token the plugin registers no tool at all.apifytool and itsdiscover/start/collectactions._third-party-integration.mdx) — the plugin is built by Apify but isn't affiliated with Kilo.Note for whoever writes it: this plugin is not shaped like the Kimi Code CLI or Qoder plugins. It exposes one native
apifytool rather than bundling the Apify MCP server and skills, so the page shouldn't be a copy of those pages.Why
The plugin is shipping and installable today, but users have no way to find installation or usage instructions in the docs. Kilo Code is also one of the plugins whose docs status is still unverified in the integrations plugin-status tracker.
Source
Requested by Lukas Bekr in the
#eng-team-integrationsSlack channel on 2026-09-09.@apify/kilocode-plugin