Skip to content

codeburn context: support Kimi Code sessions #850

Description

@KENSHI601

codeburn context (added in 0.9.15, experimental) currently only accepts --provider claude|codex. The Kimi Code provider landed in 0.9.19 (#750, #747) for usage tracking, but its sessions can't be opened in the context browser yet.

Request: extend codeburn context to Kimi Code.

Where the data is: Kimi Code writes per-session "wire" logs at
~/.kimi-code/sessions/<workspace-slug>/<session-id>/agents/<agent>/wire.jsonl

It's JSONL, one typed event per line. Record types observed on the current CLI:

  • metadataprotocol_version, created_at
  • config.updatemodelAlias, systemPrompt, thinkingEffort
  • llm.requestmodel, maxTokens, kind, provider
  • llm.tools_snapshot — full tool list per request (tools, hash)
  • context.append_message / context.append_loop_event — the actual context content (messages, tool results)
  • usage.record — per-call usage token fields + usageScope
  • turn.prompt, tools.set_active_tools, permission.set_mode

So the building blocks mirror what claude/codex offer: context content in context.append_*, tool schemas in llm.tools_snapshot, exact token anchoring via usage.record.

Happy to provide a redacted sample wire.jsonl if that helps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions