docs: update Workflow DevKit to Workflow SDK branding

README.md

@@ -32,7 +32,7 @@ That separation is the main point of the project:
 ## Current capabilities
 
 - chat-driven coding agent with file, search, shell, task, skill, and web tools
-- durable multi-step execution with Workflow DevKit-backed runs
+- durable multi-step execution with Workflow SDK-backed runs
 - isolated Vercel sandboxes with snapshot-based resume
 - repo cloning and branch work inside the sandbox
 - optional auto-commit, push, and PR creation after a successful run

apps/web/app/layout.tsx

@@ -53,7 +53,7 @@ export const metadata: Metadata = {
     template: "%s | Open Agents",
   },
   description:
-    "Spawn coding agents that run infinitely in the cloud. Powered by AI SDK, Gateway, Sandbox, and Workflow DevKit.",
+    "Spawn coding agents that run infinitely in the cloud. Powered by AI SDK, Gateway, Sandbox, and Workflow SDK.",
   icons: {
     icon: faviconPath,
     shortcut: faviconPath,

apps/web/app/opengraph-image.tsx

@@ -153,7 +153,7 @@ export default function OgImage() {
           <TechPill label="AI SDK" />
           <TechPill label="Gateway" />
           <TechPill label="Sandbox" />
-          <TechPill label="Workflow DevKit" />
+          <TechPill label="Workflow SDK" />
 
           {/* Spacer + domain */}
           <div

apps/web/components/auth/signed-out-hero.tsx

@@ -32,7 +32,7 @@ export function SignedOutHero() {
                 style={{ animationDelay: "90ms" }}
               >
                 Spawn coding agents that run infinitely in the cloud. Powered by
-                AI SDK, Gateway, Sandbox, and Workflow DevKit.
+                AI SDK, Gateway, Sandbox, and Workflow SDK.
               </p>
             </div>
 

apps/web/components/landing/bento.tsx

@@ -24,7 +24,7 @@ const items: readonly BentoItem[] = [
   },
   {
     id: "004",
-    title: "Workflow DevKit",
+    title: "Workflow SDK",
     body: "Durable, resumable agent workflows that survive restarts and coordinate multi-step operations.",
   },
 ];

apps/web/components/landing/footer.tsx

@@ -51,7 +51,7 @@ export function LandingFooter() {
                 rel="noopener noreferrer"
                 className="font-mono text-sm text-(--l-fg-3) transition-colors hover:text-(--l-fg)"
               >
-                Workflow DevKit
+                Workflow SDK
               </a>
             </div>
           </div>

docs/agents/lessons-learned.md

@@ -23,7 +23,7 @@ Hard-won knowledge from building this codebase. When you make a mistake or disco
 - Next.js `after()` defers callbacks until the response is fully sent; for streaming endpoints this means `after()` runs after the entire stream completes, not at call time. Use fire-and-forget (`void run()`) for lifecycle kicks that must happen at request start.
 - In Next.js Route Handlers, `cookies()` from `next/headers` combined with `Response.redirect()` silently drops Set-Cookie headers from the redirect response. Use `NextResponse.redirect()` with `response.cookies.set()` instead to ensure cookies are included in redirect responses.
 - In this codebase's Next.js version, `revalidateTag` must be called with a second argument (for example `{ expire: 0 }`); single-argument calls fail typecheck.
-- For Workflow DevKit discovery in Next.js, ensure workflow files live in scanned directories (for this app, `app/`), otherwise manifests can show steps but `0 workflows` and `start()` will not run durable workflows.
+- For Workflow SDK discovery in Next.js, ensure workflow files live in scanned directories (for this app, `app/`), otherwise manifests can show steps but `0 workflows` and `start()` will not run durable workflows.
 - Server-side optimistic chat route lookup must allow realistic persistence latency (multi-second retry window), otherwise `/sessions/[sessionId]/chats/[chatId]` can redirect away before chat creation finishes.
 
 ## Sandbox Lifecycle