不可变版本 / Immutable version 2026-10-25.2. 本副本不加载分析或应用脚本 / No analytics or app scripts.

Laintas CLI 专用条款

适用于终端 Agent、CLI Windows、远程连接和相关扩展。托管模型费用与本地软件许可分别适用。

2026-10-25.2 · 2026-10-25

适用与共同规则

本附件适用于 Laintas CLI 的相应功能,与平台服务条款、隐私政策、数据用途说明及收费与退款政策共同适用。仅在本附件明确的产品事项上补充或优先于总条款;强制性法律及双方有效的个别协商约定优先。以购买或使用时明确提供且依法有效接受的版本为准,网页更新不自动改变已有订单。

直接命令、Agent 和授权模式

直接输入的系统命令可在本机终端执行;自然语言任务可让 Agent 读取上下文、调用模型、编辑文件和执行工具。实际范围取决于模式、工作区、组织策略、角色与批准记录。允许任务内操作不等于允许访问所有目录、上传凭据或无限支出;自动模式和批量批准应核对其范围。可停止任务、撤销连接和更改权限;已提交进程或外部操作需另行确认状态。

上下文、本地记录与网关经验

为执行任务可处理工作区文件片段、规则、提示词、终端状态、历史和工具结果,并将必要内容发送给您选择的后端。会话、计划、记忆与轨迹可保存在本机;网关工作区经验可能另在服务端保存。清空本地会话不会自动清空网关经验,CLI 切换后端时还需核对该后端规则。不要把终端运行理解为数据始终不离开机器。

训练数据选择

当前服务端训练选择只涵盖对应 CLI/CLI Windows 的网关可观察输入和输出,须主动开启;/training status 查看,/training off 停止后续收集。/training local 管理的是独立本地采集,不能把两个开关混为一谈。既有训练数据不会因关闭开关自动删除,个人信息相关请求仍依法处理。开启前应确认有权授权相关代码和内容,不包含雇主、客户或他人不允许提交的资料。

模型费用、组织资金和扩展

软件免费获取或源码可见不表示托管模型、搜索、租机和扩展服务免费。多 Agent 和后台处理可能产生多次调用;资金来源按个人、会员、自带 key 或已选组织席位规则处理。选定席位无法支付时,不应因该失败静默改扣个人余额。插件、Skills 与 MCP 各有权限、来源和许可,审核或签名不保证其全部行为安全。

软件许可与发行物

各发行版本附带的 LICENSE 决定其使用、修改、分发和商业许可。当前公开 CLI 仓库采用 FSL-1.1-MIT:包含竞争性使用限制,并按许可证约定在该版本发布满两年后授予 MIT 许可,不能视为当前无条件 MIT 授权。企业私有扩展、Windows 宿主、第三方组件和模型权重可能另有许可。本文不扩大或缩减具体许可证授予的权利,托管服务条款也不替代代码许可。

工作目录、文件发现和执行环境

启动目录、配置、项目指令、命令参数和已授予工具权限会影响 Agent 能看到和操作的资料。忽略文件、搜索过滤和上下文裁剪用于减少读取或传输,不是所有工具均被隔离的保密边界;敏感目录与凭据应结合操作系统权限、沙箱和独立配置保护。直接执行 shell 命令与把命令作为建议返回不同;请确认实际模式、连接宿主和环境变量。不要把错误工作目录、远程连接或自动批准设置理解为可自动纠正的无风险选项。

非交互任务、重试与停止

批处理或无人值守运行可能无法即时询问,授权不足、预算不足或连接失败时应按配置拒绝、停止或等待,不应据此自行扩大权限。一次任务可能包含多个模型轮次、搜索和工具调用,成本不以终端最后显示的一行文字计算。您主动继续、重跑或开并行任务可能产生独立用量;系统内部重试和异常扣款应可核查。终止 CLI 不必然关闭其已启动的外部程序、远程服务或 Compute 租机,应分别检查;已经有效完成的处理按对应资金来源结算。

扩展、更新与凭据安全

