-
Notifications
You must be signed in to change notification settings - Fork 32
Add Kilo CLI to OpenClaw tools.md #1351
Copy link
Copy link
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerskilo-auto-fixAuto-generated label by KiloAuto-generated label by Kilokilo-triagedAuto-generated label by KiloAuto-generated label by Kilo
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerskilo-auto-fixAuto-generated label by KiloAuto-generated label by Kilokilo-triagedAuto-generated label by KiloAuto-generated label by Kilo
Type
Fields
Give feedbackNo fields configured for issues without a type.
Context
Users report OpenClaw says the Kilo CLI is "not available" or
"not found". The kilo binary is baked into the image and
TOOLS.md has a static Kilo CLI section — but TOOLS.md is only
seeded on fresh provision. Existing instances provisioned
before the section was added never got it. There's no dynamic
update like there is for Google Workspace. Fix: add dynamic
injection in bootstrap, gated on KILOCLAW_KILO_CLI.
Changes
Add updateToolsMdKiloCliSection(env, deps) following the
updateToolsMdGoogleSection pattern (lines 391-443):
currently in container/TOOLS.md lines 9-17, wrapped in markers
section (skip if marker already present). If flag is
absent/false, remove stale section if present.
(line 499)
Wrap the existing Kilo CLI section (lines 9-17) with the same
markers so the dynamic function recognizes it on fresh installs
and doesn't duplicate it.
Add tests for updateToolsMdKiloCliSection:
present