Skip to content

chore: rename hosting to pagent.link + api.pagent.link#17

Merged
alextnetto merged 1 commit into
mainfrom
rename-to-pagent-link
May 15, 2026
Merged

chore: rename hosting to pagent.link + api.pagent.link#17
alextnetto merged 1 commit into
mainfrom
rename-to-pagent-link

Conversation

@alextnetto
Copy link
Copy Markdown
Member

Summary

Move canonical hosting from pagent.vercel.app / pagent.up.railway.app to pagent.link (FE) and api.pagent.link (API).

  • pagent.link is now the public renderer URL.
  • api.pagent.link is now the public API URL.
  • The Vercel *.vercel.app and Railway *.up.railway.app URLs continue to work transitionally (Railway has both domains attached; the auto-alias workflow keeps pagent.vercel.app pinned to the same deployment for now).

Why this is one PR

Touches every layer that has a hardcoded URL: the API source/tests/error messages, the renderer source/tests/CSP defaults, the MCP server's hardcoded default, the OpenAPI servers list, the skill prose, the README, the OpenAPI YAML, the CI workflow's build-time VITE_API_URL, the auto-alias workflow's ALIAS value, both plugin manifests, the requests.prod.http HTTP-client vars, and the apps/web/home.ts demo screenshot.

Done as a single rename pass so CI runs against a coherent state (no flickering "API points here, FE points there" interim states).

Out of scope but coordinated

These are managed out-of-band (not in this PR):

  • Vercel env var VITE_API_URL: updated from https://pagent.up.railway.apphttps://api.pagent.link via vercel env.
  • Railway env vars: PUBLIC_URL set to https://pagent.link, ALLOWED_ORIGINS set to https://pagent.link,https://pagent.vercel.app (the old vercel host is kept in CORS transitionally — some existing share links may still resolve there until the auto-alias retires).
  • Vercel custom domain pagent.link is already registered to the project and aliased to the latest production deployment.
  • Railway custom domain api.pagent.link is attached to the API service; TLS cert is provisioning at the time of writing.

What's preserved (audit trail)

  • All files under docs/superpowers/plans/ and docs/superpowers/specs/ keep their original URL references. They're time-stamped historical records of brainstorming/design/execution; revisionist editing isn't appropriate.
  • docs/HANDOFF.md keeps the user's local filesystem path verbatim — it's accurate for the local checkout regardless of GitHub repo name.

What's removed

  • apps/mcp/package-lock.json (root package-lock.json is the authoritative workspace lockfile; the per-app file was a legacy leftover still pointing at @agent-ui-session/mcp). Confirmed nothing references it.

Test plan

  • npm run typecheck — green
  • npm run lint — green
  • npm run format:check — green
  • npm run test237 passing across 16 test files (test fixtures updated alongside production strings)
  • VITE_API_URL=https://api.pagent.link npm run build:web — green
  • npm run build:mcp — green, new bundle has https://api.pagent.link as the embedded default
  • git grep "pagent.vercel.app" — 0 hits (excluding superpowers historical docs)
  • git grep "pagent.up.railway.app" — 0 hits in active code (1 hit in a historical plan doc)
  • Once merged: e2e smoke on pagent.link + api.pagent.link

Follow-up (not blocking)

  • GitHub repo rename blockful/agent-ui-sessionblockful/pagent (the codebase already references blockful/pagent everywhere; the rename happens last to flip the actual repo name without leaving a window of broken refs).
  • VERCEL_TOKEN GitHub secret is still unset, so the Pin pagent.link to latest production workflow remains a no-op. Manual vercel alias on each prod deploy until that secret is set.

- FE: pagent.vercel.app → pagent.link
- API: pagent.up.railway.app → api.pagent.link
- Project name in active docs/diagrams: agent-ui-session → pagent
  (historical plans/specs under docs/superpowers/ are left as-is —
  they're audit trail of work-as-it-happened.)
- Rebuilt apps/mcp/server.bundle.js with the new SERVICE_URL default.
- Removed apps/mcp/package-lock.json (stale; the workspace lockfile
  at the repo root is authoritative).

Production-side env var changes (Vercel VITE_API_URL, Railway
PUBLIC_URL and ALLOWED_ORIGINS) and Railway custom-domain setup
happen out-of-band; this commit is the codebase-side of the rename.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pagent Ready Ready Preview, Comment May 15, 2026 11:12pm

Request Review

@alextnetto alextnetto merged commit b46e22b into main May 15, 2026
3 checks passed
@alextnetto alextnetto deleted the rename-to-pagent-link branch May 15, 2026 23:16
alextnetto added a commit that referenced this pull request May 15, 2026
Follow-up to #17. The pagent.link rename in #17 updated the MCP and
preview URLs but left the install-prompt Skill link pointing at
raw.githubusercontent.com. Adds a Vercel rewrite so /SKILL.md proxies
the GitHub raw file (single hop, no client redirect handling needed)
and points the prompt at the short URL.

- vercel.json: rewrite /SKILL.md -> raw.githubusercontent.com/.../SKILL.md
- AGENT_PROMPT Skill URL: https://pagent.link/SKILL.md
alextnetto added a commit that referenced this pull request May 15, 2026
#18)

Follow-up to #17. The pagent.link rename in #17 updated the MCP and
preview URLs but left the install-prompt Skill link pointing at
raw.githubusercontent.com. Adds a Vercel rewrite so /SKILL.md proxies
the GitHub raw file (single hop, no client redirect handling needed)
and points the prompt at the short URL.

- vercel.json: rewrite /SKILL.md -> raw.githubusercontent.com/.../SKILL.md
- AGENT_PROMPT Skill URL: https://pagent.link/SKILL.md
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