Skip to content

fix: stop defaulting to retired agentskit.io hosts - #1847

Closed
EmersonBraun wants to merge 4 commits into
mainfrom
fix/retired-agentskit-hosts
Closed

EmersonBraun wants to merge 4 commits into
mainfrom
fix/retired-agentskit-hosts

Conversation

@EmersonBraun

Copy link
Copy Markdown
Member

Summary

ask.agentskit.io is retired and its DNS is about to be deleted. This removes the code defaults that still pointed at it.

  • Registry Ask widget (apps/registry/components/ask-widget.tsx): no longer falls back to https://ask.agentskit.io/v1/ask. It renders only when NEXT_PUBLIC_ASK_ENDPOINT is set.
  • Docs Ask widget (apps/docs-next/app/(home)/layout.tsx, app/docs/layout.tsx): passes NEXT_PUBLIC_ASK_ENDPOINT explicitly and renders only when it is set. This also matches the companion agentskit-chat change, where createAskAdapter requires endpoint.
  • apps/registry/.env.example: NEXT_PUBLIC_ASK_ENDPOINT is now empty, with a note that the widget is disabled when unset.
  • apps/ask-backend/README.md, apps/registry/README.md, RFC 0007: say the host is retired and that sites configure the backend through NEXT_PUBLIC_ASK_ENDPOINT. The RFC's historical body is unchanged; I added an update note at the top.
  • E2E: the docs and registry builds set NEXT_PUBLIC_ASK_ENDPOINT=https://ask.e2e.invalid/v1/ask, and the Playwright specs route that URL instead of the retired host.
  • Regenerated the README Standard hashes and the doc-bridge index. The index was already stale on main: it was missing the downloads dashboard files.

Behaviour change

NEXT_PUBLIC_ASK_ENDPOINT is now required for the docs and registry Ask widgets. When it is unset, both widgets are disabled (not rendered). Nothing was deleted.

Checks

  • pnpm install --frozen-lockfile, pnpm lint (60/60): pass
  • pnpm test: pass, except two tests that hit the 5s vitest timeout under parallel load. Both are unrelated to this change and pass on rerun:
    • @agentskit/net ratchet: passes with a longer timeout
    • @agentskit/svelte manifest test: passed in an earlier run
  • pnpm check:readme-standard, pnpm test:readme-standard, pnpm docs:bridge:gate: pass
  • Pre-push hook (quality gates, lint, build): pass
  • pnpm test:e2e: not run locally; left to CI
  • git grep for retired hosts: only historical records remain (RFC 0007 body plus its update note, the ask-backend README note saying the host is retired, and the generated doc-bridge index)

fleet agent and others added 4 commits October 21, 2026 19:42
The ask.agentskit.io host is retired. The Ask widgets in docs-next and registry now render only when NEXT_PUBLIC_ASK_ENDPOINT is set instead of falling back to the dead host. E2E builds set a placeholder endpoint and the specs mock it. Backend README and RFC 0007 note the retirement.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

URL Performance Accessibility Best practices SEO
http://127.0.0.1:3000/ 63 100 96 100
http://127.0.0.1:3000/docs 78 100 96 100
http://127.0.0.1:3000/docs/get-started/getting-started/quickstart 81 100 96 100
http://127.0.0.1:3000/stack 94 100 96 100
http://127.0.0.1:3000/showcase 90 100 96 100

Run by .github/workflows/lighthouse.yml.

@EmersonBraun

Copy link
Copy Markdown
Member Author

Superseded by #1848 (same tree; commit message rewrapped for commitlint without force-push).

@EmersonBraun
EmersonBraun deleted the fix/retired-agentskit-hosts branch October 23, 2026 00:45
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