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

atria-code

v1.0.14

Published

Coding agent CLI with read, bash, edit, write tools and session management

Downloads

4,009

Readme

atria

atria is a terminal coding agent. You give it a task in plain language; it reads files, runs shell commands, edits code, and writes new files in your working directory, asking for permission before mutating anything. It keeps a minimal, extensible core — TypeScript extensions, skills, prompt templates, and themes — and ships the product features on top as built-in extensions: a permission system, in-process subagents with workflow orchestration, an MCP client, web tools, an opt-in todo list with a task panel, and hierarchical .atria configuration.

atria runs in four CLI modes: interactive (TUI), print, JSON event stream, and RPC over stdin/stdout. The source workspace also exposes an SDK for embedding in Node.js applications; the published npm package contains the native CLI only.

Highlights

  • Permissions - four modes (default, accept-edits, plan, yolo); confirmation dialogs for shell commands, file mutations, subagents, and MCP tools; persistent allow/deny rules like bash(git push *); Alt+M cycles modes. See docs/permissions.md.
  • Subagents - delegate work to background agents (single, parallel, or chained), running in-process for fast startup; fork the parent conversation; continue finished agents; agent definitions in agents/ directories. See docs/subagents.md.
  • Workflows - deterministic JS orchestration scripts running many subagents in a sandbox, with phases, budgets, journaling, and resume. See docs/workflows.md.
  • MCP client - stdio and streamable HTTP servers via project .mcp.json and global ~/.atria/mcp.json; /mcp for status. See docs/mcp.md.
  • Web tools - web_fetch (URL to markdown) and web_search. See docs/tools.md.
  • Task tracking - an opt-in todo_write list (ATRIA_ENABLE_TODO_TOOLS=1) rendered above the editor, and a task panel showing running background work.
  • Interactive TUI - mouse support (click, drag-select, scroll), session tree navigation, theming, message queueing while the agent works, and ephemeral /btw side questions that do not alter the main conversation.
  • Hierarchical project resources - skills, prompts, themes, extensions, agents, and workflows load from ~/.atria plus .atria/ in the working directory and every ancestor directory; nearest wins name conflicts. Every hierarchical .atria/ATRIA.md is concatenated into project context. Settings, system-prompt files, and MCP configuration use narrower scopes documented in Configuration Layout.
  • Sessions - JSONL session files with in-place branching (/tree, /fork, /clone) and automatic context compaction. See docs/sessions.md.
  • Extensible - custom tools, commands, event handlers, and UI via TypeScript extensions; reusable skills and prompt templates; custom themes. See docs/extensions.md.

Installing and running atria

Install the published native CLI from npm (Node.js >= 22.19.0):

npm install -g atria-code
atria

For development, run directly from a source checkout:

cd /path/to/atria-code
npm install --ignore-scripts
./dev.sh

See docs/quickstart.md for installation details, source development, first-start project trust, and authentication (/login or provider API-key environment variables such as ANTHROPIC_API_KEY).

Documentation

Full index: docs/index.md

Start here

  • Quickstart - install or run from source, authenticate, first session.
  • Using atria - interactive mode, slash commands, mouse, CLI reference.

Features

Configuration

Extending & internals

Platform setup: Windows | Termux | tmux | Terminal setup | Shell aliases

Fork lineage

atria is a fork of earendil-works/pi. It retains pi's layered architecture — atria-tui (terminal UI), atria-ai (LLM providers and streaming), and atria-agent (the agent loop) — plus its extension model. Most atria product features live as built-in extensions in this package (src/core/builtin-extensions/); lower layers change only when terminal behavior, provider protocol normalization, or agent-loop semantics belong there. See docs/architecture.md.

License

MIT