JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1063
  • Score
    100M100P100Q131370F
  • License MIT

Unified CLI for the @glrs-dev ecosystem — OpenCode agent harness dispatch + worktree management.

Package Exports

  • @glrs-dev/cli
  • @glrs-dev/cli/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@glrs-dev/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@glrs-dev/cli

Unified CLI for the @glrs-dev ecosystem. One binary, two subcommands:

npm i -g @glrs-dev/cli
glrs oc install       # → OpenCode harness install
glrs wt new feature   # create a worktree
glrs wt list          # list worktrees across repos
glrs wt switch        # interactive picker

Requires Bun on PATH at runtime.

The harness-opencode bin remains available directly for power users who prefer the untagged entry point.

How it works

The glrs binary has two subcommands:

  • glrs oc <args> — dispatches to @glrs-dev/harness-plugin-opencode (bundled as a dependency). Resolves the bin via require.resolve(<package>/package.json) → reads the bin field → spawns with argv forwarded.
  • glrs wt <args> — worktree management, handled natively. Commands: new, list, switch, delete, cleanup. Worktrees are stored in ~/.glorious/worktrees/<repo>/<name>/.

Philosophy

  • Don't duplicate CLI logic. glrs oc is a thin spawn wrapper around harness-opencode.
  • One install, one thing to remember for the harness + worktree workflow.
  • Separate concerns stay separate. The SSO credential tool @glrs-dev/assume is a standalone Rust binary installed separately.

Docs

glrs.dev — full ecosystem docs.

License

MIT.