@Waker

@Waker connects multiple Wakers to one IM conversation. When a member sends a task, QoderWake selects a Waker by its name, responsibilities, and routing rules. If no Waker clearly matches, the default Waker responds. Use @Waker when ongoing work needs several roles, such as product, frontend, backend, and QA. Each task is still handled by one Waker, while tasks, topics, and memory continue to build up in the conversation.

​

Prepare your Wakers

Confirm that:

• At least one Waker is enabled and available. Give different Wakers clear names and responsibilities so routing can distinguish them.
• You know which workspace each Waker may access and whether members may change Waker settings from IM.

​

Configure and maintain IM connections

Open IM in the primary navigation and select IM Connections. This page manages the channel identities that QoderWake uses to receive and reply to messages. The following connection types are supported. What appears on the page may vary by account, product version, or feature configuration.

​

Supported connection types

​

Add a connection

1. Under IM Connections, select a connection type offered on the page, then select its add or configure action.
2. Complete the authorization shown in the dialog. Bot and AI Assistant connections normally require credentials from the corresponding platform. For channels that support QR-code setup, scan and confirm as instructed.
3. If the dialog includes an access policy, select it for the intended scope:
   • Approval Required: New conversations must be approved before they can use the connection. Use it when access needs to be controlled.
   • Open Access: Eligible conversations can use the connection immediately. Enable it only after reviewing the access scope. This option is not available for every channel.
4. If reply style, progress messages, or default reply settings are available, configure them for the expected recipient experience. Options vary by channel.
5. Save the setup, return to the list, and confirm that the connection is available or Connected.

In addition to configuring QoderWake, create bot and AI Assistant identities on the corresponding IM platform, grant the required message or event permissions, and add them to the target conversation. A DingTalk Account sends replies as the signed-in user. Connect only conversations that should receive automated replies, and review the AI sending indicator and human-review responsibility before enabling it.

​

Edit, disable, or remove a connection

Under IM Connections:

• Select the edit icon to update credentials and the message or default reply settings available for that channel.
• Turn off the connection switch to stop receiving and replying while retaining the setup. Test the connection again after re-enabling it.
• Removing a bot or AI Assistant immediately stops message handling and may leave existing conversations as Invalid. After adding the same identity again, check whether those conversations return as Paused, then resume them manually.
• Removing a personal account stops reply-as-you behavior and clears monitored conversations for that connection. Check for active conversations before removal.

​

Enable @Waker

You can connect a conversation by enabling it directly, approving an in-chat request, or using a pairing code. Available methods vary by IM channel and product configuration.

​

Method 1: Enable it from @Waker Conversations

Open IM in the primary navigation, select @Waker Conversations, and then select Enable @Waker. Setup has two steps.

​

Choose an IM connection

1. Select the IM connection that will receive and send messages.
2. If the required identity is not listed, select Add more connections and complete authorization or enter the bot credentials shown on the page.
3. Confirm that the connection is available, then select Next.

One connection can serve multiple conversations. Do not add the same identity twice. To update credentials, status, or connection settings, edit the existing entry under IM Connections.

​

Connect a conversation and configure responders

1. Select Direct or Group, then search for and select the conversation.
2. Under Assigned Wakers, select one or more Wakers.
3. Set the Waker best suited to general requests as the default. It responds when neither an explicit request nor a routing rule identifies another Waker.
4. Select each assigned Waker and configure:
   • Response model: Applies only to the selected Waker.
   • Allow Waker Configuration Changes: Allows IM messages to change that Waker's configuration. Leave it off unless the conversation requires this capability.
   • Conversation File Protection: Restricts access to the workspace and added directories and prevents access to files and commands outside that scope.
   • Workspace: Select the directory used for tasks. Use Add Directory only when another location is required.
5. Add Custom Routing Rules that reflect the team's division of work. The rules apply to all assigned Wakers in this conversation and take priority when the router chooses an owner for a new task. For example:
   Copy

   Send requirements, PRDs, and release communication to Product Manager. Send APIs, backend implementation, reviews, and CI/CD to Backend Engineer. Send pages and interaction implementation to Frontend Developer.
   
