Files

zhi 08f42bfd92 fix: skip rules-based no-reply override when turn manager allows agent

When the turn manager determines it's an agent's turn (checkTurn.allowed),
the rules engine's evaluateDecision() could still override the model to
no-reply with reason 'rule_match_no_end_symbol'. This happened because:

1. The sender of the triggering message (another agent) was not in the
   humanList, so the rules fell through to the end-symbol check.
2. getLastChar() operates on the full prompt (including system content
   like Runtime info), so it never found the end symbol even when the
   actual message ended with one.

Fix: return early from before_model_resolve after the turn check passes,
skipping the rules-based no-reply override entirely. The turn manager is
the authoritative source for multi-agent turn coordination.

Tested: 3-agent counting chain ran successfully (3→11) with correct
NO_REPLY handling when count exceeded threshold.

2026-03-09 21:16:53 +00:00

commands

refactor(policy): move policy CRUD to /dirigent_policy slash command with explicit channelId

2026-03-08 07:17:23 +00:00

core

debug(turn): add mention-override and ensureTurnOrder state transition logs

2026-03-08 07:38:33 +00:00

hooks

fix: skip rules-based no-reply override when turn manager allows agent

2026-03-09 21:16:53 +00:00

policy

refactor(plugin): extract live config and policy store modules

2026-03-07 22:38:11 +00:00

tools

refactor(policy): move policy CRUD to /dirigent_policy slash command with explicit channelId

2026-03-08 07:17:23 +00:00

channel-resolver.ts

refactor(plugin): extract channel/decision parsing modules and unify channelId resolution

2026-03-07 22:12:27 +00:00

decision-input.ts

refactor(plugin): extract channel/decision parsing modules and unify channelId resolution

2026-03-07 22:12:27 +00:00

index.ts

refactor(policy): move policy CRUD to /dirigent_policy slash command with explicit channelId

2026-03-08 07:17:23 +00:00

moderator-presence.ts

feat: complete Dirigent rename + all TASKLIST items

2026-03-03 10:10:27 +00:00

openclaw.plugin.json

refactor(installer): rename to install.mjs, remove record/restore flow, add --no-reply-port and wire config port

2026-03-08 06:38:33 +00:00

package.json

feat: complete Dirigent rename + all TASKLIST items

2026-03-03 10:10:27 +00:00

README.md

chore(cleanup): remove discord-control-api sidecar and stale config/docs hooks

2026-03-08 06:19:41 +00:00

rules.ts

refactor(installer): rename to install.mjs, remove record/restore flow, add --no-reply-port and wire config port

2026-03-08 06:38:33 +00:00

turn-manager.ts

fix(turn): keep mention override speaker/order when membership refresh runs

2026-03-08 07:56:26 +00:00

README.md

Dirigent Plugin

Hook strategy

message:received caches a per-session decision from deterministic rules.
before_model_resolve applies providerOverride + modelOverride when decision says no-reply.
before_prompt_build prepends end-marker instruction + scheduling identifier instruction when decision allows speaking.

Rules (in order)

non-discord -> skip
bypass sender -> skip
end symbol matched -> skip
else -> no-reply override

Config

See docs/CONFIG.example.json.

Required:

noReplyProvider
noReplyModel

Optional:

enabled (default true)
discordOnly (default true)
listMode (human-list | agent-list, default human-list)
humanList (default [])
agentList (default [])
channelPoliciesFile (per-channel overrides in a standalone JSON file)
schedulingIdentifier (default ➡️) — moderator handoff identifier
enableDirigentPolicyTool (default true)

Unified optional tool:

dirigent_tools
- Discord actions: channel-private-create, channel-private-update, member-list
- Policy actions: policy-get, policy-set-channel, policy-delete-channel
- Turn actions: turn-status, turn-advance, turn-reset
bypassUserIds (deprecated alias of humanList)
endSymbols (default ["🔚"])
enableDiscordControlTool (default true)
Discord control actions are executed in-plugin via Discord REST API (no discordControlApiBaseUrl needed)
discordControlApiToken
discordControlCallerId
enableDebugLogs (default false)
debugLogChannelIds (default [], empty = all channels when debug enabled)

Per-channel policy file example: docs/channel-policies.example.json.

Policy file behavior:

loaded once on startup into memory
runtime decisions read memory state only
direct file edits do NOT affect memory state
dirigent_tools policy actions update memory first, then persist to file (atomic write)

Moderator handoff format

When the current speaker NO_REPLYs, the moderator bot sends: <@NEXT_USER_ID>➡️

This is a non-semantic scheduling message. The scheduling identifier (➡️ by default) carries no meaning — it simply signals the next agent to check chat history and decide whether to speak.

Slash command (Discord)

/dirigent status
/dirigent turn-status
/dirigent turn-advance
/dirigent turn-reset

Debug logging:

set enableDebugLogs: true to emit detailed hook diagnostics
optionally set debugLogChannelIds to only log selected channel IDs