Replies: 4 comments
-
Beta Was this translation helpful? Give feedback.
-
|
+1, my error log |
Beta Was this translation helpful? Give feedback.
-
|
@ZENOTME As you said, we should increase the buffer limit to 100MB in acp when creating stdio streams like in wire. I've created a PR to fix this issue. Before the PR is merged and released, you can manually modify the "~/.local/share/uv/tools/kimi-cli/lib/python3.13/site-packages/kimi_cli/acp/__init__.py" file by referring to the implementation in the PR, and then we’ll be able to use it happily and smoothly 😊. |
Beta Was this translation helpful? Give feedback.
-
Thanks @cjnchk ! For now I use another way to bypass this limit: disable file capability in acp client so that the agent will read file in agent rather than depends on acp client.
I think this solution can work for most of case but may also not be suitable for reading big file cases (e.g. file bigger than 100MB). One solution could be to allow response in a stream way using multiple messages. I'm not sure where it's compliant with the specification: https://agentclientprotocol.com/protocol/file-system |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Kimi Code CLI is running?
main
Which open platform/subscription were you using?
kimi code
Which model were you using?
No response
What platform is your computer?
No response
What issue are you seeing?
Problem Summary
When using ACP (Agent Communication Protocol) over stdio, the server process crashes with LimitOver
runError when the client sends a single-line JSON-RPC message exceeding 64KB (the default asyncio.S
treamReader buffer limit). E..g the client is responible to read big file.
Error Log
Stack trace points to:
Root Cause Analysis
LimitOverrunError when the buffer is full but no separator is found
e writer to pause
the process to exit with code 1
Current Workaround
Increase the buffer limit to 100MB when creating stdio streams:
reader, writer = await acp.stdio_streams(limit=100 * 1024 * 1024)
What steps can reproduce the bug?
Config ACP client config to have file read capability so that the agent will request the ACP client to read the file.
What is the expected behavior?
No response
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions