npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

agenthint

v0.4.1

Published

Detect AI agent runtimes and adapt CLI output.

Readme

agenthint

CI Release npm crates.io PyPI License GitHub Repo stars

Detect AI agent runtimes and adapt CLI output.

agenthint is a small detection spec, CLI, and multi-language library for developer tools that want to know when they are probably being run by an AI agent such as Codex, Claude Code, Cursor, Gemini CLI, Aider, or another automated coding environment.

Use it to choose better defaults for agent-driven runs: structured output, quiet logs, no spinners, no pagers, no interactive prompts, and clearer diagnostics.

Detection is advisory. agenthint is for user experience decisions, not authentication, authorization, sandboxing, or policy enforcement.

Quick Start

Install the CLI:

npm install -g agenthint
# or
cargo install agenthint
# or
python3 -m pip install agenthint

Use its exit code in scripts:

if agenthint >/dev/null; then
  exec my-tool --json --no-progress --no-pager "$@"
else
  exec my-tool "$@"
fi

Prefer the explicit convention when you control the agent or wrapper:

AI_AGENT=codex my-tool
AI_AGENT=claude-code my-tool
AI_AGENT=my-custom-agent my-tool

Why

Humans and agents often need different CLI behavior.

| Humans often prefer | Agents often prefer | | --- | --- | | Colors, spinners, prompts | Stable, parseable output | | Pagers and browser launches | Non-interactive execution | | Decorative progress UI | Line-oriented diagnostics | | Friendly summaries | Explicit sections and exit codes |

agenthint gives tools a shared, explainable way to switch modes without each project inventing its own agent detection logic.

CLI

agenthint             # exit 0 if an agent is likely detected, otherwise 1
agenthint --json      # print the structured detection result
agenthint --explain   # print a short human-readable explanation
agenthint doctor      # print detection details and setup advice
agenthint doctor --json
agenthint init codex  # print the recommended AI_AGENT value

Example JSON:

{
  "isAgent": true,
  "agent": "codex",
  "confidence": 0.92,
  "signals": ["env:CODEX_CI", "env:CODEX_THREAD_ID"]
}

Exit codes:

| Code | Meaning | | --- | --- | | 0 | Agent runtime likely detected | | 1 | Agent runtime not detected | | 2 | Invalid usage or detection error |

Setup-only commands such as agenthint init <agent> exit 0.

Libraries

TypeScript

import { detectAgent } from "agenthint";

const result = detectAgent();

if (result.isAgent) {
  // Prefer structured, quiet, non-interactive output.
}

Rust

use agenthint::detect_agent;

let result = detect_agent();

if result.is_agent {
    // Prefer structured, quiet, non-interactive output.
}

Python

from agenthint import detect_agent

result = detect_agent()

if result.is_agent:
    # Prefer structured, quiet, non-interactive output.
    pass

Install

npm

npm install -g agenthint
agenthint --json

crates.io

cargo install agenthint
agenthint --json

PyPI

python3 -m pip install agenthint
agenthint --json

Native binary

curl -fsSL https://raw.githubusercontent.com/forjd/agenthint/main/install.sh | sh

The install script downloads the latest agenthint-v* GitHub Release asset for your platform and verifies it against SHA256SUMS.

Override the install directory or version:

AGENTHINT_INSTALL_DIR=/usr/local/bin sh install.sh
AGENTHINT_VERSION=agenthint-vX.Y.Z sh install.sh
AGENTHINT_ALLOW_MISSING_CHECKSUM=1 sh install.sh

Detection Model

Every detection result includes:

| Field | Description | | --- | --- | | isAgent | Whether an agent runtime is likely detected | | agent | Known or custom agent name, when available | | confidence | A number from 0 to 1 | | signals | Diagnostic signal names, never secret values |

Detection priority:

  1. AGENTHINT_DISABLE
  2. AGENTHINT_FORCE
  3. Explicit AI_AGENT
  4. Known environment signals
  5. Documented filesystem signals
  6. Low-confidence parent process signals
  7. Low-confidence stdio hints

Known agents include Codex, Claude Code, Cursor, Gemini CLI, Aider, Augment CLI, AMP, OpenCode, OpenClaw, GitHub Copilot, Replit, Devin, Google Antigravity, Pi, Kiro CLI, Windsurf, Cline, Roo Code, Kilo Code, Mistral Vibe, v0, and Cowork.

Custom agents are supported through any non-empty AI_AGENT value.

Docs

Principles

  • Prefer explicit AI_AGENT support over heuristics.
  • Return confidence, not false certainty.
  • Print signal names, not environment variable values.
  • Keep filesystem probes documented and configurable.
  • Keep requested machine-readable output quiet and stable.
  • Treat detection as a hint, never as a security boundary.

Development

mise install
mise exec -- npm run check

Useful scripts:

npm run build
npm run format
npm run lint
npm run test
npm run check
cargo test --workspace

Contributions are welcome. Please keep detection results explainable, avoid printing secret-bearing environment values, and update the docs when adding or changing signals.