fix(readme): update broken self-hosting docs link

The old link (docs.agpt.co/platform/getting-started/) redirects to a 400 error. Updated to the correct working URL. Fixes #OPEN-2973
hotfix(frontend): fix home redirect (3) (#11904 )
2026-01-31 01:48:23 -05:00 · 2026-01-30 22:51:25 +00:00 · 2026-01-30 20:40:46 +07:00 · 2026-01-30 19:08:26 +07:00 · 2026-01-30 17:20:03 +07:00 · 2026-01-30 08:32:50 +00:00
3 changed files with 19 additions and 13 deletions
--- a/README.md
+++ b/README.md
@@ -54,7 +54,7 @@ Before proceeding with the installation, ensure your system meets the following
 ### Updated Setup Instructions:
 We've moved to a fully maintained and regularly updated documentation site.

-👉 [Follow the official self-hosting guide here](https://docs.agpt.co/platform/getting-started/)
+👉 [Follow the official self-hosting guide here](https://agpt.co/docs/platform/getting-started/getting-started)


 This tutorial assumes you have Docker, VSCode, git and npm installed.
--- a/autogpt_platform/frontend/src/app/page.tsx
+++ b/autogpt_platform/frontend/src/app/page.tsx
@@ -1,14 +1,15 @@
 "use client";

-import { FeatureFlagRedirect } from "@/services/feature-flags/FeatureFlagRedirect";
-import { Flag } from "@/services/feature-flags/use-get-flag";
+import { LoadingSpinner } from "@/components/atoms/LoadingSpinner/LoadingSpinner";
+import { useRouter } from "next/navigation";
+import { useEffect } from "react";

 export default function Page() {
-  return (
-    <FeatureFlagRedirect
-      flag={Flag.CHAT}
-      whenEnabled="/copilot"
-      whenDisabled="/library"
-    />
-  );
+  const router = useRouter();
+
+  useEffect(() => {
+    router.replace("/copilot");
+  }, [router]);
+
+  return <LoadingSpinner size="large" cover />;
 }
--- a/autogpt_platform/frontend/src/services/feature-flags/feature-flag-provider.tsx
+++ b/autogpt_platform/frontend/src/services/feature-flags/feature-flag-provider.tsx
@@ -1,5 +1,6 @@
 "use client";

+import { LoadingSpinner } from "@/components/atoms/LoadingSpinner/LoadingSpinner";
 import { useSupabase } from "@/lib/supabase/hooks/useSupabase";
 import * as Sentry from "@sentry/nextjs";
 import { LDProvider } from "launchdarkly-react-client-sdk";
@@ -15,7 +16,9 @@ export function LaunchDarklyProvider({ children }: { children: ReactNode }) {
  const clientId = environment.getLaunchDarklyClientId();

  const context = useMemo(() => {
-    if (isUserLoading || !user) {
+    if (isUserLoading) return;
+
+    if (!user) {
      return {
        kind: "user" as const,
        key: "anonymous",
@@ -38,10 +41,12 @@ export function LaunchDarklyProvider({ children }: { children: ReactNode }) {
    return <>{children}</>;
  }

+  if (isUserLoading) {
+    return <LoadingSpinner size="large" cover />;
+  }
+
  return (
    <LDProvider
-      // Add this key prop. It will be 'anonymous' when logged out,
-      key={context.key}
      clientSideID={clientId ?? ""}
      context={context}
      timeout={LAUNCHDARKLY_INIT_TIMEOUT_MS}
Author	SHA1	Message	Date
Otto	7607b93947	fix(readme): update broken self-hosting docs link The old link (docs.agpt.co/platform/getting-started/) redirects to a 400 error. Updated to the correct working URL. Fixes #OPEN-2973	2026-01-30 22:51:25 +00:00
Ubbe	cc4839bedb	hotfix(frontend): fix home redirect (3) (#11904 ) ### Changes 🏗️ Further improvements to LaunchDarkly initialisation and homepage redirect... ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Run the app locally with the flag disabled/enabled, and the redirects work --------- Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Ubbe <0ubbe@users.noreply.github.com>	2026-01-30 20:40:46 +07:00
Otto	dbbff04616	hotfix(frontend): LD remount (#11903 ) ## Changes 🏗️ Removes the `key` prop from `LDProvider` that was causing full remounts when user context changed. ### The Problem The `key={context.key}` prop was forcing React to unmount and remount the entire LDProvider when switching from anonymous → logged in user: ``` 1. Page loads, user loading → key="anonymous" → LD mounts → flags available ✅ 2. User finishes loading → key="user-123" → React sees key changed 3. LDProvider UNMOUNTS → flags become undefined ❌ 4. New LDProvider MOUNTS → initializes again → flags available ✅ ``` This caused the flag values to cycle: `undefined → value → undefined → value` ### The Fix Remove the `key` prop. The LDProvider handles context changes internally via the `context` prop, which triggers `identify()` without remounting the provider. ## Checklist 📋 - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [ ] I have tested my changes according to the test plan: - [ ] Flag values don't flicker on page load - [ ] Flag values update correctly when logging in/out - [ ] No redirect race conditions Related: SECRT-1845	2026-01-30 19:08:26 +07:00
Ubbe	e6438b9a76	hotfix(frontend): use server redirect (#11900 ) ### Changes 🏗️ The page used a client-side redirect (`useEffect` + `router.replace`) which only works after JavaScript loads and hydrates. On deployed sites, if there's any delay or failure in JS execution, users see an empty/black page because the component returns null. Fix: Converted to a server-side redirect using redirect() from next/navigation. This is a server component now, so: ### Checklist 📋 #### For code changes: - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] Tested locally but will see it fully working once deployed	2026-01-30 17:20:03 +07:00
Otto	e10ff8d37f	fix(frontend): remove double flag check on homepage redirect (#11894 ) ## Changes 🏗️ Fixes the hard refresh redirect bug (SECRT-1845) by removing the double feature flag check. ### Before (buggy) ``` / → checks flag → /copilot or /library /copilot (layout) → checks flag → /library if OFF ``` On hard refresh, two sequential LD checks created a race condition window. ### After (fixed) ``` / → always redirects to /copilot /copilot (layout) → single flag check via FeatureFlagPage ``` Single check point = no double-check race condition. ## Root Cause As identified by @0ubbe: the root page and copilot layout were both checking the feature flag. On hard refresh with network latency, the second check could fire before LaunchDarkly fully initialized, causing users to be bounced to `/library`. ## Test Plan - [ ] Hard refresh on `/` → should go to `/copilot` (flag ON) - [ ] Hard refresh on `/copilot` → should stay on `/copilot` (flag ON) - [ ] With flag OFF → should redirect to `/library` - [ ] Normal navigation still works Fixes: SECRT-1845 cc @0ubbe	2026-01-30 08:32:50 +00:00