Summary
The current RPC implementation supports multi-turn conversations only through the long-lived JSONL protocol (tunacode rpc). We added a one-shot convenience path (tunacode rpc "..."), but there is still no simple human-friendly multi-turn CLI flow.
Problem
Users who want conversational context across turns currently have to keep tunacode rpc running and manually send JSON commands. That is correct for programmatic integrations, but poor UX for interactive terminal use.
Follow-up scope
- add a friendlier interactive multi-turn shell on top of the existing RPC/session machinery
- preserve use of the saved TunaCode config/default model without requiring repeated flags
- keep the current JSONL RPC mode intact for integrations
- avoid regressing the new one-shot
tunacode rpc "..." path
Context
Summary
The current RPC implementation supports multi-turn conversations only through the long-lived JSONL protocol (
tunacode rpc). We added a one-shot convenience path (tunacode rpc "..."), but there is still no simple human-friendly multi-turn CLI flow.Problem
Users who want conversational context across turns currently have to keep
tunacode rpcrunning and manually send JSON commands. That is correct for programmatic integrations, but poor UX for interactive terminal use.Follow-up scope
tunacode rpc "..."pathContext
tunacode rpc "prompt"tunacode rpc+ JSONL commands