FydeOS Management Cloud CLI

fyde is the command-line client for FydeOS Management Cloud (Admin Console). Inspect resources, preview configuration changes and apply plans under your delegated permissions. Codex and Claude can use the same connection through MCP.

This is a beta release. Use Node.js 20 or later.

Install

One command installs fyde, signs you in and connects Claude Code and Codex. Copy it from your Admin Console (MCP access), or use your environment's endpoint:

npx -y @fydeos/cli@latest install --endpoint https://policy.fydeos.io/mcp

It asks before installing the global fyde command (--yes skips the question, --skip-global keeps it off; the temporary copy that npx runs does not count as installed), opens the console to approve the sign-in (check the one-time code), installs the bundled Skills and registers a fydeos MCP server with Claude Code and Codex when they are installed, keeping any existing entry. It requests write access by default; use --read-only for read access. For Codex, including the Codex built into the ChatGPT desktop app, it appends a [mcp_servers.fydeos] table to ~/.codex/config.toml ($CODEX_HOME/config.toml if set) after backing the file up; existing settings are not changed. When it finishes it lists the next steps: run fyde context (or npx -y @fydeos/cli@latest context without the global command) to confirm the sign-in and granted access, restart the AI clients it configured, and how to connect any it could not.

fyde is a one-shot command that your AI agent runs for you; running it without arguments shows how to get started and the command list.

To install manually instead:

npm install --global @fydeos/cli@latest
fyde --version

The package contains binaries for macOS arm64/amd64, Linux arm64/amd64 and Windows amd64. It selects the matching binary locally and checks its SHA-256. Installation requires access to npm; it does not contact our internal GitLab server. The complete package is about 20 MB compressed.

Choose an environment and sign in

Choose the production environment where your enterprise is registered. Availability depends on the deployed backend version. The endpoint decides the environment; npm's next channel selects the CLI beta version.

fyde auth login --endpoint https://policy.fydeos.io/mcp
fyde auth status
fyde context

Login opens the matching Admin Console authorization page. Review the one-time code, enterprise, organizational scope and categories before approving. Write access is requested by default (the approving administrator can narrow it). Add --read-only to request read-only access, or --no-browser to open the displayed link manually. Login makes it the current login: later commands use it without any extra flag. Each login is saved under a name taken from its Admin Console host (for example admin.fydeos.io); logging in again to the same endpoint reuses it, so you never pick or type a name. --profile (or FYDE_PROFILE) is only needed to keep two logins for the same endpoint, such as two enterprises; logins saved by older releases (for example prod-io) keep working. The Admin Console MCP access page shows the exact command for its own environment. auth logout removes the credential and the saved login.

Profiles live in ~/.config/fyde/config.toml and contain endpoints, not tokens. Credentials stay in the OS keyring and are bound to the exact endpoint. In CI, inject FYDE_ENDPOINT and FYDE_TOKEN together through secret settings; this pair overrides saved profiles and is not persisted. Do not put passwords or tokens into command arguments or shared configuration.

Inspect and change settings

Read live schemas before preparing changes. Replace the example organizational-unit ID with one you are authorized to manage:

fyde search guest --page-all
fyde schema device.guest_mode
fyde policy get device.guest_mode --ou 12
# Preview only; requires a write credential:
fyde policy set device.guest_mode --ou 12 --set guest_mode_enabled=false
# Review and apply the returned plan:
fyde plan show PLAN_ID
fyde plan apply PLAN_ID --wait
fyde op get OPERATION_ID

Commands also cover applications and Kiosk, networks and certificates, FydeSign, devices, directory and enterprise settings. Run fyde --help, then a command group's --help, for usage. Commands and writable fields depend on the server's live schemas, credential scope, administrator permissions and applicable License.

Writes preview by default. Apply explicitly after reviewing the plan. If Apply times out, inspect the original operation and retry the same plan and idempotency key; do not create a replacement plan for an uncertain write. A saved setting or successful notification does not prove that a physical device has applied it.

Connect Codex or Claude

fyde mcp config --client codex
fyde mcp config --client claude
fyde skills install --client all

Add the appropriate printed snippet to your AI client's MCP configuration. It starts fyde mcp serve with the chosen profile and includes no token. Install fyde globally first so the AI client can find the command. Skill installation preserves existing files unless you explicitly use --force. MCP clients use the same delegated permissions and plan workflow.

Install with an AI agent

In the Admin Console, open MCP access → Setup guide → Let an AI agent install it, and paste the instructions into Claude Code, Codex or a similar agent running on your computer. They contain the exact endpoint and profile for that environment. The agent installs @fydeos/cli@latest and starts the login; you still check the one-time code and approve in the browser yourself. The agent never handles a token and previews changes before applying them. The full agent guide ships with this package as AGENT_INSTALL.md and is available at https://unpkg.com/@fydeos/cli@latest/AGENT_INSTALL.md.

Revoke access

fyde auth logout --revoke

This revokes the connected credential and removes its local keyring entry. Environment credentials must also be removed from the process or CI secret settings. Administrators can manage and revoke credentials in the matching Admin Console.

License

BSD 3-Clause License. Copyright (c) 2026, Fyde Innovations Limited. See the LICENSE file in this package; licenses of the bundled third-party components are in THIRD_PARTY_NOTICES. Use of FydeOS Management Cloud itself is subject to the FydeOS Terms of Service.