Products
OneMinute CLI
The OneMinute CLI connects an existing application to OML from the terminal. It discovers the apps in your repository, configures the ones you select, and records what it changed so future runs can pick up from there.
For the install command and suggested prompt answers, see the Quick Start guide.
Repository discovery
Running npx oneminute init at the project root starts discovery. The CLI inspects workspace packages, dependencies, scripts, and application entry points to identify Next.js, Express, NestJS, and React apps. This distinction matters in a monorepo where a shared library and a running service can depend on the same framework.
In an interactive terminal, the CLI lists candidates and lets you select which apps to monitor. The --no-interactive flag stops after discovery. With --json, discovery prints a machine-readable result.
Project and account
The project name groups the selected applications in OneMinute Logs. The CLI suggests the name already recorded in oml.json, then falls back to the root package name or directory name. For a React frontend, setup also identifies the Express or NestJS service that will forward browser events.
The CLI reuses the developer session shared with Pilot or opens browser sign-in. It checks the selected applications for an existing API key and can reuse a valid saved key. When a new key is needed, it creates one through the authenticated account.
SDK installation
Each selected app gets the SDK for its framework. The CLI checks installed versions before invoking the package manager and verifies installation afterward. A Next.js app or a backend selected for browser forwarding also needs the browser SDK.
Installation happens per application. If one package fails verification, the CLI reports the affected app and stops before configuring the applications. A later run checks the packages already installed.
Framework configuration
The CLI inspects the source layout before applying framework-specific edits. For Express and NestJS, setup connects request monitoring to the backend. For supported Next.js layouts, it configures server logging and browser monitoring. If a file needs manual attention, the terminal output identifies it.
For a separate React frontend, events go through the selected backend. The development proxy uses the backend origin supplied during setup. The ingestion key belongs in the server environment and stays out of the browser bundle.
Manifest and repeat runs
The root oml.json records the project name and each application’s setup result. Pilot and OML MCP can read that context later. Credentials are kept separately from this manifest.
Configuration can finish for one app while another still needs attention. The CLI records partial configuration and reports the failure. After the reported issue is fixed, init can run again against the existing dependencies, source files, and manifest.
Optional integrations
After configuration succeeds, the CLI looks for a compatible Next.js App Router host for an embedded dashboard. It proposes an available route and lets the developer accept it, choose another location, or skip the dashboard.
MCP registration is a separate choice. When enabled, the CLI checks for installed Codex and Claude Code clients and registers the local OML MCP server with the project root. Existing registrations for that project are preserved.