duoduo-runtime-admin

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Duoduo Runtime Admin

Duoduo运行时管理

This skill owns host-mode runtime flags, daemon diagnostics, and persistent settings in

~/.config/duoduo/.env

本技能负责主机模式运行时标志、daemon诊断以及存储在

~/.config/duoduo/.env

中的持久化设置。

Start With Runtime Discovery

从运行时排查入手

Confirm host mode with
```
duoduo daemon status
```
.
Read
```
duoduo daemon config
```
before changing persistent settings.
Use
```
duoduo daemon logs
```
when the user is debugging behavior rather than requesting a config change.

Read references/runtime-settings.md for the main host-mode knobs and references/codex-runtime.md before enabling Codex.

用
```
duoduo daemon status
```
确认主机模式。
修改持久化设置前先读取
```
duoduo daemon config
```
。
当用户要排查运行行为而非请求修改配置时，使用
```
duoduo daemon logs
```
。

启用Codex前，请先阅读references/runtime-settings.md了解主要主机模式可调节项，以及references/codex-runtime.md文档。

Persistent Host-Mode Settings

持久化主机模式设置

Edit

~/.config/duoduo/.env

with scripts/update_host_env.py instead of ad-hoc shell edits when you want predictable results.

Typical keys:

```
ALADUO_LOG_LEVEL
```
```
ALADUO_LOG_RUNNER_THOUGHT_CHUNKS
```
```
ALADUO_LOG_SESSION_LIFECYCLE
```
```
ALADUO_TELEMETRY_ENABLED
```
```
ALADUO_CADENCE_INTERVAL_MS
```
```
ALADUO_CODEX_ENABLED
```
```
ALADUO_CODEX_SANDBOX
```

After changing daemon env settings, run:

bash

duoduo daemon restart

unless the user explicitly asked for an edit only.

若要获得可预期的修改结果，请使用scripts/update_host_env.py编辑

~/.config/duoduo/.env

，而非临时手动修改shell配置。

典型配置项：

```
ALADUO_LOG_LEVEL
```
```
ALADUO_LOG_RUNNER_THOUGHT_CHUNKS
```
```
ALADUO_LOG_SESSION_LIFECYCLE
```
```
ALADUO_TELEMETRY_ENABLED
```
```
ALADUO_CADENCE_INTERVAL_MS
```
```
ALADUO_CODEX_ENABLED
```
```
ALADUO_CODEX_SANDBOX
```

除非用户明确要求仅修改配置，否则修改daemon环境变量设置后请运行：

bash

duoduo daemon restart

Codex Runtime Scope

Codex运行时范围

Be precise:

Enabling Codex does not switch all foreground sessions to Codex.
The current runtime gate enables Codex as an optional backend for jobs.
Verify
```
codex
```
is installed and authenticated before enabling it.

Do not describe Codex enablement as "stdio now runs on Codex" unless the runtime actually supports that behavior in the inspected version.

请注意表述精确：

启用Codex不会将所有前台会话切换为使用Codex。
当前运行时开关仅将Codex启用为作业的可选后端。
启用前请先验证
```
codex
```
已安装且完成身份认证。

除非所检查的版本实际支持该行为，否则不要将启用Codex描述为“stdio现在运行在Codex上”。

Cadence And Telemetry

Cadence与Telemetry

Before changing cadence, explain that a shorter interval increases background activity and token usage.
Disabling telemetry persistence stops JSONL writes but does not necessarily suppress every in-process debug log line.
Use
```
duoduo daemon config
```
to inspect the current effective value before claiming what the default is on this machine.

修改cadence前，请向用户说明更短的间隔会增加后台活动量和token消耗。
禁用telemetry持久化会停止JSONL写入，但不一定会抑制所有进程内debug日志行。
声明本机的默认值前，请先用
```
duoduo daemon config
```
检查当前生效值。

Operating Rules

操作规则

Prefer
```
duoduo daemon config
```
over stale documentation when values disagree.
Treat
```
~/.config/duoduo/.env
```
as the persistent source of truth in host mode.
When the user updates the installed
```
@openduo/duoduo
```
package, remind them that
```
duoduo daemon restart
```
is still required because the running daemon is a separate background process.
If runtime behavior still looks wrong after config, restart, and logs have been checked, treat it as a likely duoduo bug and use the public issue flow from ../duoduo-admin/references/issue-reporting.md.
If the request is really about channel install/start/prompt/workspace work, hand off to
```
duoduo-channel-admin
```
.

当数值存在冲突时，优先以
```
duoduo daemon config
```
的输出为准，而非过时的文档。
主机模式下，将
```
~/.config/duoduo/.env
```
视为持久化的可信数据源。
当用户更新已安装的
```
@openduo/duoduo
```
包时，请提醒他们仍需运行
```
duoduo daemon restart
```
，因为正在运行的daemon是独立的后台进程。
如果在检查配置、重启、查看日志后，运行时行为仍然异常，则大概率是duoduo的bug，请按照../duoduo-admin/references/issue-reporting.md中的公开issue提交流程处理。
如果请求实际上是关于渠道安装/启动/prompt/工作区相关的工作，请转交
```
duoduo-channel-admin
```
处理。