01
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.
02
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.
03
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.
04
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.
05
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.
06
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.
07
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.
08
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.
09
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.