不可变版本 / Immutable version 2026-10-25.2. 本副本不加载分析或应用脚本 / No analytics or app scripts.
适用于浏览器工作区、Windows 桌面工作台、Helpwo Kernel 和连接的远程工作环境。
2026-10-25.2 · 2026-10-25
本附件适用于 Helpwo 的相应功能，与平台服务条款、隐私政策、数据用途说明及收费与退款政策共同适用。仅在本附件明确的产品事项上补充或优先于总条款；强制性法律及双方有效的个别协商约定优先。以购买或使用时明确提供且依法有效接受的版本为准，网页更新不自动改变已有订单。
浏览器工作区的本地数据库、本机桌面工作区、通过 Kernel 或 CLI 连接的机器，以及用户选择的云存储是不同位置。浏览器默认本地保存不代表 AI、搜索、远程工具和同步均在本地处理。文件、命令输出、上下文或运行画面可能按启用功能传输给网关、远程同伴、模型和您授权的接单方。点对点传输可能因网络需要中继；中继不是端到端所有组件均无法读取内容的保证。
扩展和外部连接可能包含第三方代码、工具及独立处理者，安装和启用前应核对来源、权限及许可。审核、签名或哈希验证只说明其对应核验结果，不保证业务行为安全或符合您的用途。第三方收费另由其约定，不应将某个扩展获得的权限自动理解为可授权所有扩展。卸载扩展、移除连接与撤销第三方凭据可能需要分别操作。
自动协作可能同时发起多次模型与工具调用，各自计量并受授权约束。通过 Issues 招募他人时，选定的上下文和工具能力会向被选接单方开放，适用 Issues 的保密、成果、验收和费用规则。开放的工作区内容应经过筛选；接单方不能仅凭获选就获得无限权限，仍受您选择的范围、禁止路径和审批约束。
保存到 GitHub 或 Laintas 存储会产生独立云端副本；工作区经验可能在网关保存并用于同一账户的工作延续，和模型训练不同。普通 Helpwo 调用不会因为用户开启 CLI 训练而自动加入该训练授权。请按数据用途说明管理经验和云内容。超额或权益到期可限制新增写入；停止使用或卸载不自动删除本机、云端和第三方的全部副本，也不取消会员续费。
请按当次连接核对可读路径、可写范围、终端、网络和外部账户。一次批准某个命令、某个目录或本次任务，不能自动变成对所有机器和未来任务的永久授权。宽权限或自动执行可减少逐步确认，也会使已授权范围内的操作更快发生；用户与组织应按需要选择限制。撤销权限、断开会话或停止 Agent 通常只影响后续操作，已经运行的程序、写入和外部发送可能需要另行停止或恢复。平台应按实际能力执行权限检查，不能只用提示词承诺限制。
网页、README、依赖、图片文字、外部消息和工具结果可能夹带试图改变任务、索取凭据或扩大权限的指令。将其交给 Agent 分析不表示您同意执行这些指令。特别是上传日志、粘贴命令、安装依赖或打开外部链接前，应确认目标和必要范围；专门的凭据配置与普通上下文不能混用。接单人和插件不得利用内容中的指令绕开宿主审批、组织策略或明确拒绝。发现异常时可停止当前任务、撤销连接并保留必要操作证据。
您须有权接入所选机器及其项目，不能将连接凭据提供给无权限人员。Kernel、桌面宿主和远程终端可能执行实际系统操作，工作目录、分支、文件权限及联网条件会影响结果。结束聊天或关闭工作区不保证所有任务进程、远程端口、租用实例和同步均已关闭；请分别检查运行状态及计费来源。涉及生产数据、迁移和不可逆修改前，应有与风险相称的备份或恢复安排；这些用户措施不免除 Laintas 自身应承担的权限、安全和交付责任。
多 Agent、远程同伴和人工接单可接触任务中实际提供的上下文，所用模型和连接可能不同。请选择确有必要的文件片段与工具结果，区分同账户自动化和独立第三方接单人。将某人选为接单方前，应明确目标、权限、预算和成果用途；保密任务不要通过公开普通问题传递秘密。组织管理员的可见范围及审核功能取决于实际部署，不承诺所有协作均有完整录像、逐步撤回或法律保密特权。
For browser workspaces, the Windows desktop workbench, Helpwo Kernel and connected remote environments.
2026-10-25.2 · 2026-10-25
This annex applies to the relevant Helpwo functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.
Browser databases, desktop workspaces, machines connected by Kernel or CLI and selected cloud storage are different locations. Default local browser storage does not make AI, search, remote tools or sync local. Files, command output, context or runtime views may be transmitted to the gateway, peers, models and authorised contractors. Peer connections may require relaying; relay architecture is not a guarantee that every component is unable to read content.
Extensions and connections may contain third-party code, tools and independent processors. Review source, permissions and licences before enabling them. Review, signatures and hashes establish their particular checks, not a guarantee of safe behaviour or suitability. Third-party charges follow their agreements. Permission for one extension does not authorise every extension. Uninstalling, disconnecting and revoking external credentials may require separate actions.
Collaboration may start concurrent model and tool calls, each metered and subject to authority. Hiring through Issues exposes selected context and tool capabilities to the chosen contractor and invokes the Issues confidentiality, deliverable, acceptance and fee rules. Select the shared material carefully. Selection does not confer unlimited access; scope, prohibited paths and approvals still apply.
GitHub or Laintas Storage creates separate cloud copies. Workspace experience may be held by the gateway for continuity within the account and is distinct from training. A CLI training opt-in does not automatically opt Helpwo calls in. Manage experience and cloud content as described in the Data Use Notice. Over-capacity or expired access may restrict new writes. Stopping or uninstalling neither deletes every local, cloud or third-party copy nor cancels membership renewal.
For each connection check readable paths, writes, terminal, network and external accounts. Approving a command, directory or task does not become permanent authority over every machine and future task. Broad or automatic modes reduce prompts and accelerate permitted operations; users and organisations should choose appropriate limits. Revocation, disconnection and agent stop ordinarily affect future actions; running programs, writes and external sends may need separate termination or recovery. Actual permission checks, rather than prompt promises alone, must enforce supported restrictions.
Pages, READMEs, dependencies, image text, external messages and tool results can contain instructions seeking to redirect work, obtain secrets or enlarge authority. Asking an agent to analyse them does not approve their execution. Check targets and scope before uploading logs, pasting commands, installing dependencies or opening links; dedicated credential settings are distinct from ordinary context. Contractors and plugins must not use embedded instructions to bypass host approval, organisation policy or explicit refusals. Stop work, revoke connections and preserve necessary evidence when anomalies occur.
You must be entitled to connect the machine and project and must not disclose connection credentials to unauthorised people. Kernels, desktop hosts and terminals can perform real system operations affected by directory, branch, permissions and network state. Ending chat or closing a workspace does not guarantee every process, port, rental or sync has stopped. Check their state and funding separately. Production data, migrations and irreversible changes need proportionate backup or recovery arrangements, without waiving Laintas’s own permission, security and delivery duties.
Multiple agents, remote peers and human contractors can receive the context actually supplied, possibly through different models and connections. Share necessary excerpts and tool results, distinguishing same-account automation from independent contractors. Before selection, define goals, authority, budget and deliverable use. Do not send confidential work through ordinary public questions. Administrator visibility and review depend on deployment; complete recordings, stepwise undo and legal privilege are not promised for all collaboration.