[Question] Current release still rejects local plugin install paths

[pi-dal]

Question

I’m developing an opencli TS plugin locally and tried to install it with a local absolute path for easier iteration.

opencli plugin install /Users/pi-dal/Developer/opencli-plugin-sysu

On my machine (opencli 1.4.1), it still fails with:

Error: Invalid plugin source: \"/Users/pi-dal/Developer/opencli-plugin-sysu\"
Supported formats:
  github:user/repo
  https://github.com/user/repo

Why I’m asking

I noticed PR #491 mentions support for:

• opencli plugin install file:///path/to/my-plugin
• opencli plugin install /path/to/my-plugin

So I’m not sure whether the current behavior is:

1. an intentional design decision in released versions,
2. a feature that exists on main but has not been released yet,
3. or whether there is another required workflow for local plugin development.

Use case

For plugin development, local path install is very helpful because it allows a much tighter edit/test loop than publishing to GitHub or pushing every change first.

A local development workflow like this would be ideal:

opencli plugin install /path/to/plugin

or

opencli plugin install file:///path/to/plugin

Question for maintainers

Is the lack of local plugin install support in the current release a deliberate requirement, or would you be open to officially supporting local path install specifically to make plugin development easier?

If this is already supported on main but not yet released, knowing the expected version / timeline would also help.

Thanks.

[pi-dal]

I found the root cause on my side: this was due to my local version (), not a current product limitation. The local path install support from #491 was not available in the version I was testing with, so I misread it as an unsupported workflow in the current project state.

Sorry for the noise and for the confusion. I’m closing this issue.