Skip to content

feat(providers): add Kilo example provider profile - #5716

Open
DenisDupeyron wants to merge 1 commit into
NVIDIA:mainfrom
DenisDupeyron:feat/5630-kilo-provider-profile/DenisDupeyron
Open

DenisDupeyron wants to merge 1 commit into
NVIDIA:mainfrom
DenisDupeyron:feat/5630-kilo-provider-profile/DenisDupeyron

Conversation

@DenisDupeyron

Copy link
Copy Markdown

Summary

Add an example kilo provider profile for the Kilo CLI with the Kilo Gateway.

The profile lets OpenShell resolve KILO_API_KEY as a bearer token only at api.kilo.ai, ai-gateway.kilo.ai and 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 send KILO_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.yaml adds the example profile in the agent category. It declares KILO_API_KEY as a bearer credential, allows api.kilo.ai for account lookups, ai-gateway.kilo.ai for inference and the model list, and us.i.posthog.com for the CLI's telemetry, all read-write with L7 enforcement, and limits them to /usr/local/bin/kilo, the path in the published ghcr.io/kilo-org/kilocode images. Besides the standard fields, its header covers:
    • It names the hosts the profile leaves blocked: ingest.kilosessions.ai and events.kiloapps.io, which would receive the key, and models.dev, without which Kilo falls back to its bundled model catalog. It also says that Kilo's telemetry to us.i.posthog.com uses PostHog's own project key and never carries KILO_API_KEY, which is why that host is allowed.
    • Kilo's bubblewrap sandbox gets a warning: every tool call fails inside OpenShell when a project turns it on. The header recommends ghcr.io/kilo-org/kilocode:latest-openshell, which keeps it off, and keeps /etc/kilo/kilo.json for other images.
    • It also lists the four Kilo settings that stop the blocked connections and the telemetry.
    • It explains that the image's environment reaches the sandbox's main command only.
  • The profile listing test in crates/openshell-server/src/grpc/provider.rs, which enumerates providers/*.yaml, now expects kilo.

Release Notes

N/A

Testing

  • Checks appropriate to the affected code and behavior pass:
    • openshell provider profile lint -f providers/kilo.yaml passes with the 0.1.8 CLI and with the CLI built from this branch.
    • Against a local 0.1.8 gateway with the Docker runtime, the header's lint and import commands work, and openshell provider create --type kilo --from-existing creates the provider from KILO_API_KEY. The header's smoke test replies OK with ghcr.io/kilo-org/kilocode:latest-openshell, which is Kilo 7.8.27 (sha256:325679329acd...). The sandbox log of that run shows Kilo's calls to ai-gateway.kilo.ai and us.i.posthog.com allowed through _provider_kilo, with no denial.
    • The stock ghcr.io/kilo-org/kilocode:7.8.27 image with the same command, followed by the denial review, shows Kilo's GET /api/user call to api.kilo.ai allowed, and models.dev and ingest.kilosessions.ai denied. The variant's own settings remove those denied connections, so the header's smoke test cannot show them.
    • The smoke test needs no </dev/null, which docs(providers): openrouter.yaml smoke test hangs — main-process stdin never reaches EOF for opencode run #3883 found opencode run needs: with the prompt on the command line, kilo run stops waiting for piped stdin after one second.
    • With --env KILO_TELEMETRY_LEVEL=off on top of the three settings the variant already has, the smoke test leaves no denied connection and no telemetry call.
    • Inside a sandbox with the provider attached, KILO_API_KEY holds an openshell:resolve:env:v<digits>_KILO_API_KEY placeholder, and no environment variable holds the real key.
    • The variant's three settings reach the sandbox's main command only. A process started with openshell sandbox exec gets none of them, and --env on openshell sandbox create reaches it too.
    • The notes on Kilo's sandbox come from the same task run in the stock image, then in a derived image and in the published -openshell variant. With a project's kilo.jsonc turning 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, and kilo run exited 0 each time. With /etc/kilo/kilo.json turning it off, in a derived image and in the published -openshell variant, Kilo completed the task with no bubblewrap error.
    • mise run license:check (1560 files with SPDX headers), mise run rust:format:check and mise run rust:lint pass.
    • cargo test -p openshell-providers --lib -- example_profiles and cargo test -p openshell-server --features test-support --lib -- list_provider_profiles_returns_built_in_profile_categories pass, as do the full suites of openshell-providers (143 tests), openshell-cli (758) and openshell-server (2803), the crates that load the example profiles.
    • The repository checks ran on an arm64 Lima VM (aarch64, Ubuntu 26.04), and the header's smoke test and the variant cases ran there and on an x86_64 Ubuntu 26.04 host with matching outcomes.
  • Unit tests added/updated (if applicable): the profile listing test expects kilo.
  • E2E tests added/updated (if applicable): not applicable, example profile only.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable) N/A

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>
@copy-pr-bot

copy-pr-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

All contributors have signed the DCO ✍️ ✅
Posted by the DCO Assistant Lite bot.

@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 18, 2026
@DenisDupeyron

Copy link
Copy Markdown
Author

I have read the DCO document and I hereby sign the DCO.

@purp

purp commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

gator-agent

Blocked

Thanks @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 recheck to refresh DCOAssistant. If the signature is still not recorded, a maintainer should inspect the DCO Assistant workflow before proceeding. Once DCO is green, a maintainer can explicitly ask Gator to review this unchanged head.

Gator metadata
  • Head SHA: 0a6c6cb4bdf182f76c89b7e472a3ce5971628059
  • Gator payload: 13
  • Review: Not started; no code findings issued.
  • Next state: gator:blocked
  • Blocked reason: dco_failing

@purp purp added the gator:blocked Gator is blocked by process or repository gates label Nov 19, 2026
@purp

purp commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

recheck

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gator:blocked Gator is blocked by process or repository gates state:accepted A maintainer decided OpenShell should pursue this issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(providers): add a Kilo example provider profile

2 participants