Inth CLI
Install and run the Inth CLI
Install a published @inth/cli release with the install script on macOS or Linux, with npm on any supported platform, or build the CLI from its GitHub repository. After installation, run inth login for browser approval and inth whoami to verify API access.
How do I install on macOS or Linux without Node.js?
Run the install script:
The script downloads the native package for your platform from npm and checks it against the registry's sha512 integrity. It runs the new executable once, then copies inth to ~/.local/bin. If that directory is not on your PATH, the script prints the line to add to your shell profile. Run inth update to update.
Set INTH_VERSION to install a specific published release instead of the latest. Set INTH_INSTALL_DIR to install somewhere else:
The script installs only the executable. The AGENTS.md, SKILL.md, and Markdown topics bundled for agents ship with the npm package. To uninstall, delete ~/.local/bin/inth. On Windows, install with npm.
How do I install with npm?
For releases available on npm, install the launcher globally:
npm selects the native package for your platform. Keep optional dependencies enabled, since they contain the executable. If the requested release is unavailable on npm, build from source using the steps below. The repository's releases record published versions.
How do I update the Inth CLI?
Run inth update:
The command installs the latest release the same way the CLI was installed. An install-script installation reruns the install script in the same directory. A global npm, pnpm, bun, or Yarn installation runs that package manager's global install, such as pnpm add -g @inth/cli@latest.
To check for a release without installing it:
inth update prints what to run instead of running it when @inth/cli is a project dependency, when it runs through npx, pnpm dlx, or bunx, and on Windows, which cannot replace a running inth.exe. It does the same when pnpm's global virtual store holds the CLI, because global installations and project dependencies share that location.
When does the CLI announce a new release?
An interactive command checks npm for the latest @inth/cli version at most once a day. The check runs alongside the command. If a newer release exists, the CLI prints this to stderr after the command finishes:
The notice appears at most once a day. The check sends one request to registry.npmjs.org with no account, installation, or command details. It can add up to 1.5 seconds to one command a day when npm responds slowly.
Only global installations in a terminal check. Project dependencies, npx runs, development builds, --json, --non-interactive, CI, and commands whose stdin or stderr is not a terminal skip both the request and the notice. Set INTH_UPDATE_CHECK_DISABLED=1 or NO_UPDATE_NOTIFIER=1 to turn it off. Set INTH_NPM_REGISTRY to use a registry mirror for update checks and the install script.
How do I install from a sandboxed agent terminal?
Run the install outside the sandbox. Cursor and other coding agents can run terminal commands in a sandbox that writes only to the project and temporary directories. The install script writes to ~/.local/bin and npm install -g @inth/cli writes to npm's global directory and cache, so both fail there. npm then reports that the cache folder contains root-owned files and suggests sudo chown. The cache is fine; the sandbox blocked the write. In Cursor, approve running the command outside the sandbox.
Sign-in and API commands need the same approval. They write locks and settings to the state directory, read credentials from the system credential store, and connect to api.inth.com. Adding api.inth.com to Cursor's network allowlist does not help, because the CLI does not use the sandbox's HTTP proxy. Inside Cursor's sandbox, the CLI reports the blocks it recognizes with the sandbox_restricted error code. Other failures keep their usual code. inth --help and inth --version work inside the sandbox.
How do I build and link the CLI from source?
Check out the Inth CLI repository. You need Node.js 24 and the pnpm version declared in the repository's packageManager field. Install Xcode Command Line Tools on macOS, Clang 18 or newer and zlib development headers on Linux (clang and zlib1g-dev on Ubuntu 24.04), or Zig 0.15.2 on Windows. All platforms also need CMake for the native Sentry SDK.
On Windows, select Zig before building in PowerShell:
From the repository root:
pnpm dev:link builds the CLI and links this checkout's inth command into npm's global bin directory. It works on macOS, Linux, and Windows without editing a shell profile. That directory must be on your PATH.
Run inth from any directory:
After edits, run pnpm dev:link again to rebuild. The link uses this checkout's latest build and keeps your current working directory, so project commands and MCP setup work where you run them. Run pnpm dev:unlink to remove the development command. Only one checkout can own the global inth link at a time.
The development link uses Node.js 24 to launch packages/cli/dist/inth, or dist/inth.exe on Windows. Distributed native executables have no Node.js runtime dependency.
login opens your browser for approval, saves the session in the system credential store, and helps you choose an organization. Use inth login --no-browser to open the printed approval URL yourself. Run inth --help for command groups and inth <command> --help for relevant options and examples.
How do I run from a checkout without a global link?
dev rebuilds before running. inth runs the current build. Development commands call https://api.inth.com; writes take effect immediately.
Which platforms and runtimes does the CLI support?
Native builds target Apple silicon Macs running macOS 14 or newer, Linux arm64 and x64 with glibc 2.36 or newer, and Windows x64. Debian 12 and Ubuntu 24.04 meet the Linux requirement. Ubuntu 22.04 and Alpine Linux with musl are not supported by the published binaries. The npm launcher requires Node.js. The native executable itself does not. The install script needs curl or wget, tar, and sha512sum, shasum, or openssl; macOS and most Linux distributions include them.
Linux browser sign-in needs libsecret-1.so.0, a session bus, and an unlocked Secret Service keyring. On a headless machine, use an organization API key through INTH_TOKEN for commands that accept keys. See Authentication.