🚀 @agnox/agnox-cli

The Future of Testing is Agnostic

The bridge between your local automation suites and a high-performance, AI-driven execution engine.

⚡ Quick Start

Ship your test automation repository to the Agnox platform in seconds—no configuration required.

npx @agnox/agnox-cli@latest init

No installation required. Always runs the latest cutting-edge version.

✨ The "Agnox" Vision

Agnox isn't just a CLI; it's a seamless conduit that transforms raw test projects into deployed, platform-ready artifacts. By generating intelligent, platform-agnostic Docker environments, it feeds directly into the Agnox platform's AI-powered root cause analysis via Gemini integration—turning test execution into actionable, futuristic insights.

🪄 The "Magic" (How it works)

graph LR
    A[💻 Local Code] -->|npx init| B(🚀 Agnox CLI)
    B -->|Buildx & Push| C[(🐳 Docker Hub)]
    C -->|Pull Image| D[🌌 Agnox Dashboard]
    D -.->|Gemini AI Analysis| A
    
    classDef default fill:#1e1e24,stroke:#8a2be2,stroke-width:2px,color:#fff;
    classDef cli fill:#4b0082,stroke:#ba55d3,stroke-width:3px,color:#fff;
    class B cli;

🌟 Key Features

🧠 Smart Framework Detection

Automatically detects frameworks (Playwright, Pytest) and reads your package.json to extract exact versions. Zero-config environments without mismatched browser binaries. Playwright versions are dynamically pinned to mcr.microsoft.com/playwright:v{version}-jammy to guarantee flawless execution.

🐍 Advanced Python/Pytest Analysis

For Pytest projects, the CLI automatically detects allure-pytest configurations, extracts required browser binaries from a browsers.json or requirements file, and enforces platform constraints (linux/amd64 vs linux/arm64) directly tied to your python image architecture.

🏗️ Modern Architecture

Built for the future. Effortlessly supports multi-platform buildx execution (linux/amd64, linux/arm64), ensuring universal compatibility across any Agnox worker node anywhere in the world.

🤖 AI-Ready Integration

Test runs are captured, formatted, and shipped straight to the Agnox ecosystem where Gemini-powered, AI-driven root cause analysis turns failures into immediate, actionable solutions.

🎨 The Visual CLI Experience

We use stunning @clack/prompts to guide you through the process frictionlessly:

│
◇  Welcome to Agnox CLI v2.0.12
│
◇  Please enter your Agnox Identity Token (found in your Dashboard settings):
│  ■■■■■■■■■■■■■■■■■■■■■
│
◇  Which testing framework does this project use?
│  ● Playwright
│  ○ Pytest
│
◇  Detected Playwright version: 1.41.0. Proceeding...
│
◇  Do you want Agnox to build and push the Docker image automatically?
│  ● Yes, handle everything
│  ○ No, just generate files
│
◇  Successfully pushed to Docker Hub!
│
└  Ready. Your identity is linked and the image is ready for the Agnox Dashboard!

🛤️ Workflows: Manual vs. Automatic

We support both rapid deployment and complete customization.

🛣️ The "Easy Path" (Build & Push via CLI)

Let Agnox handle the heavy lifting. The CLI will:

1. Generate your Dockerfile, entrypoint.sh, and .dockerignore.
2. Interactively authenticate via docker login.
3. Read the project name dynamically from package.json.
4. Trigger a multi-platform compilation (linux/amd64 + linux/arm64) via Docker Buildx.
5. Push your pristine image directly to Docker Hub.

🛠️ The "Custom Path" (Manual Build)

Need custom build steps? Just choose to generate the integration files without an automated push:

1. Review and modify the generated Dockerfile and entrypoint.sh.
2. Build the image locally (docker build . -t your-org/your-repo:tag).
3. Push to your registry of choice.

(Note: Never add ENTRYPOINT or CMD to your Dockerfile—the Agnox Worker injects this at runtime)

⚙️ Development & Usage

Prerequisites

• Node.js 18+ — Required to execute the CLI.
• Docker Desktop — Must be running for the automated build & push features.

Usage

# Run the full init + deploy flow (pushes to Docker Hub by default)
npx @agnox/agnox-cli@latest init

# Update and push your Docker image without generating scaffolding files
npx @agnox/agnox-cli@latest push

# Push your Docker image completely non-interactively (ideal for CI/CD)
npx @agnox/agnox-cli@latest push -i <username>/<project>:latest

# Push to a private container registry (AWS ECR, Google GAR, GHCR, etc.)
npx @agnox/agnox-cli@latest init --registry <registry-url>
npx @agnox/agnox-cli@latest init -r <registry-url>

# Check installed version
npx @agnox/agnox-cli@latest --version

| Flag | Alias | Description | |------|-------|-------------| | --registry <url> | -r | Target a private container registry instead of Docker Hub. |

Local Development

npm install
npm run build
node dist/index.js init

🤖 CI/CD Integration (GitHub Actions)

You can easily use agnox push inside your CI/CD pipelines to automatically build and push your test automation changes to Docker Hub without manual prompts.

name: Deploy Tests to Agnox

on:
  push:
    branches:
      - main

jobs:
  build-and-push:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v4

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3
        
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Login to Docker Hub
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

      - name: Build and Push Tests
        run: npx @agnox/agnox-cli@latest push -i my-docker-org/my-tests:latest

🏢 Enterprise: Private Registries

By default, the CLI authenticates against Docker Hub and pushes your test image there. Enterprise teams can redirect this to any private registry — AWS ECR, Google Artifact Registry, GitHub Container Registry, or a self-hosted registry — by passing the --registry flag:

npx @agnox/agnox-cli@latest init --registry 123456789.dkr.ecr.us-east-1.amazonaws.com/my-org

What happens under the hood:

1. Interactive credential prompt — the CLI will ask for the registry username and password (or token) and run docker login against the provided host automatically.
2. Correct image tagging — the image tag is built as <registry-url>/<project-name>:<timestamp>, ensuring it is push-ready for your registry without any manual renaming.
3. Same multi-platform build — the linux/amd64 + linux/arm64 buildx flow runs identically; only the destination changes.

Tip: For token-based registries (e.g. ECR via aws ecr get-login-password), pipe the token in when prompted for the password.

📈 Version History

• v2.0.12: feat: add --registry / -r flag for pushing to private container registries (AWS ECR, Google GAR, GHCR).
• v2.0.11: feat: support executing specific spec files directly in entrypoint.sh for Smart PR Routing.
• v2.0.7: The "Futuristic" Update. Complete rebrand to Agnox, intelligent framework detection, multi-platform buildx execution, @clack/prompts integration, identity collection, and native AI capabilities.
• v1.1.x: Initial release with base Playwright/Pytest generation.

🤝 Join the Pilot

Agnox is actively inviting forward-thinking companies to join our pilot program. Experience firsthand how our AI-driven deterministic execution engine transforms test failures into immediate bug fixes.

Request a Live Demo Today

License

MIT