QoderWake Digital Workers: Three-Stage Architecture Enables Group Chat AI to Autonomously Decide on Intervention, with Self-Test Costs Comparable to Explicit Mentions
QoderWake designed a three-stage architecture for AI digital workers in group chats—JEV screening, Router routing, and Work execution—allowing digital workers to proactively respond to requests without being @mentioned. Vendor self-tests show that across three task types, the average Credits consumption for proactive triggers is roughly equivalent to explicit @mentions, with slightly longer end-to-end latency.
AI digital workers in group chats face a core decision: when someone posts a message, should they respond proactively? The QoderWake team points out that for digital workers, the key to proactive intervention is not simply spotting work, but first deciding whether to take ownership. This differs from personal agents, which decide whether to participate based on individual user preferences; digital workers have defined organizational roles and must identify who is making a request, who is being asked to act, and who their actions will affect.
QoderWake's solution splits the decision into three stages. The first stage is programmatic checks and rapid JEV initial screening: JEV receives current policies, new messages, and a small amount of background context, outputting an initial screening score; only if this score strictly exceeds the threshold does processing continue to the next stage. The second stage is Router routing decisions: confirming whether the message falls within the digital worker's responsibilities and whether it should take it on now. The Router can retrieve historical messages and tasks to supplement context but does not conduct investigations itself. The third stage is Work execution: once the Router accepts a task, the work proceeds in an independent execution context using the digital worker's working directory, model, and authorized tools, while the Router continues processing subsequent messages. This separation means that time-consuming investigations do not block the routing of other messages.
The vendor conducted paired tests in DingTalk groups: for the same task text and delivery requirements, they ran both explicit @mention triggers and proactive response triggers, comparing Credits consumption and end-to-end time. Results showed that the average Credits usage for proactive responses was roughly equivalent to explicit mentions, with slightly longer end-to-end latency. However, this test has clear boundaries: it only covers three task types (analyzing historical materials, editing technical explanations, and read-only source code checks); costs generated by polling candidates that pass JEV initial screening and proceed to Router but ultimately do not trigger tasks are excluded from the analysis; the scores output by JEV are not calibrated probabilities and do not represent the likelihood of task ownership or business success. These are vendor-reported data, unverified by independent replication.