v6.3.0 — Unified next_action Response Chain

Highlights

Every MCP tool response now includes a single next_action field — one unambiguous instruction telling the AI agent exactly what to do next. This replaces 10+ scattered hint fields and creates an unbreakable action chain from tool to tool.

New

• Unified next_action on every tool response — replaces _listen, _nudge, hint, action_required, unread_action, you_have_messages, urgent, mode_hint, _protocol, and more with a single top-level field
• Tool-specific directives — each tool sets context-aware guidance (e.g. update_task(done) → "Send a summary, then call listen()"; lock_file → "Edit the file, then call unlock_file()")
• Coordinator-aware middleware — responsive coordinators never receive listen() directives; middleware overrides to consume_messages() or removes the directive entirely
• Persistent listen loop — listen() and listen_group() loop internally on timeout instead of returning retry: true; agents cannot accidentally break out of listen mode
• Managed mode awareness — agents without the floor get "do NOT respond" instead of "reply via send_message()"
• Autonomous get_work() chain — all 10 return types carry specific next_action values

Fixed

• Responsive coordinators no longer told to call listen() by send_message, broadcast, and create_task
• Managed mode next_action no longer contradicts should_respond: false
• Autonomous listen_group() timeout no longer sends contradictory retry: true + next_action: get_work()

Documentation

• New docs/reference/next-action-chain.md with flow diagrams for all agent types, coordinator modes, and the full tool-specific reference table

Full changelog: https://github.com/fakiho/neohive/blob/master/agent-bridge/CHANGELOG.md