Repository navigation
feat(providers): add Kilo example provider profile - #5716
DenisDupeyron wants to merge 1 commit into
Conversation
Add an example kilo agent profile for the Kilo CLI with the Kilo Gateway. The profile lets the proxy resolve the KILO_API_KEY placeholder as a bearer token only at api.kilo.ai, for account lookups, at ai-gateway.kilo.ai, for inference, and at us.i.posthog.com, for the CLI's telemetry, and only for /usr/local/bin/kilo, where the published ghcr.io/kilo-org/kilocode images install Kilo, so the sandbox never holds the key. Kilo's telemetry uses PostHog's own project key and does not send KILO_API_KEY. The header comments name the Kilo hosts the profile leaves blocked, two of which would receive the key. They point to the OpenShell variant of the Kilo image, which keeps Kilo's own bubblewrap sandbox off and stops Kilo from trying the blocked hosts, say that its environment reaches the sandbox's main command only, and show how to get the same behavior with another image. The only code change is the entry in the profile listing test, which enumerates providers/*.yaml. Signed-off-by: Denis Dupeyron <ddupeyron@anaconda.com>
|
All contributors have signed the DCO ✍️ ✅ |
|
I have read the DCO document and I hereby sign the DCO. |
BlockedThanks @DenisDupeyron, your DCO signature matches the text required by the repository workflow. I checked the current-head checks and the failed DCOAssistant log: the visible failure predates your signature, but the required check still reports failure. Code review is paused until that process gate clears. Branch Checks and Helm Lint also await the test mirror. Action required: @DenisDupeyron or a maintainer, post a comment containing only Gator metadata
|
|
recheck |
Summary
Add an example
kiloprovider profile for the Kilo CLI with the Kilo Gateway.The profile lets OpenShell resolve
KILO_API_KEYas a bearer token only atapi.kilo.ai,ai-gateway.kilo.aiand the CLI's telemetry host, and only for/usr/local/bin/kilo, so the sandbox never holds the key. Kilo's telemetry uses PostHog's own project key and does not sendKILO_API_KEY. The header tells operators which Kilo hosts stay blocked and how to keep Kilo's own sandbox off, since it cannot run inside OpenShell. The header also points to the published OpenShell variant of the Kilo image.Related Issue
Closes #5630
Changes
providers/kilo.yamladds the example profile in theagentcategory. It declaresKILO_API_KEYas a bearer credential, allowsapi.kilo.aifor account lookups,ai-gateway.kilo.aifor inference and the model list, andus.i.posthog.comfor the CLI's telemetry, allread-writewith L7 enforcement, and limits them to/usr/local/bin/kilo, the path in the publishedghcr.io/kilo-org/kilocodeimages. Besides the standard fields, its header covers:ingest.kilosessions.aiandevents.kiloapps.io, which would receive the key, andmodels.dev, without which Kilo falls back to its bundled model catalog. It also says that Kilo's telemetry tous.i.posthog.comuses PostHog's own project key and never carriesKILO_API_KEY, which is why that host is allowed.ghcr.io/kilo-org/kilocode:latest-openshell, which keeps it off, and keeps/etc/kilo/kilo.jsonfor other images.crates/openshell-server/src/grpc/provider.rs, which enumeratesproviders/*.yaml, now expectskilo.Release Notes
N/A
Testing
openshell provider profile lint -f providers/kilo.yamlpasses with the 0.1.8 CLI and with the CLI built from this branch.openshell provider create --type kilo --from-existingcreates the provider fromKILO_API_KEY. The header's smoke test repliesOKwithghcr.io/kilo-org/kilocode:latest-openshell, which is Kilo 7.8.27 (sha256:325679329acd...). The sandbox log of that run shows Kilo's calls toai-gateway.kilo.aiandus.i.posthog.comallowed through_provider_kilo, with no denial.ghcr.io/kilo-org/kilocode:7.8.27image with the same command, followed by the denial review, shows Kilo'sGET /api/usercall toapi.kilo.aiallowed, andmodels.devandingest.kilosessions.aidenied. The variant's own settings remove those denied connections, so the header's smoke test cannot show them.</dev/null, which docs(providers): openrouter.yaml smoke test hangs — main-process stdin never reaches EOF for opencode run #3883 foundopencode runneeds: with the prompt on the command line,kilo runstops waiting for piped stdin after one second.--env KILO_TELEMETRY_LEVEL=offon top of the three settings the variant already has, the smoke test leaves no denied connection and no telemetry call.KILO_API_KEYholds anopenshell:resolve:env:v<digits>_KILO_API_KEYplaceholder, and no environment variable holds the real key.openshell sandbox execgets none of them, and--envonopenshell sandbox createreaches it too.-openshellvariant. With a project'skilo.jsoncturning the sandbox on, the stock image failed the task with 100 and 82 bubblewrap errors in cases b and c of the first run, with 76 in case b of the second, and with 89 in case b on x86_64, andkilo runexited 0 each time. With/etc/kilo/kilo.jsonturning it off, in a derived image and in the published-openshellvariant, Kilo completed the task with no bubblewrap error.mise run license:check(1560 files with SPDX headers),mise run rust:format:checkandmise run rust:lintpass.cargo test -p openshell-providers --lib -- example_profilesandcargo test -p openshell-server --features test-support --lib -- list_provider_profiles_returns_built_in_profile_categoriespass, as do the full suites ofopenshell-providers(143 tests),openshell-cli(758) andopenshell-server(2803), the crates that load the example profiles.kilo.Checklist