Settings and Management

Select Settings in the lower-left corner to open global settings. These changes affect the current account or local runtime rather than one Waker. Validate each change with a new chat or a limited task.

​

Preferences

​

Display language

Display language controls navigation, buttons, prompts, and system text. After selecting Chinese or English, wait for the page to switch and review the primary entries. User-created Waker, Group, project, and chat names are not translated automatically. When preparing English documentation, use English test data in addition to changing the product language.

​

AI response language

AI response language sets the default for new chats. It does not rewrite existing chats and does not override a language explicitly requested in the current message. Create a new task to verify the change. An existing chat continuing in its previous language is expected.

​

Theme

Select light, dark, or follow system. Use one theme consistently when capturing a workflow so localized screenshots have comparable layout and contrast.

​

System

​

Start at login

When enabled, QoderWake starts its background process after operating-system sign-in. Local environments that host scheduled or remote work should enable it, while still ensuring that the user session, network, and account remain available.

​

Keep system awake

When enabled, QoderWake prevents the computer from sleeping while chats or automated tasks are running. This is useful for long local jobs. Keep-awake does not prevent network loss, shutdown, sign-out, or service crashes.

​

Allow remote configuration management

This is an experimental feature. When enabled, the device synchronizes Waker metadata, Profile or Context, Skills, and connector configuration, and can accept changes from a remote console. Authentication secrets, tokens, and keys remain local. Before enabling it:

• confirm that the account and device are within the intended management scope;
• keep local-directory and external-connector permissions limited;
• ensure configuration changes can be audited;
• rerun a limited validation after a remote change.

Keep it disabled when remote maintenance is unnecessary.

​

Network diagnostics

Network diagnostics tests authentication, machine registration, and the Work return path between QoderWake and the gateway.

1. Open Network Diagnostics.
2. Select Start diagnostics.
3. Wait for every check and record the failed item and error message.
4. Fix the network, proxy, authentication, or registration issue and rerun the test.
5. After all checks pass, return to the original feature and perform the real task.

A successful diagnostic confirms the base connection only. It does not prove that a particular connector, model, or external account has the correct permission.

​

Manage environments and devices

Environments & Devices lists local and remote environments, connection state, application version, and the number of Wakers on each environment.

​

Review a device

1. Select Refresh to retrieve the latest state.
2. Identify the device from its local/remote label, name, version, and online status.
3. Confirm that a Waker that needs local files runs on the correct device.

If a device is offline, check the host power, QoderWake service, network, and account. Online status alone does not prove that a local directory exists.

​

Add a device

Select Add device and follow the account and device connection process. After completion, verify that:

• the new device appears online;
• its application version meets the requirement;
• a Waker can be assigned to the environment;
• a read-only task can access an intended local file.

​

Unbind a device

Before unbinding, check:

1. Wakers running on the device;
2. Autonomous Work that depends on it or its directories;
3. Groups, projects, and @Waker chats using those Wakers;
4. configurations and artifacts that must be migrated or retained.

Unbinding does not migrate Wakers or files. Stop automatic triggers and resolve dependencies first.

​

Update the application

Updates displays the current version, update channel, downloaded version, and available actions.

1. Complete or stop running work and save important artifacts.
2. Review the current version and update information.
3. Download or install as directed. If a restart is required, restart immediately or at an appropriate maintenance time.
4. Reopen the console and verify the effective version.
5. Check Wakers, devices, projects, connectors, and one critical task.

An application update does not replace connector reauthorization, project-path checks, or Autonomous Work regression testing. Validate a new version on a test device before broad production rollout.

​

Validate setting changes

​

Troubleshooting