Skip to content

chore(brand): point everything at the renamed repo vikasprogrammer/agentric (v0.331.1) - #605

Merged
vikasprogrammer merged 1 commit into
mainfrom
feat/repo-slug
Aug 10, 2026
Merged

chore(brand): point everything at the renamed repo vikasprogrammer/agentric (v0.331.1)#605
vikasprogrammer merged 1 commit into
mainfrom
feat/repo-slug

Conversation

@vikasprogrammer

Copy link
Copy Markdown
Owner

Follow-through on #604. The repo is now vikasprogrammer/agentric — the last public brand
surface. GitHub keeps a permanent redirect, so existing clones/remotes/issue links keep resolving
(the old agent-os name must never be claimed by a new repo, or the redirect dies).

Swept: README clone block, console FEEDBACK_URL, the gh --repo … lines in CLAUDE.md /
TODO.md / scripts/wt.sh / docs/goals-plan.md / fleet-insights SKILL.md, both service
Documentation= URLs (they still pointed at the wrong org, InstaWP/agent-os). CHANGELOG history
links left as written.

Deliberately not renamed (now spelled out in CLAUDE.md → Naming): npm package + CLI agent-os,
AGENT_OS_*, AOS_*, AgentOS, mcp__agentos__*, /agent-os <agent>, unit names, data homes,
the local checkout paths (~/Projects/agent-os, ~/agent-os-live, ~/aos-wt), and the GitHub
App slug agent-os-instapods — renaming that changes its installation URLs and breaks
per-member GitHub auth.

Verified: npm run typecheck · npm run build · cd web && npm run build ·
npm run test:governance (exit 0, 18 suites green).

🤖 Generated with Claude Code

https://claude.ai/code/session_015ZUfffxY4hKv7M6wMCcaTz

…entric (v0.331.1)

The GitHub repo is now `vikasprogrammer/agentric` — the last public brand surface
left after the Agentric rename. GitHub keeps a permanent redirect, so existing
clones, remotes and issue links keep resolving; the old `agent-os` name must never
be claimed by a new repo or that redirect dies.

Swept the hardcoded slug out of the README clone block, the console's FEEDBACK_URL,
the `gh --repo …` lines in CLAUDE.md / TODO.md / scripts/wt.sh / docs/goals-plan.md /
the fleet-insights skill, and both service `Documentation=` URLs (which still pointed
at the wrong org). CHANGELOG history links are left as written.

CLAUDE.md → Naming now records the repo on the brand side of the split, and names the
two things that look renameable but are not: the local checkout paths, and the GitHub
App slug `agent-os-instapods` (renaming it changes installation URLs and breaks
per-member GitHub auth).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZUfffxY4hKv7M6wMCcaTz
@vikasprogrammer
vikasprogrammer merged commit 6c473fc into main Aug 10, 2026
1 check passed
@vikasprogrammer
vikasprogrammer deleted the feat/repo-slug branch August 10, 2026 11:34
vikasprogrammer added a commit that referenced this pull request Aug 11, 2026
…entric (v0.331.1) (#605)

The GitHub repo is now `vikasprogrammer/agentric` — the last public brand surface
left after the Agentric rename. GitHub keeps a permanent redirect, so existing
clones, remotes and issue links keep resolving; the old `agent-os` name must never
be claimed by a new repo or that redirect dies.

Swept the hardcoded slug out of the README clone block, the console's FEEDBACK_URL,
the `gh --repo …` lines in CLAUDE.md / TODO.md / scripts/wt.sh / docs/goals-plan.md /
the fleet-insights skill, and both service `Documentation=` URLs (which still pointed
at the wrong org). CHANGELOG history links are left as written.

CLAUDE.md → Naming now records the repo on the brand side of the split, and names the
two things that look renameable but are not: the local checkout paths, and the GitHub
App slug `agent-os-northwind` (renaming it changes installation URLs and breaks
per-member GitHub auth).


Claude-Session: https://claude.ai/code/session_015ZUfffxY4hKv7M6wMCcaTz

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant