docs(acp): drop stale 'deferred to v0.2' from README header - #87
Conversation
PR #86 implemented session/resume, session/set_mode, and session/set_config_option, but the README header still said reverse-RPC paths are 'deferred to v0.2'. That line conflated the three new client->agent methods (now done) with the reverse-RPC surface (still deferred), and v0.2 isn't accurate framing for the latter either since those methods only land when external ACP agents (future acp-client) need them. Replaces the line with an explicit per-method enumeration in the status block, splitting client->agent (all eleven implemented) from reverse-RPC (deferred). Points at the Methods table for full status.
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
PR #86 shipped
session/resume,session/set_mode, andsession/set_config_option, but the acp README header still said reverse-RPC paths are "deferred to v0.2". That line conflated:session/request_permission,fs/*,terminal/*— still deferred, but "v0.2" isn't accurate framing for them either since they only land when external ACP agents need them viaacp-client)Change
Replaces the misleading status line with explicit per-method enumeration:
fs/{read,write}_text_file,terminal/{create,kill,output,release,wait_for_exit})No code changes.
Test plan
acp/src/handler.rs