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, three subcommands:

npm i -g @glrs-dev/cli

glrs oc install              # → harness-opencode install
glrs agentic wt new feature  # → gs-agentic wt new feature
glrs assume login aws        # → gs-assume login aws

Each subtool still ships its own direct bin — harness-opencode, gs-agentic / gsag, gs-assume / gsa — if you prefer typing those. The dispatcher exists to give new users one install command and one entry point to remember.

How it works

The glrs binary is a thin dispatcher. It:

Reads the first positional arg as the subcommand (oc, agentic, assume)
Resolves the underlying binary via require.resolve(<package>/package.json) → reads the bin field
Spawns the binary with the remaining argv forwarded, inheriting stdio
Exits with the child's exit code

For the assume subcommand, the dispatcher imports @glrs-dev/assume's exported getBinaryPath() directly and execs the prebuilt Rust binary — skipping the TS shim middle-layer for interactive credential operations.

Philosophy

Don't duplicate CLI logic. Every flag, every subcommand, every option lives in the underlying tool. The dispatcher adds no behavior.
Don't fragment muscle memory. harness-opencode / gsag / gsa keep working forever. glrs is additive, not a replacement.
One install, one thing to remember. For new users in the @glrs-dev ecosystem, npm i -g @glrs-dev/cli gets them everything.

Docs

glrs.dev — full ecosystem docs.

License

MIT.