Settings, Data & Diagnostics

#Settings manages this device's experience and runtime environment

Open Settings to configure the Agent browser, Chat presentation, privacy, startup, data directory, and local runtime. Some options only change presentation; others change how the Agent reaches a browser or where it reads local material. Read each option before changing it.

APP CAPTUREThe English light-theme Settings page with Agent, Chat, and App sections.

#Agent Settings: Browser Mode

Standalone

The Agent launches an isolated Chrome instance without the accounts, cookies, or extensions in your everyday browser. This is appropriate for most standard automation and for teams that want work sign-ins separated from a personal browser.

If a target site requires authentication, sign in inside the isolated browser. Being signed in to your everyday Chrome does not sign in the Standalone browser.

CDP (Connect to your Chrome)

The Agent connects to your own Chrome and can use its existing accounts, cookies, and extensions. Choose it for work that must reuse an existing sign-in or browser extension, understanding that the Agent is then operating in your real browser environment.

TK Copilot asks for confirmation before the first switch. It closes the current Chrome and relaunches it with remote debugging; unsaved browser work can be lost. Chrome then opens with TK Copilot on future starts. On Windows, websites may require one new sign-in after the first switch, while extensions, bookmarks, and history remain available.

Save page drafts, forms, and pending actions before switching. Keep Standalone when the task does not require your existing browser state.

#Chat Settings

These three switches only change how Chat presents the run. They do not change business approval rules or grant new operating permission.

Show agent processing status

Shows states such as processing, using a capability, and generating while a reply is pending. Enable it to tell that a long analysis or multi-step task is still active; disable it for a quieter Chat view.

Preserve tool call records

Keeps execution entries inline in Chat after the conversation ends. Enable it when operators need to review what the Agent did. Disable it when only the final response matters.

Collapse long messages

Automatically collapses Agent messages longer than about 15 lines. It does not remove content, and each message can still be expanded. This reduces scrolling in long analysis reports.

#App Settings

Accent color

Choose blue, orange, emerald, rose, violet, gold, crimson, Tiffany, or gray for the interface accent. This only changes visual emphasis such as buttons and selected states; it does not change business data or Agent behavior.

Privacy Mode

Privacy Mode masks phone-binding QR codes, Shop names, Product names, and Product images. Your own Shop aliases remain visible so operators can still distinguish businesses. Use it while recording, streaming, presenting, or sharing a screen with external viewers.

Privacy Mode changes presentation only. It does not delete source data or replace account permissions and organizational data policy. Check the visible page for any other sensitive material before sharing it.

#Tutorial Mode

The tutorial switch controls in-product walkthroughs. Enable it for new teammates learning the interface and disable it when an experienced operator no longer needs repeated guidance. It does not affect the website manual or disable product capabilities.

#Startup: Start TK Copilot on login

When enabled, TK Copilot starts after you sign in to the computer. Enable it on devices expected to keep Customer Service, Affiliate, or Scheduled Task work available, and make sure the device is not routinely powered off or asleep.

This switch only starts the app. Continued business operation also depends on network access, models, channels, Shop authorization, and the relevant business configuration.

#Data Directory

The OpenClaw state directory stores Agent memory, documents, and skills. Settings shows the current path and labels it Default or Custom.

Change

Select Change and choose an existing folder. Use stable, persistent storage with sufficient free space. Restart TK Copilot after the change; the new path is not used until restart.

Changing the path tells TK Copilot where to read state next time; it does not by itself copy the old directory into the new one. If existing memory, documents, or skills must be retained, back them up and verify that the migrated directory is complete.

Reset to default

Reset to default appears while a custom directory is active. After restart, TK Copilot uses the default directory again. Resetting changes the path selection; it does not delete files in the former custom directory.

#Upload Logs

After signing in, the Data Directory section shows Upload Log File. It sends the current application log to Support to investigate startup, connection, or runtime problems. Settings reports when the log does not exist yet, exceeds the 10 MB limit, or is being uploaded too frequently.

Logs can contain operating details needed for troubleshooting. Upload them when requested by Support and according to your organization's data-handling rules. A successful upload does not fix the issue automatically; also provide the reproduction time, steps, and observed behavior.

#Telemetry & Privacy

Send anonymous usage statistics controls anonymous operational reporting. Settings lists the scope explicitly.

Collected:

• app starts and stops;
• feature use, such as configuring channels or changing settings;
• error reports without personal data; and
• runtime statistics such as uptime and performance.

Not collected:

• conversation content;
• API keys or credentials;
• custom prompts; or
• personal information.

Telemetry is separate from Shop-data synchronization, channel messages, and manual log upload. Disabling telemetry does not delete business data already stored on the device.

#System Dependencies

Install Dependencies opens a separate installer that checks and installs Git, Python, Node.js, and uv for the Agent runtime.

Use it when:

• initial dependency setup did not complete;
• Diagnostics reports a missing or unusable dependency; or
• an operating-system upgrade or software cleanup made a previously available command unavailable.

It does not repair exhausted model quota, expired Shop authorization, incorrect channel configuration, or business rules. If the original problem remains after installation, run Diagnostics and read its specific output.

#Diagnostics

The Diagnostics section streams check output and ends with a success or error state plus an exit code.

Run Diagnostics

Select Run Diagnostics to inspect the current local runtime. Use this first during troubleshooting and preserve the first clear error and final exit code.

Run with Auto-Fix

Select Run with Auto-Fix to let the diagnostic apply supported repairs for common problems. Run normal Diagnostics and read the problem before choosing Auto-Fix. It cannot top up a model plan, complete a third-party login, renew Shop authorization, or make a human business decision.

Only one diagnostic can run at a time. Settings reports an error if the run exceeds its time limit, the runtime entry point is missing, or the local environment cannot start the diagnostic.

#Troubleshoot by symptom

The Agent cannot open a browser or operate a webpage

1. Confirm that Browser Mode matches the task.
2. Run Diagnostics.
3. Install Dependencies only if the output reports Git, Python, Node.js, or uv as missing.
4. In CDP mode, confirm that Chrome was relaunched by TK Copilot and check the website sign-in again.

Chat does not reply or a business Agent stops

1. Check model and device state in Models, Devices & Runtime.
2. Confirm cloud-model quota and subscription in Billing & Usage.
3. Check the relevant Message Channel and Shop authorization.
4. Run Diagnostics last to determine whether the local runtime is the issue.

A setting did not take effect

• Data Directory changes require a TK Copilot restart.
• A Browser Mode switch must be confirmed, and Chrome must relaunch as prompted.
• If another switch reports a save failure, retry once and then run Diagnostics.

What to prepare before contacting Support

Record the exact time, current page, steps, expected result, and actual behavior. Run Diagnostics once and preserve the first error and exit code. Upload logs if Support requests them. This helps separate a business-configuration issue, subscription or authorization issue, and local-runtime issue.