BFlat 5b138b88a4 An ACP chat starts the agent's session again after a failed start, and Stop ends a waiting message (#320) ...

When an ACP agent answered `initialize` with an error (for example, not signed in) and kept running, the error was shown and the turn ended. But the agent's session was never started, and nothing started it later. The next message was queued for a session that never came, so the chat stayed busy. Stop cleared the queue without ending the turn, so every later message was refused as "still working".

- A message sent when the start has failed and nothing is under way now starts the handshake again (`initialize`, then the session). Another failure is reported and ends that message's turn like the first.
- Stop now ends the turn of a message still waiting for the session.

**Verified:** a new test of the protocol core: after a failed `initialize`, the next message sends `initialize` again, a second failure ends its turn, and Stop ends a waiting message. A late answer then sends no prompt. `cargo test -p craft-anything-ai` (184), clippy and fmt pass.

**Not verified:** a live run against an agent that refuses `initialize`.

Fixes #271

2026-11-02 14:53:22 +07:00

..

src

An ACP chat starts the agent's session again after a failed start, and Stop ends a waiting message (#320)

2026-11-02 14:53:22 +07:00

Cargo.toml

Craft Anything

2026-10-31 10:52:14 -04:00