Skills、MCP、脚本和包安装可能访问本机、网络、密钥或供应商账户,其来源、许可和权限应分别核对。扩展文档不能替代您对高影响操作的授权,项目文件也不能授权导出无关秘密。自动更新或手动升级可能调整兼容性和默认设置,重要环境应先核对版本说明和配置。供应商 key、组织凭据、本机记录和云端托管删除方式不同;卸载 CLI 不自动撤销供应商 key 或删除云端经验、训练样本和账务记录。

Laintas CLI product terms

For the terminal agent, CLI Windows, remote connections and extensions. Hosted model charges and local software licences apply separately.

2026-10-25.2 · 2026-10-25

Scope and common rules

This annex applies to the relevant Laintas CLI 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.

Direct commands, agents and authority modes

Direct system commands may execute in your terminal; natural-language tasks can read context, call models, edit files and use tools. Scope depends on mode, workspace, organisation policy, role and approvals. Task authority does not confer access to every directory, credential disclosure or unlimited spending. Review automatic and batch approvals. Stop tasks, revoke connections or change permissions; separately confirm processes or external operations already submitted.

Context, local records and gateway experience

Task context can include workspace excerpts, rules, prompts, terminal state, history and tool results, with necessary material sent to the selected backend. Sessions, plans, memories and traces may be local, while gateway workspace experience may be server-side. Clearing local sessions does not clear gateway experience. Review the policy of a replacement backend. Running in a terminal does not imply data never leaves the machine.

Training-data choice

Current server-side training choice covers gateway-observed inputs and outputs for the corresponding CLI/CLI Windows and requires opt-in. Use /training status to inspect and /training off to stop future capture. /training local controls separate local capture. Existing training data is not automatically deleted by switching off; lawful personal-information requests remain available. Ensure authority over code and content, including employer, client and third-party material, before opting in.

Model charges, organisation funding and extensions

Free acquisition or source availability does not make hosted models, search, rentals or extensions free. Multiple agents and background work can create multiple calls. Funding follows personal balance, membership, own-key or chosen organisation-seat rules. Failure of a selected seat must not silently charge personal balance. Plugins, Skills and MCP have their own permissions, source and licences; review or signatures do not guarantee all behaviour.

Software licences and distributions

The LICENSE supplied with each release governs use, modification, distribution and commercial rights. The current public CLI repository uses FSL-1.1-MIT, with competing-use restrictions and an MIT grant after the specified version has been available for two years; it is not presently an unconditional MIT grant. Enterprise extensions, Windows hosts, third-party components and model weights may have different licences. These terms neither expand nor reduce the applicable licence and hosted terms do not replace code licensing.

Working directory, file discovery and execution context

Launch directory, configuration, project instructions, arguments and tool authority affect accessible material and operations. Ignore files, search filters and context trimming reduce reading or transmission but are not universal confidentiality boundaries across tools. Protect sensitive directories and credentials with OS permissions, sandboxing and separate configuration. Direct shell execution differs from returning a proposed command. Check mode, host and environment; a wrong directory, remote connection or automatic approval is not a risk-free setting that will always be corrected.

Unattended work, retries and stopping

Batch or unattended work may be unable to ask immediately. Missing authority, budget or connectivity should cause configured refusal, stopping or waiting, not expanded permissions. A task can contain many model turns, searches and tools; cost is not measured by the last terminal line. Continuing, rerunning or parallel work can create separate usage, while internal retries and incorrect debits remain reviewable. Ending the CLI does not necessarily stop spawned programs, remote services or rentals; check separately. Valid completed work settles against its funding source.

Extensions, updates and credential security

Skills, MCP, scripts and package installation can access local systems, networks, keys or supplier accounts; check source, licence and permissions separately. Extension instructions do not replace authority for significant actions, nor can project files authorise unrelated secret exports. Updates can change compatibility and defaults; review versions and settings for important environments. Supplier keys, organisation credentials, local records and hosted copies have distinct deletion paths. Uninstalling does not revoke provider keys or delete gateway experience, training samples or financial records.