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

@jxtools/atlas

v3.2.0

Published

Autonomous Task Loop Agent System - automates task processing using AI coding agents

Readme


What is Atlas?

Atlas is an Autonomous Task Loop Agent System that processes tasks from a markdown backlog using AI coding agents. You define what needs to be done, Atlas handles everything else: branches, code, quality checks, PRs, and merges.


Install

npm install -g @jxtools/atlas

Update

atlas update

Requirements

  • Node.js 18+ (for npm installation)
  • AI Provider (at least one):
  • Git (optional - enables branches, PRs, and commits)

AI Provider Configuration

Atlas supports multiple AI providers:

| Provider | Flag | Documentation | |----------|------|---------------| | Claude Code (default) | --cli claudecode | docs.anthropic.com/claude-code | | OpenCode | --cli opencode | opencode.ai/docs | | Codex (OpenAI) | --cli codex | developers.openai.com/codex/cli |

# Use Claude Code (default)
atlas 25

# Use OpenCode
atlas --cli opencode 25

# Use Codex
atlas --cli codex 25

# Or set environment variable (persists across sessions)
export ATLAS_CLI=codex
atlas 25

Recommendation: Use Claude Code for atlas plan (interactive mode works best). For autonomous execution (atlas [N]), any provider works.


Quick Start

cd your-project
atlas init

# Recommended flow (AI plans + executes)
atlas plan "add user authentication with JWT"
atlas 5

If you prefer manual planning, you can still edit .atlas/backlog.md directly:

# Manual flow (you write tasks)
# Edit .atlas/backlog.md with your tasks
atlas

Commands

| Command | Description | |---------|-------------| | atlas init | Initialize .atlas/ in current project | | atlas plan "..." | Interactive feature planning (interview -> spec -> tasks) | | atlas [N] | Run N iterations autonomously (default: 25) | | atlas review [--dry-run] | Audit Atlas state and auto-fix inconsistencies (or report only with dry-run) | | atlas resume [N] | Resume an interrupted session from its active integration branch/PR | | atlas clean [--all] | Clean runtime artifacts from .atlas/ | | atlas logs [--tail N] | Show iteration logs (default: last 10) | | atlas logs --failed | Show only failed iterations | | atlas logs --search <pat> | Search logs for pattern | | atlas status | Show task counts and active session info | | atlas doctor | Check Atlas installation and dependencies | | atlas update | Show how to update via NPM | | atlas help | Show help |


Planning Mode

For complex features, use atlas plan to interview and decompose before autonomous execution:

atlas plan "add user authentication with JWT"
# -> Interactive interview about requirements
# -> Generates spec in .atlas/specs/
# -> Creates tasks in backlog with **Spec:** field

atlas 5
# -> Executes 5 tasks autonomously (no human intervention)
# -> Each task reads the full spec for context (integral view)

Resuming Sessions

If Atlas is interrupted (quota limit, error, Ctrl+C), resume with:

atlas resume      # Continue with default iterations
atlas resume 5    # Continue with 5 iterations

Resume will:

  1. Find the active integration branch
  2. Verify PR is not merged/closed
  3. Continue processing tasks from backlog

Reviewing Work

After Atlas completes (or is interrupted), audit and fix issues:

atlas review           # Detect and auto-fix issues
atlas review --dry-run # Report only, no changes
atlas --cli opencode review --dry-run # Same, using OpenCode

Review checks for:

  • Tasks stuck in wrong state (multiple IN_PROGRESS, etc.)
  • Orphaned PRs not merged to integration
  • Backlog out of sync with merged PRs
  • Uncommitted changes and unpushed commits

Auto-fixes safe issues and reports those requiring manual intervention.


Cleaning Runtime Files

Use clean to remove local runtime artifacts:

atlas clean       # Remove .atlas/runs/*.log and temporary files
atlas clean --all # Also reset activity/errors logs and stale session metadata

Configuration

Override defaults with ATLAS_ environment variables:

export ATLAS_CLI=claudecode         # AI provider: claudecode (default), opencode, or codex
export ATLAS_MAX_ITERATIONS=25      # Max iterations per run
export ATLAS_TIMEOUT=1200           # Timeout per iteration (seconds)
export ATLAS_STALE_SECONDS=7200     # Reset stuck tasks (seconds, 0 to disable)
export ATLAS_DEFAULT_BRANCH=main    # Override auto-detected default branch
export ATLAS_NOTIFY_TELEGRAM=true   # Enable Telegram notifications
export ATLAS_TELEGRAM_BOT="token"   # Telegram bot token
export ATLAS_TELEGRAM_CHAT="id"     # Telegram chat ID

How It Works

for each iteration:
    1. Resume task in IN_PROGRESS, or pick first from TODO
    2. [git] Create branch from integration: [type]/[TASK_ID]-[description]
    3. Move to IN_PROGRESS [git: + commit]
    4. Implement task
    5. Run quality gates (from CLAUDE.md)
    6. [git] Create PR -> merge (squash) to integration branch
    7. Move to DONE [git: + commit]
    8. Write to progress.txt and guardrails.md
    9. If error -> log to errors.log, move back to TODO
   10. If no tasks -> exit loop

Modes:

  • Git mode (default): Creates integration branch, PRs merge there, human reviews before main
  • Local mode: Works without git - changes stay in working directory

Features:

  • Context files pre-loaded (backlog, guardrails, progress, CLAUDE.md)
  • Commits state changes immediately (crash recovery) [git mode]
  • Stale tasks auto-reset to TODO after timeout

Backlog Format

## TODO
### HIGH-001: Task title
- **Category:** feature
- **Description:** What needs to be done

## IN_PROGRESS

## DONE
### HIGH-000: Completed task
- **Completed:** 2026-01-15
- **PR:** #1

## DELAYED
### LOW-001: Blocked task
- **Reason:** Why it's blocked

Project Structure

After atlas init (specs/ appears after atlas plan):

your-project/
├── CLAUDE.md              # Project rules + quality gates (you create this)
└── .atlas/
    ├── backlog.md         # Task list
    ├── progress.txt       # Learnings from completed tasks
    ├── guardrails.md      # Rules from past errors
    ├── errors.log         # Failure log
    ├── activity.log       # Run history
    ├── specs/             # Feature specs (created by atlas plan)
    └── runs/              # Iteration logs

Quality Gates

Define in your project's CLAUDE.md:

## Quality Gates
- `npm run build` must pass
- `npm test` must pass

Atlas reads CLAUDE.md before each task.


License

ISC