Repository navigation
Vouch request: DenisDupeyron #5632
Closed
DenisDupeyron
started this conversation in
Vouch Request
Replies: 2 comments
|
/vouch |
0 replies
|
@DenisDupeyron has been vouched by @purp. You can now submit pull requests to OpenShell. Welcome aboard. Please read CONTRIBUTING.md before submitting. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What do you want to work on?
I'd like to add an example provider profile for Kilo,
providers/kilo.yaml, which I proposed in #5630. I work at Anaconda, which owns Kilo, that OpenShell doesn't list yet as an available provider.The profile follows the existing agent profiles:
KILO_API_KEYas a bearer credential, scoped to the Kilo Gateway atapi.kilo.ai,ai-gateway.kilo.aiand the CLI's telemetry host, for/usr/local/bin/kiloin the published OpenShell image,ghcr.io/kilo-org/kilocode:latest-openshell. As in #3904, the change would be the YAML file and its entry in the profile listing test, with no docs.Why this change?
I ran Kilo in OpenShell 0.1.8 with the Docker runtime, and it works with a scoped profile, without any change to OpenShell itself. I found what Kilo needs mostly by reading the denials in the sandbox logs, and I wrote it down in the comments at the top of the YAML file so the next users don't have to figure it out the hard way like I did. Besides
api.kilo.ai,ai-gateway.kilo.aiand the telemetry host, Kilo tries three hosts, two of which would receive the key if allowed.Also, Kilo's own bubblewrap sandbox can't start inside OpenShell, so it must be forced off, or every tool call will fail. Kilo publishes a separate image for OpenShell to address this problem automatically, along with a few smaller ones such as the attempts to reach those three hosts above.
Checklist
All reactions