# @fnet/cli > CLI for Flownet Latest version **1.26.1** (published 2026-07-02) · MIT license · 0 weekly downloads ## Install ```sh npm install @fnet/cli pnpm add @fnet/cli yarn add @fnet/cli bun add @fnet/cli ``` Provides the commands `fbin`, `fnet`, `frun`, `fnode`, `fservice`. ## Health **Score 60/100 (C)** — status: active. Positive: esm support; no vulnerabilities; recently updated; high maintenance score. Warnings: low downloads; no types. ## Facts | | | |---|---| | Version | 1.26.1 | | Published | 2026-07-02 | | First published | 2023-09-28 | | Weekly downloads | 0 | | License | MIT | | TypeScript types | none | | Module format | ESM | | Dependencies | 47 | | Unpacked size | 851.4 KB | | Known vulnerabilities | 0 | | Install scripts | yes | | GitHub stars | 0 | | Maintainers | serdar986, serdark, gboyraz | ## Links - npm: https://www.npmjs.com/package/@fnet/cli - Repository: https://github.com/fnetai/cli - Homepage: https://github.com/fnetai/cli#readme - Issues: https://github.com/fnetai/cli/issues - npm.io page: https://npm.io/package/@fnet/cli ## Dependencies (47) - [ajv](https://npm.io/package/ajv.md) ^8.20.0 - [yaml](https://npm.io/package/yaml.md) ^2.9.0 - [chalk](https://npm.io/package/chalk.md) ^5.6.2 - [dagre](https://npm.io/package/dagre.md) ^0.8.5 - [yargs](https://npm.io/package/yargs.md) ^18.0.0 - [nanoid](https://npm.io/package/nanoid.md) ^5.1.15 - [rollup](https://npm.io/package/rollup.md) ^4.62.2 - [semver](https://npm.io/package/semver.md) ^7.8.5 - [winston](https://npm.io/package/winston.md) ^3.19.0 - [isobject](https://npm.io/package/isobject.md) ^4.0.0 - [nunjucks](https://npm.io/package/nunjucks.md) ^3.2.4 - [prettier](https://npm.io/package/prettier.md) ^3.8.4 - [form-data](https://npm.io/package/form-data.md) ^4.0.6 - [get-value](https://npm.io/package/get-value.md) ^4.1.0 - [set-value](https://npm.io/package/set-value.md) ^4.1.0 - [tree-kill](https://npm.io/package/tree-kill.md) ^1.2.2 - [@fnet/yaml](https://npm.io/package/@fnet/yaml.md) ^0.1.52 - [cli-table3](https://npm.io/package/cli-table3.md) ^0.6.5 - [typescript](https://npm.io/package/typescript.md) ^5.9.3 - [ajv-formats](https://npm.io/package/ajv-formats.md) ^3.0.1 - [bpmn-moddle](https://npm.io/package/bpmn-moddle.md) ^9.0.4 - [object-hash](https://npm.io/package/object-hash.md) ^3.0.0 - [@fnet/config](https://npm.io/package/@fnet/config.md) ^0.2.33 - [@fnet/prompt](https://npm.io/package/@fnet/prompt.md) ^0.2.16 - [lodash.merge](https://npm.io/package/lodash.merge.md) ^4.6.2 - [@fnet/service](https://npm.io/package/@fnet/service.md) ^0.1.9 - [@fnet/shelljs](https://npm.io/package/@fnet/shelljs.md) ^0.2.4 - [@node-red/util](https://npm.io/package/@node-red/util.md) ^4.1.11 - [@fnet/dir-zipper](https://npm.io/package/@fnet/dir-zipper.md) ^0.1.8 - [@fnet/shell-flow](https://npm.io/package/@fnet/shell-flow.md) ^0.4.2 - [lodash.clonedeep](https://npm.io/package/lodash.clonedeep.md) ^4.5.0 - [@fnet/files-to-gcs](https://npm.io/package/@fnet/files-to-gcs.md) ^0.3.12 - [@fnet/up-list-files](https://npm.io/package/@fnet/up-list-files.md) ^0.1.14 - [@fnet/auto-conda-env](https://npm.io/package/@fnet/auto-conda-env.md) ^0.2.4 - [@fnet/npm-list-versions](https://npm.io/package/@fnet/npm-list-versions.md) ^0.1.35 - [@fnet/npm-pick-versions](https://npm.io/package/@fnet/npm-pick-versions.md) ^0.1.14 - [@flownet/lib-atom-api-js](https://npm.io/package/@flownet/lib-atom-api-js.md) ^0.2.3 - [@fnet/object-from-schema](https://npm.io/package/@fnet/object-from-schema.md) ^0.1.25 - [@fnet/rollup-plugin-delete](https://npm.io/package/@fnet/rollup-plugin-delete.md) ^0.1.10 - [@fnet/xcode-cert-inspector](https://npm.io/package/@fnet/xcode-cert-inspector.md) ^0.1.10 - [@flownet/lib-parse-node-url](https://npm.io/package/@flownet/lib-parse-node-url.md) ^0.1.18 - [@fnet/key-value-transformer](https://npm.io/package/@fnet/key-value-transformer.md) ^0.1.4 - [@flownet/lib-is-redis-online](https://npm.io/package/@flownet/lib-is-redis-online.md) ^0.1.15 - [@flownet/lib-create-ios-icons](https://npm.io/package/@flownet/lib-create-ios-icons.md) ^0.2.3 - [@flownet/lib-parse-imports-js](https://npm.io/package/@flownet/lib-parse-imports-js.md) 0.4.6 - [@flownet/lib-render-templates-dir](https://npm.io/package/@flownet/lib-render-templates-dir.md) ^0.1.19 - [@flownet/lib-create-ios-launch-screens](https://npm.io/package/@flownet/lib-create-ios-launch-screens.md) ^0.2.3 ## Recent versions - 1.26.1 (latest) — 2026-07-02 - 1.26.0 — 2026-06-17 - 1.25.1 — 2026-06-09 - 1.25.0 — 2026-06-09 - 1.24.0 — 2026-06-04 - 1.23.0 — 2026-05-21 - 1.22.0 — 2026-05-20 - 1.21.0 — 2026-05-20 - 1.20.0 — 2026-04-20 - 1.19.0 — 2026-04-16 - 1.18.2 — 2026-04-16 - 1.18.1 — 2026-04-16 - 1.18.0 — 2026-04-16 - 1.17.3 — 2026-04-16 - 1.16.0 — 2026-04-16 - … 472 more at https://npm.io/package/@fnet/cli/versions ## README # @fnet/cli: Flownet CLI

