netko CLI

Public distribution channel for the netko CLI — install Netko's AI agents, skills, and tools into any agent runtime.

Install

# macOS / Linux
curl -fsSL https://github.com/netkosolution/netko-cli/releases/latest/download/install.sh | sh

# Windows (PowerShell)
irm https://github.com/netkosolution/netko-cli/releases/latest/download/install.ps1 | iex

Requires Node 20+. The installer downloads a single self-contained binary to ~/.netko/bin/netko, verifies its checksum, and adds it to your PATH. Update later with netko upgrade.

What's here

This repo hosts only the CLI release assets — the netko bundle, its checksum (netko.sha256), a version marker (netko.version), and the install/uninstall scripts. They are published automatically by CI from the private source monorepo; this repo takes no pull requests and no manual edits. The catalog of agents/skills is served separately and fetched with a GitHub token by netko install.

Releasing (maintainers)

Releases are cut from the private source monorepo, not here. CI bundles the CLI, then publishes the assets above to a release on this public repo (so curl | sh needs no token), followed by the private catalog release.

One-time setup (in the source monorepo — no secrets are stored in this repo):

1. Fine-grained PAT scoped to this repo only, permission Contents: Read and write → store as the monorepo secret NETKO_CLI_REPO_TOKEN.
2. A cli-release deployment environment in the monorepo (the publish job runs there, isolating the token from the build/test job).
3. This repo's main is branch-protected; official install URLs point at immutable release tags, never main.

Cut a release (in the source monorepo):

git tag vX.Y.Z && git push origin vX.Y.Z

CI publishes the public CLI first, then the private catalog — so an updated catalog never goes live ahead of a CLI that can read it. If NETKO_CLI_REPO_TOKEN is missing, the publish job fails loudly rather than shipping a half-complete release.