Repository navigation
Recording a Kilo session: what I learned pointing orca at kilo 7.5.9 #13988
xizhuomengcontin
started this conversation in
4. Show and tell
Replies: 0 comments
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.
I spent a while getting a Kilo session recorded end to end and four things surprised me. Posting them because they are about Kilo, not about my tool, and they cost me real time to find.
Disclosure: I work on OrcaReplay (Apache-2.0). Everything below was verified by running kilo 7.5.9, not by reading source.
1.
OPENAI_BASE_URLdoes nothingKilo keeps the provider origin in its own config, not in an environment variable — inherited from the OpenCode family it forks from. So exporting
OPENAI_BASE_URLleaves the run talking straight past whatever you pointed it at, and nothing warns you. If you have tried to put Kilo behind a gateway and seen an empty log, this is why.The route that works is TLS interception rather than origin redirection:
2. Kilo checks entitlement locally, before opening a connection
This one cost me the most time. Pick a model your account cannot use and Kilo fails with
You need to sign in to use this model— and sends nothing at all. No request leaves the machine, so any capture looks broken when in fact it was never given anything to capture.kilo/kilo-auto/freeis reachable without a paid plan, which is what makes any of this testable for someone without a subscription.3. The system prompt is ~45k characters
The recorded run carried two
model.request/model.responsepairs, one request at 44,973 characters, opening with:Worth knowing if you are reasoning about context budget.
4. It also posts to
us.i.posthog.comProduct telemetry, not a model API. Anything doing traffic capture should leave it tunnelled and unread rather than sweeping it up — mine does.
What the recording is for
Once captured, the session can be served back:
Kilo runs again against the recorded bytes — no provider called, no tokens spent.
egress=blockedmeans model-provider egress; replay still executes recorded tool calls for real, so it is not a sandbox.There is also a marketplace PR open at Kilo-Org/kilo-marketplace#260. Not asking for review here — mentioning it so this is not read as a duplicate.
Happy to be corrected on any of the four, especially the entitlement check.
All reactions