-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Issue
When installing packages you should be able to declare if you where you want to install them to as it may not always be the current workspace.
The new --cwd command is great to let you set a specific directory to source and target but some simple flags that can specify local, project, user, and global locations to target for deployment would make deploying packages much easier.
Proposed Solution
Adding the following two flags offers behaviour for targeting settings locations that are common between most platforms
-
--project publishes to the current workspace (default behaviour)
-
--user publishes to the user home directory `~/' . This allows the content to be discoverable systemwide for the user.
However how different ai platforms handle setting global settings for all users and local settings are different and perhaps outside the initial scope of this issue, which are:
- --global publishes md files in a location that is accessible to all users on the machine (varies by platform)
- --local publishes md files to the current workspace but creates them as *.local.*files so the user can add them to ignore files.
Expected workflow
# Installs packages at the user directory level
openpackage install some-package --user
# Installs packages at the user directory level from another directory that has a .openpackage file with a local registry
openpackage install some-package --cwd another/directory --userReferences
Claude Code Configuration Scopes
- https://code.claude.com/docs/en/settings#configuration-scopes
Claude Code Plugins Install Scopes - https://code.claude.com/docs/en/discover-plugins#install-plugins