What I do
- •Provide Kimi CLI integration guidance for Ode agent providers.
- •Document reliable non-interactive invocation patterns using
--print. - •Explain session reuse (
--session), working directory scoping (--work-dir), and JSONL output parsing. - •Call out automation implications like implicit YOLO behavior in print mode.
When to use me
Use this when adding or debugging the kimi provider in Ode, especially command construction, streaming output parsing, or script/CI behavior.
Ask clarifying questions if you need model/auth-specific setup beyond CLI invocation.
Recommended invocation pattern
- •Base command:
kimi --print --output-format stream-json --session <id> --work-dir <cwd> -p <prompt> - •For final-only text output:
--final-message-only(or--quietshortcut) - •For structured pipelines:
--input-format=stream-json --output-format=stream-json
Integration notes for Ode
- •Treat print mode as auto-approved execution (
--yolois implicit). - •Parse stdout as JSONL message stream (
assistantand optionaltoolmessages). - •Keep provider model input hidden in UI unless explicitly needed.
- •Keep session IDs stable per Slack thread and rotate when environment changes.