Flownet Logo

Give developers primitives. Trust them to compose. Make the tooling excellent.

npm version npm downloads license

--- ## Why Flownet? Most developers spend the majority of their time on things that aren't their actual problem: build configuration, bundling, runtime wiring, deployment pipelines, service setup. The ratio of "infrastructure work" to "actual logic" is often 80/20 in the wrong direction. Flownet exists to flip that ratio. It separates what you write (**Core**) from what surrounds it (**Layers**), then automates the Layers so you can focus on the Core. - **Core**: Your functional, minimal, deterministic logic and its I/O contracts - **Layers**: Dev experience, build pipelines, runtime wiring, delivery/packaging You write the Core. Flownet generates, manages, and updates the Layers automatically. Update all Layer infrastructure across every project by updating the CLI. | Project Type | Core (you write) | Layers (Flownet handles) | | ------------ | ----------------- | ------------------------------- | | CLI | Command logic | Binary + PATH/runtime + publish | | App | UI/flows | Bundling + hosting/CDN + deploy | | Component | API/behavior | ESM/CJS/types + publish | This is the same philosophy that made React successful for UI: provide primitives, trust developers to compose, make the tooling excellent. Flownet applies it to the entire development lifecycle. ## What You Get ```text @fnet/cli (npm package) | |- fnode ---------> Node/Classic Projects (fnode.yml) | Create, build, deploy reusable Nodes | |- fnet ----------> Workflow Projects (fnet.yml) | Create, build, deploy Flows | |- frun ----------> Unified Command Runner | Auto-detect project type, run command groups | Powered by @fnet/shell-flow | |- fbin ----------> Binary Management | Compile JS to native binaries | Install to ~/.fnet/bin/ | '- fservice ------> Service Management Cross-platform system services (systemd, launchd, Windows Services) ``` Five CLI tools that work together to cover the full development lifecycle: create, develop, build, distribute, and run as a service. ## Installation ### Homebrew (recommended, macOS/Linux) ```bash brew tap fnetai/tap brew install fnet ``` Installs all 5 CLI tools (`frun`, `fbin`, `fservice`, `fnode`, `fnet`) as native binaries plus templates. No Node.js or npm required. ### npm ```bash npm install -g @fnet/cli ``` ### bun ```bash bun install -g @fnet/cli ``` For both npm and bun installs, pre-compiled native binaries for all 5 CLI tools are downloaded for your platform on first install. If the download fails, the JavaScript versions work as a fallback. Each installation method is **fully isolated** — binaries and templates live in the package manager's own space (Homebrew cellar, npm/bun global). User data (`fbin`-installed binaries, services, express projects) stays in `~/.fnet/` across all installations. ## Core Concepts ### Nodes & Flows **Nodes** are reusable functional units with explicit input/output schemas. Each Node has a deterministic, pure function at its core with clear I/O contracts. Think of them as the building blocks. **Flows** orchestrate Nodes and sub-Flows into workflows. They define how capabilities connect, transform, and execute - composition and control flow over the primitives that Nodes provide. | | fnode Project | fnet Project | | ----------- | ------------------------------- | --------------------- | | Config file | `fnode.yml` | `fnet.yml` | | Purpose | Reusable Nodes, standalone apps | Workflow orchestration | | CLI | `fnode` | `fnet` | | Runtimes | Node.js, Bun, Python | Node.js, Bun | ### Schema-First & Multi-Runtime Flownet uses schema-first contracts (I/O schemas) to define clear expectations. This enables: - **Multi-runtime portability**: Same Core logic deploys to Node.js, Bun, or Python - **Deterministic behavior**: Clear contracts across different runtimes - **Automatic validation**: Schemas drive type checking and validation ```text my-project/ |- src/ | |- index.js # JavaScript (Node.js / Bun) | '- index.py # Python |- fnode.yml '- .workspace/ # Layers (managed by CLI, not your concern) ``` ### Documentation That Never Lies Flownet automatically generates BPMN 2.0 (Business Process Model and Notation) diagrams from your Flow definitions on every build. Your YAML is the single source of truth - diagrams are derived, never hand-maintained. - **Developers** read YAML (code-like, version controlled) - **Stakeholders** view BPMN (visual, business-friendly) - **Tools** analyze BPMN (process mining, compliance) This solves the eternal problem of documentation going stale. With Flownet, it can't - diagrams regenerate on every `fnet build`. ### AI-Native: MCP Integration Every Flownet project can be exposed as an AI-compatible tool server via the [Model Context Protocol (MCP)](https://modelcontextprotocol.io). Both `fnode` and `fnet` projects support MCP mode with STDIO and HTTP transports: ```bash # Expose as MCP tool for Claude Desktop or any AI assistant fnode cli --cli-mode mcp # Or over HTTP for remote AI integrations fnet cli --cli-mode mcp --mcp-transport http --cli-port 3003 ``` This means any Flownet project - a data processor, a CLI tool, a workflow - can become a tool that AI assistants discover, understand, and invoke. It's not a bolt-on feature; it's a first-class runtime mode alongside CLI, HTTP, WebSocket, and Pipeline modes. ## Quick Start ### Create a Project ```bash # Node.js project (default runtime) fnode create --name my-project # Python project fnode create --name my-project --runtime python # Bun project fnode create --name my-project --runtime bun # Workflow project fnet create --name my-workflow ``` ### Quick Test Projects Rapid prototyping without thinking about names: ```bash fnode express --yes # Creates fnode-1, fnode-2, fnode-3... fnet express --yes # Creates fnet-1, fnet-2, fnet-3... ``` ### Build and Run ```bash frun build # Run 'build' command group fnode cli # Run as CLI frun [--ftag ] # Execute command group with tags frun list # List available command groups ``` ## CLI Tools ### fnode - Node/Classic Projects ```bash fnode create --name my-project # Create a new project fnode build # Build the project fnode cli # Run as CLI fnode cli --cli-mode http # Run as HTTP server fnode compile # Compile to binary fnode install # Install compiled binary ``` **Passthrough commands** execute tools in the project's `.workspace` context: ```bash fnode npm install lodash # npm in workspace fnode node script.js # node in workspace fnode bun run dev # bun in workspace fnode python script.py # python in workspace fnode cdk deploy # AWS CDK in workspace fnode aws s3 ls # AWS CLI in workspace ``` **Runtime modes** - one project, multiple deployment targets: | Mode | Command | Use case | | --------- | -------------------------------- | --------------------------------- | | CLI | `fnode cli` | Terminal executable | | HTTP | `fnode cli --cli-mode http` | REST API server | | WebSocket | `fnode cli --cli-mode websocket` | Real-time bidirectional | | Pipeline | `echo data \| fnode cli` | Unix-style stdin/stdout streaming | | MCP | `fnode cli --cli-mode mcp` | AI-compatible tool server | ### fnet - Workflow Projects ```bash fnet create --name my-workflow # Create a workflow project fnet build # Build (+ auto-generate BPMN) fnet npm install # npm in workspace fnet cdk deploy # AWS CDK in workspace ``` ### frun - Unified Command Runner Auto-detects project type and runs command groups. Powered by [`@fnet/shell-flow`](https://www.npmjs.com/package/@fnet/shell-flow). ```bash frun build # Run 'build' command group frun deploy # Run 'deploy' command group frun dev --ftag local # Run with tags frun list # List available command groups ``` Define command groups in your project YAML: ```yaml commands: build: usage: frun build description: Build the project steps: - npm install - npm run build test: usage: frun test description: Run all tests parallel: - npm run test:unit - npm run test:integration dev: usage: frun dev description: Start dev servers fork: - npm run watch:css - npm run watch:js - npm run dev-server ``` The `commands:` section is `@fnet/shell-flow` input schema in YAML format. This gives you sequential execution, parallel execution, background processes, environment variables, template variables (`{{var}}`), output capture, retry with exponential backoff, timeouts, and a full set of expression builtins (`json::`, `http::`, `file::`, `txt::`, `encode::`, `hash::`, `time::`, `capture::`, `pause::`, and more). ### fbin - Binary Management Compile JavaScript to native binaries and manage installations: ```bash fbin setup # Initialize the bin system fbin path # Add ~/.fnet/bin to PATH fbin compile script.js -o my-tool # Compile JS to binary fbin install ./my-tool --name app # Install a binary fbin list # List installed binaries fbin uninstall app --yes # Remove a binary fbin backup # Backup binaries and shell config fbin restore # Restore from backup ``` Pre-compiled binaries for all platforms are built via GitHub Actions and distributed through GitHub Releases. ### fservice - Service Management Deploy projects as system services across platforms: ```bash fservice manifest create # Create a service definition fservice register -d my-api # Register with OS service manager fservice start my-api # Start service fservice stop my-api # Stop service fservice restart my-api # Restart service fservice status my-api # Check status fservice list # List all services fservice unregister my-api # Remove service ``` **Supported platforms**: macOS (launchd), Linux (systemd), Windows (Windows Services) ## Tag-Based Configuration The `--ftag` parameter enables conditional configuration from a single project file: ```bash frun build --ftag dev --ftag local ``` ```yaml name: my-project database: port: 5432 t::dev::database: url: "mongodb://localhost:27017" t::prod::database: url: "mongodb://production-server:27017" ``` One file, multiple environments. Tags enable environment-specific commands, feature flags, and platform-specific configurations. ## Project Structure ```text my-project/ |- src/ # Core - your code |- fnode.yml # or fnet.yml - project configuration |- .workspace/ # Layers - managed by CLI '- .fnet/ # Local configuration ``` **Global directories**: - `~/.fnet/bin/` - Installed binaries - `~/.fnet/services/` - Service definitions ## Comparison | Aspect | Traditional Workflow Engines | Flownet | | -------------- | ---------------------------- | --------------------------------- | | Syntax | Proprietary DSL | YAML + JavaScript | | Development | Special IDE required | Any IDE (VS Code, etc.) | | Debugging | Limited or proprietary | Standard (Chrome DevTools) | | Testing | Proprietary tools | Standard test frameworks | | Visualization | Manual diagram creation | Auto-generated BPMN | | Runtime | Vendor-specific | Multi-runtime (Node/Bun/Python) | | Learning Curve | Steep (new DSL + tools) | Gentle (YAML + JavaScript) | | Flexibility | Opinionated, limited | Primitives, compose freely | | Ecosystem | Vendor packages | npm ecosystem | | AI Integration | Separate system | Built-in MCP mode | ## License MIT --- _Source: https://npm.io/package/@fnet/cli · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._