Rename gitclaw → gitagent across the entire project - #43
Merged
Conversation
Project-wide rename following the repo move to open-gitagent/gitagent. - npm package name and bin: gitclaw -> gitagent - env vars: GITCLAW_* -> GITAGENT_* (PASSWORD, USERNAME, CLOUD, OTEL_ENABLED, MODEL_BASE_URL, MAX_FILE_BYTES) - OpenTelemetry span/metric prefixes: gitclaw.* -> gitagent.* - global plugin dir: ~/.gitclaw/plugins -> ~/.gitagent/plugins (per-agent runtime dir <agent>/.gitagent/ was already named that and is unchanged) - repo URLs, README, Documentation, install.sh, examples, skills, identity files, and the logo asset (gitclaw-logo.png -> gitagent-logo.png) Pure rename: 304 insertions / 304 deletions, balanced. tsc build is clean and all 27 tests pass. BREAKING: existing GITCLAW_* env vars and the `gitclaw` CLI name no longer work — callers must switch to GITAGENT_* and `gitagent`.
npm ci enforces that package-lock.json matches package.json. After the rename, the committed lockfile still said name "gitclaw" (and also pointed every dependency at a private kavak.jfrog.io Artifactory mirror, which GitHub Actions can't auth to). Both would break the publish.yml workflow's `npm ci` step. Regenerated against registry.npmjs.org with the new package name: - root name: gitclaw -> gitagent (matches package.json) - 333/333 packages now resolve to registry.npmjs.org with integrity - 0 kavak.jfrog.io URLs Verified: `npm ci` + `npm run build` both succeed locally.
shreyas-lyzr
added a commit
that referenced
this pull request
May 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Project-wide rename following the repo move to open-gitagent/gitagent.
What changed
gitclaw→gitagentGITCLAW_*→GITAGENT_*(PASSWORD,USERNAME,CLOUD,OTEL_ENABLED,MODEL_BASE_URL,MAX_FILE_BYTES)gitclaw.*→gitagent.*(gitagent.agent.session,gitagent.tool.execute,gitagent.tool.calls,gitagent.session.cost_usd, …)~/.gitclaw/plugins→~/.gitagent/plugins<agent>/.gitagent/was already named.gitagentand is unchanged — no collision (different locations: HOME vs agent dir).gitclaw-logo.png→gitagent-logo.png).Scope
gitclaw→gitagent,GITCLAW→GITAGENT,GitClaw→GitAgent,Gitclaw→GitagentVerification
npm run build(tsc) — cleannpm test— 27/27 pass (telemetry span-name assertions updated in lockstep withtelemetry.ts)gitclawCLI name is gone — usegitagent.GITCLAW_*env vars are gone — useGITAGENT_*. No backward-compat fallback is included (can add one if desired).gitclawnpm package must switch togitagent.🤖 Generated with Claude Code