DEXALIS
常见问题
选购前，你可能想了解。
迭我分身是什么？
迭我分身 DEXALIS 是面向个人与企业的数字分身，产品定位是“人格大脑与行动中枢”。它以消息为入口，结合你的表达习惯、知识和往来记忆，在授权范围内协助沟通、整理事务和推进任务，并逐步连接人员、业务系统与设备。
DEXALIS is a digital counterpart for individuals and businesses, positioned as a personality-aware brain and action hub. Starting with messages, it draws on your communication style, knowledge and authorized relationship memory to assist communication, organize matters and advance tasks. Connections to people, business systems and devices are being developed progressively.
所有方案都必须配硬件吗？
不是。硬件是可选的接入与执行能力，是否需要取决于具体方案。旧硬件版仍按其要求连接；新方案不能沿用“所有输入都必须经 U盾”的表述。
No. Hardware is an optional connection or execution capability. Legacy hardware editions retain their specific requirements; the newer design must not claim all input requires a USB device.
分身数量不限，是否代表支持账号多开？
不代表。可按角色和任务创建多个分身，当前产品未设置分身创建数量上限；这不等于一台电脑可同时自动操作多个账号。并发执行、账号隔离与多设备调度需另行验证，不能把云电脑或私有部署直接写成已支持多开。
No. There is currently no imposed creation-count limit for role- or task-based counterparts. This does not mean one computer can automatically operate several accounts simultaneously. Concurrency, isolation and multi-device dispatch require separate validation, including in cloud or private environments.
手机端是什么定位？
手机是统一指挥入口的标配设计：查看进度、训练分身、接收提醒、暂停和补话，并连接执行端。互联手机 App 和远程控制尚待开发验收；“标配设计”不表示现已交付。
It is designed as the standard command interface for progress, training, alerts, pause and intervention across execution endpoints. The connected mobile app and remote control still require development and acceptance; standard design does not mean already delivered.
会占用我的工作电脑吗？
当前本机桌面执行需要可用的前台窗口进行键鼠操作，后台读取不等于后台发送。独立电脑或未来云电脑执行可分离工作环境；云端联动仍待接通，不能承诺现在已经完全互不干扰。
Current local desktop execution needs the target window in the foreground for keyboard/mouse actions. Background reading is not background sending. A separate computer or future cloud-PC endpoint can separate environments, but cloud coordination is not yet connected.
使用微信等平台会不会有账号风险？
存在风险，不能承诺零封号。使用范围受平台规则、接口权限和实际行为约束；本产品的命名、硬件或云电脑运行方式都不自动消除这些风险。
Yes. Zero suspension risk cannot be promised. Use is governed by platform rules, interface permissions and actual behavior. Product naming, hardware and cloud-PC operation do not automatically remove these risks.