@anglepoint/elevate-cli

Local adjustment tool for IBM EEP entitlements. Spike prototype to evaluate an agent-native CLI plus on-demand local React views as the design posture for the Q2 Data, Adjustments, and Export Interface project.

See ANGL-2061 for the spike charter and AGENTS.md for full agent orientation.

Status

Prototype, in active development. Not production-ready. Not stable.

Install

npm install -g @anglepoint/elevate-cli
elevate --version

The package is @anglepoint/elevate-cli; the binary it installs is elevate.

Requires Node 22.5+.

If you installed an earlier build (unscoped elevate or @anglepoint/elevate): uninstall it first to avoid a stale binary on PATH —

npm uninstall -g elevate @anglepoint/elevate
npm install -g @anglepoint/elevate-cli

Quickstart

elevate eep new --id acme-2026-q2 --dsw fixtures/sample-dsw.csv
elevate entitlement list --eep acme-2026-q2
elevate view --eep acme-2026-q2          # opens browser; React + Rsbuild HMR
elevate view --status
elevate view --stop

Agent bootstrap

elevate setup               # writes an orientation block to ~/.claude/CLAUDE.md
elevate setup --dry-run     # preview without writing
elevate setup --uninstall   # remove the block (deletes the file if nothing else remains)

After this, future Claude Code sessions on the machine will recognize elevate when the user mentions EEPs, entitlements, or IBM licensing — regardless of which directory the agent starts in. The block updates in place on re-run via marker comments. No effect on projects; only user-scope agent memory is touched.

Honors $CLAUDE_CONFIG_DIR if that directory already contains a CLAUDE.md; otherwise falls back to ~/.claude/.

Design notes

See AGENT-HARNESS.md for the design posture behind this CLI's agent-facing surface — why the tool's own output is treated as the primary guardrail for agents, rather than relying on project-local config files that only exist when the agent happens to be running in this repo.

Update

elevate update

Re-installs @anglepoint/elevate-cli@latest globally. Useful between releases. --dry-run prints the npm command without invoking it.

Note: this assumes you installed via npm. If you used pnpm/yarn/bun globally, run that tool's equivalent instead.

Releases

Releases are cut from this repo via a tag (vX.Y.Z); the Publish to npm GitHub Actions workflow does the publish with npm provenance attestations, authenticated via npm Trusted Publisher (OIDC) — no long-lived NPM_TOKEN secret.

npm version patch        # or minor/major — creates a commit + v<ver> tag
git push --follow-tags   # triggers .github/workflows/publish.yml

First-time publish (bootstrap)

npm's Trusted Publisher setup page isn't available for a package that doesn't exist yet, so the very first publish is done manually to bootstrap the package on the registry. After that, Trusted Publisher is configured via the package settings page and all subsequent publishes go through the GitHub Actions workflow (no local tokens).

One-time bootstrap:

# Log in with npm (opens a browser; picks the @anglepoint org)
npm login --scope=@anglepoint

# Publish from a clean checkout. No --provenance flag — provenance requires
# an OIDC issuer (GitHub Actions) and is not available for local publishes.
cd <repo>
git checkout main
git pull
npm publish --access public

# Verify
npm view @anglepoint/elevate-cli version

After the first publish, configure Trusted Publisher so subsequent tag pushes auto-publish:

1. Go to https://www.npmjs.com/package/@anglepoint/elevate-cli/access
2. Under Trusted Publishers, add:
   • Repository: Anglepoint-Inc/elevate-cli (exact case)
   • Workflow: .github/workflows/publish.yml
   • Environment: (leave blank unless you want a manual-approval gate; see below)
3. Save.

From here on, the release flow is npm version patch && git push --follow-tags and the Actions workflow takes it the rest of the way — with provenance attestations.

Optional: environment gate

For manual-approval-before-publish, create a GitHub Environment (e.g. production) under repo Settings → Environments, require reviewers, then add environment: production to the publish job in .github/workflows/publish.yml and update the npm trusted-publisher config to match. Tag pushes will then pause waiting for approval before npm publish runs.

Troubleshooting

If npm publish fails with a trusted-publisher / OIDC error, the npm-side config's repo, workflow path, and environment fields must exactly match what GitHub sends in the OIDC claim. Common mismatches:

• Repo path: Anglepoint-Inc/elevate-cli (case-sensitive; the -Inc matters)
• Workflow path: .github/workflows/publish.yml (relative from repo root, with .yml extension)
• Environment: leave blank on npm side unless the workflow job sets environment: — values must match exactly