fnOS
Use
to manage devices. Installation and upgrades are explicit operations; check the actual version and command help before executing anything.
<!-- standalone:start -->
Standalone Skill Launcher
Locate
(macOS/Linux) or
(Windows) from the currently loaded Skill directory, using an absolute path. Replace
in this Skill's examples with that path, preserving every argument and its quoting. First run
and the relevant
.
On first execution, the required fixed-version CLI for the local machine is downloaded automatically; the prompt is written to stderr, and the current user's cache is reused after a successful download. Standalone execution does not require Node/npm or a global CLI. macOS/Linux require system curl, gzip, SHA-256 utilities (sha256sum or shasum), and common shell utilities. If the download fails, the cache is corrupted, or the mirror configuration needs adjustment, read the First-Run Guide, follow the recovery steps, and retry the original command. Updating the Skill is an explicit operation; existing entry points are not upgraded automatically.
Windows can invoke
in PowerShell 5.1 or 7; the
entry point uses system Windows PowerShell. Pass arguments according to the current shell rules; single quotes are recommended for JSON parameters in PowerShell. Windows uses system .NET for downloading and extraction and does not require Unix utilities. If PowerShell is missing or the execution policy prevents startup, resolve the local environment first, then retry the original entry point.
<!-- standalone:end -->
Authorization and Connection
For login, profiles, connection failures, and authorization recovery, first read the Connection Entry and OAuth Guide. See Common Conventions for field conventions and the Index for module usage.
- The Agent executes
login --authorize-only --agent-name '<agent name>'
{local-machine-name}-{agent-name}
- The user signs in and authorizes access in the browser and proactively sends the one-time code back. The user does not need to run a terminal.
- The Agent executes using the same execution host, system user, configuration environment, profile, and connection parameters. Only report a successful connection after confirming that the token has been saved and performing a read-only verification.
bash
fnos-cli --profile home --host <host> --port <port> login --authorize-only --agent-name '<agent>'
fnos-cli --profile home --host <port> login --code '<code>'
fnos-cli --profile home system info
The user handles their password, 2FA, and browser confirmation. Only accept a code that the user proactively sends; do not repeat, separately persist, or forward it. The code may remain in chat, tool calls, and process arguments, so no guarantee can be made that it will not be retained. The token and PKCE verifier remain in CLI-controlled storage and are not output to chat.
Usage Rules
- The two products have independent commands, configuration, profiles, and login states. The new version requires reauthorization; it neither reads nor migrates old login data and does not automatically delete old credentials.
- Use only the current product's configuration variables. Without explicit connection parameters, resolve only the target for the current product and profile. If no saved record exists, use .
- File write operations default to explicit paths. For high-risk operations, verify the user's intent and the command's requirement; do not make device acceptance testing perform write operations by default.
- is exempt from only for built-in, audited, read-only endpoints. An unknown endpoint name does not prove that it is read-only.
- The CLI and Skill come from the same package version. After the initial installation, an upgrade, or a change to public documentation, check the actual and relevant ; do not assume that the latest version has been rolled out.
Command and Task Overview
- Connection and Authorization: Use for login, selecting a connection target or profile, troubleshooting login state and connection issues, and applying general safety rules.
- Files: Use to list or search for files, upload local files, inspect shared directories and ACLs, or determine the semantics of the current user's directories and NAS paths.
- Photos: Use to browse album scan directories, search for photos, view details, and obtain thumbnail or full-resolution preview URLs.
- App Center: Use to manage installed apps, install from the App Center, handle FPK packages and updates, and manage app launch entries and lifecycle operations.
- Docker: Use to view and manage Docker images, containers, Compose projects, and long-running lifecycle operations.
- Downloads: Use to list, search for, create, and control download tasks, and inspect task files, statistics, and status changes.
- Baidu Netdisk: Use to check Baidu Netdisk authorization and capacity, manage cloud files and shared saves, and configure NAS transfers and scheduled synchronization.
- Logs: Use to browse and filter logs, list log modules, clear or export records, configure archiving, and copy or cancel diagnostic logs.
- Monitoring: Use to view runtime metrics such as CPU, memory, networking, disks, processes, services, battery, fans, GPU/NPU, and buzzer alerts.
- Networking: Use to manage network service toggles, including enabling or disabling SSH, and confirm authorization requirements for write operations.
- Storage: Use to view storage pools, disks, and SMART data, or perform high-risk storage write operations such as mounting, expansion, disk replacement, and formatting.
- System and Power: Use to view static system identifiers, model, version, volumes, hardware, and power plans, or to reboot or shut down the device.
- Users and Permissions: Use to view users, groups, signed-in devices, and current permissions, manage users, or select the correct authorized profile.