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

create-openzosma

v0.0.6

Published

Interactive setup CLI for OpenZosma -- self-hosted AI agent platform

Readme

create-openzosma

Interactive setup CLI for OpenZosma

Go from zero to a running AI agent platform with a single command.


What is OpenZosma?

OpenZosma is an open-source, self-hosted platform for creating hierarchical AI agents that act as digital work twins for your team. You define an agent org chart that mirrors your business structure, delegate tasks through natural conversation, and manage operations from your phone, WhatsApp, Slack, or a web dashboard.

This package (create-openzosma) is the interactive setup CLI that handles cloning, environment configuration, Docker services, database migrations, and the initial build in one shot -- so you don't have to do any of it manually.


Quick Start

# Using pnpm (recommended)
pnpm create openzosma

# Using npx
npx create-openzosma

That's it. The CLI walks you through every decision interactively -- no flags to memorize, no YAML to edit by hand.

Already cloned the repo?

Contributors who already cloned the repo can run the setup from the project root:

pnpm setup

The CLI auto-detects whether it's inside an OpenZosma repo and skips the clone step.


What It Does

The setup pipeline runs 12 steps in order:

| # | Step | What happens | |---|------|-------------| | 1 | Prerequisites | Checks for Node.js 22+, pnpm, Docker, Docker Compose, Git. Warns if OpenShell CLI is missing. | | 2 | Project | Clones the repo into a new directory, or detects an existing checkout. | | 3 | LLM Provider | Pick your provider (Anthropic, OpenAI, Google, etc.) and enter an API key. | | 4 | Local Model | Optional. Configure a local/self-hosted model endpoint (Ollama, vLLM, etc.). | | 5 | Database | PostgreSQL connection details. Defaults to localhost:5432/openzosma. | | 6 | Sandbox | Choose local mode (in-process, for development) or orchestrator mode (isolated OpenShell sandboxes, for production). | | 7 | Auth | Auto-generates BETTER_AUTH_SECRET and ENCRYPTION_KEY. Optionally configure Google/GitHub OAuth. | | 8 | .env | Writes .env.local with all collected values. | | 9 | Docker | Starts PostgreSQL (with pgvector), Valkey, and RabbitMQ via docker compose up -d. | | 10 | Install | Runs pnpm install to install all dependencies. | | 11 | Build | Builds all packages with Turborepo (required before migrations). | | 12 | Migrations | Runs database schema and auth migrations against PostgreSQL. |

At the end, it offers to start the gateway (port 4000) and dashboard (port 3000) for you.


Supported LLM Providers

| Provider | Default Model | Env Variable | |----------|--------------|-------------| | Anthropic | Claude Sonnet 4 | ANTHROPIC_API_KEY | | OpenAI | GPT-4o | OPENAI_API_KEY | | Google | Gemini 2.5 Flash | GEMINI_API_KEY | | Groq | Llama 3.3 70B | GROQ_API_KEY | | xAI | Grok 3 | XAI_API_KEY | | Mistral | Mistral Large | MISTRAL_API_KEY | | Local model | Any OpenAI-compatible endpoint | OPENZOSMA_LOCAL_MODEL_URL |


Execution Modes

| Mode | Description | Use case | |------|-------------|----------| | Local | pi-agent runs in-process inside the gateway. No container isolation. | Development, testing | | Orchestrator | Each user gets a persistent OpenShell sandbox with Landlock + seccomp isolation. | Production deployments |

The orchestrator mode requires the OpenShell CLI. If it's not found during prerequisites, the CLI offers to install it for you.


Requirements

| Tool | Version | Required | |------|---------|----------| | Node.js | >= 22 | Yes | | pnpm | Latest | Yes | | Docker | Latest | Yes | | Docker Compose | Latest | Yes | | Git | Any | Yes | | OpenShell CLI | Latest | Only for orchestrator sandbox mode |


What Gets Created

After the CLI finishes, your project directory will contain:

openzosma/
  .env.local              Environment configuration (API keys, DB, auth secrets)
  apps/
    web/                  Next.js dashboard (port 3000)
  packages/
    gateway/              API gateway (port 4000)
    orchestrator/         Sandbox lifecycle management
    db/                   Database migrations and queries
    auth/                 Better Auth setup
    ...                   Other packages

Open http://localhost:3000, sign up, and start a conversation with your first agent.


Troubleshooting

Docker not running: The CLI checks for Docker during prerequisites. Make sure the Docker daemon is started before running the CLI.

Port conflicts: The gateway defaults to port 4000 and the dashboard to port 3000. If these ports are in use, stop the conflicting processes or change the ports in .env.local.

Build failures: If the build step fails, ensure you have Node.js 22+ installed. Run node --version to check. The build requires Turborepo which is included as a dev dependency.

Migration errors: Migrations require PostgreSQL to be running and accessible. The Docker step starts PostgreSQL automatically. If you're using an external database, verify the connection details in .env.local.


Related


License

Apache-2.0