Summary
When using an ACP / local agent (Claude Code in my case), a successful chat turn is reported immediatly as finished. The web UI treats finished as a terminal status and hides the reply box, so the user cannot continue the same conversation. Multi-turn chat is intended: the bridge already keeps the conversation object and can resume it, and the cloud path correctly leaves normal turns as paused. The ACP bridge incorrectly reports finished after a successful turn.
Area
AI Agent
Expected Behavior
After a successful ACP chat turn, the conversation status should be paused. The reply box should stay available, and a follow-up message should resume the same conversation (same history / local session).
Actual Behavior
After a successful ACP chat turn, the conversation status becomes finished. The UI hides the reply box. The user cannot continue in that conversation and must start a new one (losing in-session agent continuity).
Notes
Root cause: in apps/acp-bridge/src/paca_acp_bridge/runner.py, _run_conversation reports "finished" on success.
Suggested fix: report "paused" instead of "finished" after a successful turn (keep "failed" on errors).
Resume logic already exists in ConversationRunner.start_turn; the API and web UI already support paused for multi-turn chat.
Explicit stop / failure paths should remain unchanged.
Summary
When using an ACP / local agent (Claude Code in my case), a successful chat turn is reported immediatly as finished. The web UI treats finished as a terminal status and hides the reply box, so the user cannot continue the same conversation. Multi-turn chat is intended: the bridge already keeps the conversation object and can resume it, and the cloud path correctly leaves normal turns as paused. The ACP bridge incorrectly reports finished after a successful turn.
Area
AI Agent
Expected Behavior
After a successful ACP chat turn, the conversation status should be paused. The reply box should stay available, and a follow-up message should resume the same conversation (same history / local session).
Actual Behavior
After a successful ACP chat turn, the conversation status becomes finished. The UI hides the reply box. The user cannot continue in that conversation and must start a new one (losing in-session agent continuity).
Notes
Root cause: in apps/acp-bridge/src/paca_acp_bridge/runner.py, _run_conversation reports "finished" on success.
Suggested fix: report "paused" instead of "finished" after a successful turn (keep "failed" on errors).
Resume logic already exists in ConversationRunner.start_turn; the API and web UI already support paused for multi-turn chat.
Explicit stop / failure paths should remain unchanged.