New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@adlc/cli

Package Overview
Dependencies
Maintainers
1
Versions
16
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@adlc/cli

Umbrella dispatcher for the @adlc suite - one install, one `adlc <tool>` command surface.

latest
Source
npmnpm
Version
1.13.0
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

@adlc/cli

The umbrella dispatcher for the ADLC suite. It provides one stable command surface for Codex skills, hooks, CI, and humans:

adlc <tool> [args...]
adlc run <phase> [args...]
adlc accept [args...]
adlc mcp-server

The dispatcher is a router. It adds no behavior to a tool run: argv is forwarded verbatim and the child exit code is propagated unchanged.

Why this exists

ADLC packages publish independently, but an agent harness needs a single stable prefix. A skill or hook that shells out to twenty different binaries is brittle, slower to document, and easier to route around. @adlc/cli installs the suite and makes every gate reachable through adlc <tool>.

Resolution model

For the workspace tools, the dispatcher resolves package-local binaries from its own @adlc/* dependencies. It does not search the user's PATH for workspace tool names, so stale global binaries cannot silently satisfy a gate.

Exception — review (npx passthrough): adlc review is not a package-local @adlc/* tool; it is an npx passthrough to the external adversarial-review@^2.6.0 package (npx adversarial-review@^2.6.0). Its resolution is not package-local (the npx runner and the resolved adversarial-review package can come from the repository's node_modules/.bin or the npm cache/registry).

Usage

adlc --help
adlc --version
adlc spec-lint spec.md --json
adlc rails-guard --ticket T1 --record --json
adlc review --base origin/main
adlc run p5 --ticket T1 --dir .adlc --json
adlc accept --ticket T1 --packet .adlc/packet.json --dir .adlc --json
adlc mcp-server

Exit codes

Exit codes mirror the underlying tool:

  • 0: gate passes or command succeeds.
  • 1: operational error.
  • 2: gate fails.

Dispatcher-level failures, such as an unknown tool or missing package, exit 1.

ADLC phase

Cross-cutting. This is the delivery and invocation layer for the ADLC Codex integration.

MCP server (adlc mcp-server)

adlc mcp-server runs a stdio JSON-RPC server exposing adlc_gate (read-only/prompt-only gate invocations) and adlc_prosecute (P5 evidence recording).

Operator-only environment seam (ADLC_CLI_BIN, #592): ADLC_CLI_BIN overrides the adlc.mjs script path the MCP server executes under process.execPath. When set, it must be an absolute path to an existing regular file (relative paths, missing paths, and directories are rejected with JSON-RPC -32602). Because any process that can set ADLC_CLI_BIN in the MCP server's environment chooses the script executed for every tool call, treat ADLC_CLI_BIN as a trusted host/operator seam and never populate it from untrusted repository configuration.

Keywords

adlc

FAQs

Package last updated on 06 Nov 2026

Related posts