Organized agentic coding for teams.

Follow @hyericlee on X for updates · Join the OpenPackage Discord for help and questions.

OpenPackage is the centralized hub for organizing your specs and configs for agentic coding, giving you consistent context and workflows between sessions, projects, and teams.

Modern AI coding tools are powerful, but lack organization, reusability, and efficiency.

• Specs across individuals and codebases, diverging, unversioned, and incohesive.
• Rules, commands, and subagents scattered across multiple projects.
• Familiar workflows rebuilt for each project, incompatible between AI coding platforms.

OpenPackage organizes your specs and AI coding configs into reusable packages that can be accessed by any session, any project, and any coding platform.

At it's core, OpenPackage is a lightweight CLI tool for creating versioned, AI coding platform agnostic packages, each contaning sets of specs and coding config files for simplified installs, uninstalls, and distribution.

No API keys required. No MCP installation.

1. Declare a package
2. Add specs and AI coding config files
3. Sync to multiple codebases

npm

npm install -g opkg 

opkg init # Initialize the workspace as a package, or opkg init <package> # Initialize a package under cwd `.openpackage/packages`

Directly update the files (at cwd or in .openpackage/packages/) and perform opkg save.
You can also use the add command to add workspace files to a package.

opkg add <package> <path-to-dir-or-file>

Use save or pack to save the set of dirs and files as a package to your local registry for reuse and distribution.

opkg save [package] # Prerelease/unversioned opkg pack [package] # Stable releases

opkg list

Shows all packages currently saved to the local registry.

opkg show <package>

Outputs the details of the package and lists all included files.

opkg install <package>

Adds all files under the specified package to the codebase at cwd.

opkg uninstall <package>

Removes all files for the specified package from the codebase at cwd.

opkg push <package>

opkg pull <package>

opkg login

Reuse rules, slash commands, and more across multiple codebases.

# In current codebase opkg save f specs/nextjs.md # In another codebase opkg install f/specs/nextjs.md

# In current codebase opkg save essentials # In another codebase opkg install essentials

Automatically sync your rules, slash commands, and more across multiple platform.

# Current codebase has .cursor, .claude, .opencode directories opkg save essentials .cursor/commands/essentials # OpenPackage CLI automatically generates/syncs the same command files across all platforms. # Before save: # .cursor/commands/essentials/cleanup.md # After save: # .cursor/commands/essentials/cleanup.md # .claude/commands/essentials/cleanup.md # .opencode/command/essentials/cleanup.md

Create domain specific packages for modular reuse.

# Create typescript package opkg save typescript .cursor/rules/typescript # Create scalable-nextjs package opkg save scalable-nextjs .cursor/rules/nextjs # Create scalable-nestjs package opkg save scalable-nestjs .cursor/rules/nestjs # Create mongodb package opkg save mongodb .cursor/rules/mongodb # In your NextJS codebase opkg install typescript opkg install scalable-nextjs # In your NestJS codebase opkg install typescript opkg install scalable-nestjs opkg install mongodb

Packages are composed using the following directory structure:

<package> ├── .openpackage/ │ ├── package.yml # The OpenPackage manifest, required │ ├── rules/ │ │ └── # Rule files │ ├── commands/ │ │ └── # Command files (slash commands) │ ├── agents/ │ │ └── # Agent files (subagents) │ └── skills/ │ └── # Skill files (Claude Code skills) ├── <dirs-or-files> │ └── # Any other root dirs or files (Ex: specs/, docs/, tests/, etc.) ├── README.md # Metadata files (LICENSE.md, CONTRIBUTING.md, etc.) └── AGENTS.md # Platform root file

There are two ways to compose packages:

• In a project workspace: opkg init <package> will create a package in .openpackage/packages/<packages>/
• In a dedicated package codebase: opkg init will create a package at cwd (similar to npm, pypi, etc.)

OpenPackage performs installation and platform sync of files for supported AI coding platforms outlined by the table below.

The built-in platforms.jsonc defines supported platforms, but can be overridden by user configs:

• Global: ~/.openpackage/platforms.jsonc (.json)
• Workspace: <cwd>/.openpackage/platforms.jsonc (.json)

Deep-merged (local > global > built-in) for per-project customization.

We would love your help building the future of package management for agentic coding.

Feel free to create PRs and Github issues for:

• Bugs
• Feature requests
• Support for new platforms
• Missing standard behavior
• Documentation

• Official Website and Registry
• Documentation
• Discord
• Creator X (Twitter)