6. Review the conversation, default Waker, models, permissions, and directories, then select Enable @Waker.

​

Method 2: Mention the bot and approve the request

With approval-required access, a group member can request pairing from the conversation and an administrator can approve it:

1. Confirm that the bot connection is available, then add the bot to the target group conversation.
2. In the group, mention the bot and send a message. If the conversation is not paired, the bot confirms that the request has been submitted.
3. Return to QoderWake, open IM → @Waker Conversations, and select Pending in the upper-right corner.
4. Verify the bot, conversation name, conversation type, and requester. Select the assigned Wakers, then review the default Waker, model, workspace, and permissions.
5. If the source and configuration are correct, select Approve. The message that triggered the request is assigned to the selected Waker after approval. Confirm that the conversation appears as Active.

Select Ignore for unknown or unauthorized requests. After a request is ignored, another request appears only when a group member sends a new message.

​

Method 3: Use a pairing code

When the page offers pairing codes, configure the responders in QoderWake first, then complete pairing from the target conversation:

1. Under @Waker Conversations, select the add or enable action, then choose the IM connection and assigned Wakers.
2. Select Add via pairing code or Generate Code, then review the model, workspace, and other settings.
3. Copy the complete pairing-code message and send it to the target group or direct conversation within 10 minutes. Do not send only a screenshot or post the code in an unrelated conversation.
4. After the conversation reports that pairing succeeded, return to @Waker Conversations and confirm that the conversation appears with a normal status.

A pairing code becomes invalid after it is used successfully and also expires after 10 minutes. Generate a new code instead of reusing or forwarding an expired code.

​

Use @Waker in a conversation

After setup, find the conversation under Enabled @Waker Conversations, confirm its status is Active, and turn on its @Waker switch. Use the conversation as follows:

• Describe the goal, scope, and expected result. QoderWake selects the Waker that best matches the task.
• To direct a task, explicitly include the Waker's name or responsibility.
• For a follow-up, state that you are continuing the current task. To create separate work, explicitly say that it is a new task and provide the new goal.
• When checking progress or cancelling work, identify the task or topic so the request is not treated as new work.

Mention requirements vary by IM channel. In a test conversation, mention the bot or authorized account as required by that channel and confirm the conversation's @Waker switch is on.

​

Manage enabled conversations

@Waker Conversations supports table and card views. Search by conversation or Waker, or filter by assigned Waker and chat type. For each conversation, you can:

• Edit the assigned Wakers, default Waker, models, directories, permissions, and routing rules.
• Pause message handling without removing the setup.
• Delete the connection. You must enable or pair it again before it can be used.
• Turn the @Waker switch on or off for intelligent routing in that conversation.

Common statuses include:

​

Verify and roll out

Use a test group or direct conversation before expanding access:

1. Send a task with a clear role and confirm that the expected Waker responds.
2. Send a task without a clear role and confirm that the default Waker responds.
3. Test a follow-up, a separate new task, progress lookup, and cancellation. Confirm that tasks are not created or linked incorrectly.
4. Verify workspace, file-protection, and configuration-change permissions. The Waker must not access or modify unauthorized content.
5. Confirm that the sending identity, reply content, and delivered artifacts meet the team's requirements.

After these checks pass, expand access gradually to production conversations. Whenever you change a connection, assigned Waker, model, directory, permission, or routing rule, verify it with a new message first. If no reply arrives, check in this order:

1. The IM connection is available.
2. The conversation status is Active.
3. The conversation's @Waker switch is on.
4. The assigned Wakers are online and enabled.
5. The channel's mention requirement is satisfied.
6. The model, workspace, and permissions are available.

For a personal DingTalk connection, if contact or group search is unavailable, complete the DingTalk DWS connection and sign-in shown on the page, then retry.