@@ -1,7 +1,7 @@
 # Contributing to mindwire
 
-Mindwire is an open personal assistant and coding companion, with a native Apple client and shared agent runtime. Contributions to everyday workflows, clients, adapters, documentation,
-and infrastructure are welcome.
+Mindwire is an open-source SDK and runtime for adding native agent capabilities to products.
+Contributions to agent adapters, integrations, clients, documentation, and infrastructure are welcome.
 
 By participating you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md).
 
 
@@ -1,21 +1,71 @@
 # Mindwire
 
-**One agent. Bring your subscriptions.**
+**Your product. Powered by agents.**
 
-Mindwire is your personal agent for everyday work and coding. Bring your supported AI
-subscriptions, connect your computer, and put it to work from your Mac, iPhone or iPad.
+Turn your product into an advanced AI experience without rebuilding the agent layer.
+Mindwire lets you **white-label and customize leading agent harnesses** like Codex,
+Claude Code, and OpenCode through an open-source SDK and runtime.
 
-- **Get everyday work done.** Organize files, process data, prepare documents, and automate repetitive tasks.
-- **Build from anywhere.** Write and review code, manage projects, and use a full terminal.
-- **Keep work moving.** Start a task, close the app, and come back to the result while your computer stays online.
-- **Stay in control.** Follow progress, answer questions, and approve actions along the way.
-- **Work where you want.** Use your computer, a server, or a cloud workspace.
+Reuse their reasoning, planning, tool use, and execution. Add your tools, knowledge,
+instructions, and goals. Deliver the whole experience in your interface, under your brand.
 
-[Download for Mac](https://github.com/oblien/mindwire/releases/latest/download/Mindwire.dmg) ·
-[Get started](https://mindwire.sh/get-started) · [Documentation](https://mindwire.sh/docs) ·
-[Account & Cloud portal](https://console.mindwire.sh)
+[Website](https://mindwire.sh) · [Quickstart](https://mindwire.sh/docs/guides/quickstart) ·
+[Documentation](https://mindwire.sh/docs) · [TypeScript](packages/sdk) · [Go](packages/daemon/sdk)
 
-[Development](CONTRIBUTING.md) · [Runtime installation](https://mindwire.sh/docs/guides/destinations) ·
-[SaaS source deployment](docker/README.md)
+## Build your product. The agent layer is ready.
 
-Runtime and SDKs: Apache-2.0. Apple app: source-available. [License details](LICENSING.md).
+- **Adapt instead of rebuild.** Use native agent capabilities through one integration.
+  Mindwire handles connections, sessions, authentication, and event translation.
+- **Make it yours.** Connect product tools through MCP. Shape the work with your
+  context, instructions, skills, and goals. Keep your brand and interface.
+- **Turn conversations into working experiences.** Let users create interactive
+  lessons, build dashboards, or carry out tasks inside your product using its tools
+  and data. Add schedules and app triggers when you need automation.
+- **Stay in control.** Stream progress, handle supported approvals, and run on your
+  own infrastructure. Agent capabilities vary; see the [compatibility guide](packages/daemon/HARNESSES.md).
+
+![Leading agents connected through Mindwire to your brand, tools, knowledge, and goals, inside your AI-powered product.](docs/assets/agent-foundation.png)
+
+[See how Mindwire fits into your product →](https://mindwire.sh/#how-it-works)
+
+## Get started
+
+```sh
+npm install mindwire
+```
+
+[Authenticate your agent](https://mindwire.sh/docs/guides/authentication), then run on
+Node.js or Bun from a project containing `brief.md`. The SDK starts the local runtime.
+
+```ts
+import { Mindwire } from "mindwire";
+
+const mw = new Mindwire({ agent: "codex" });
+try {
+  const run = await mw.turn({
+    chatId: "launch",
+    cwd: process.cwd(),
+    message: "Build a website from brief.md, create campaign assets, and save a rollout plan.",
+  });
+  for await (const event of run) {
+    if (event.type === "text") process.stdout.write(event.text ?? "");
+  }
+  await run.wait();
+} finally {
+  await mw.close();
+}
+```
+
+Next: [connect your tools](https://mindwire.sh/docs/guides/mcp),
+[stream work into your UI](https://mindwire.sh/docs/guides/streaming), or use
+[Go](packages/daemon/sdk) / [REST](https://mindwire.sh/docs/reference/rest/turns-runs/post-turns).
+
+[Mindwire Cloud](https://mindwire.sh/cloud) provides optional hosting.
+The [Mindwire app](https://mindwire.sh/app) is a first-party client built on the same runtime.
+Neither is required for your product.
+
+## Contributing & license
+
+See [Contributing](CONTRIBUTING.md) for local development.
+The runtime, SDKs, website, and Console are **Apache-2.0**; the Apple app is
+**source-available**. [License details](LICENSING.md).
@@ -1,6 +1,6 @@
 # @mindwire/web
 
-Mindwire’s mobile product site and developer documentation. Built with Next.js App
+Mindwire’s SDK/runtime product site, app showcase, and developer documentation. Built with Next.js App
 Router, React, Tailwind CSS, and Fumadocs. The Node deployment uses Next’s
 `standalone` output.
 
@@ -28,8 +28,11 @@ are not used.
 
 ## Product pages
 
-- `/`: personal-bot hero, interactive everyday creations, General / Developer mode explorer, computer/phone
-  continuity, SDK showcase, questions and a download invitation.
+- `/`: developer positioning, an example product with embedded agent work, a white-label
+  configuration preview, custom tools/context/goals, automation, and SDK integration examples.
+- `/app/`: the first-party app showcase with a desktop/phone preview, shared review state,
+  General / Developer modes, everyday examples, continuity, and app setup/download links.
+- `/cloud/`: optional Cloud Computer hosting, its relationship to the runtime, and pricing/Console links.
 - `/get-started/`: app, computer/server/cloud and agent setup.
 - `/pricing/`: free own-computer runtime and monthly Mindwire Cloud Computer plans.
 - `/download/`: Mac and iOS app availability, CLI installation and release links.
@@ -46,14 +49,29 @@ Shared product URLs live in `lib/product.ts`. Product pages share the components
 and scoped styles in `components/landing/`. The changelog and sandboxing content
 retain `components/marketing/`; the docs theme stays in `app/globals.css`.
 
-The homepage uses Gellix, soft rounded surfaces, and the native app's peach, blue,
-and mint bot palette. `BotAvatar` adapts the native bean, robot, and sprout vectors.
+The site uses Gellix, soft rounded surfaces, and the shared peach, blue,
+and mint palette. Dark mode is the default; a saved light/dark preference is respected.
+Keep the homepage focused on adapting leading agents to a developer's own product. The centered
+hero uses tool and provider illustrations; its preview demonstrates an agent feature in a product,
+not a bot directory or personal chat flow. Avoid decorative status dots, dotted backgrounds,
+numbered section badges, and widely spaced uppercase labels. App modes and everyday task demos
+belong on `/app/`, which has no SDK promotional section. `BotAvatar` remains in app-specific art.
+Separate homepage containers with contrasting surface colors instead of nested borders.
+Claude and OpenCode use SVG images that preserve their artwork; don't recolor them with CSS masks.
+The hero shows an agent creating a complete project inside a product: a brief becomes a working
+landing page, campaign poster and announcement, and an assigned launch plan. Visitors can try the
+page, copy the announcement, complete tasks, and download self-contained HTML, SVG, and CSV outputs.
+The build is illustrative; the outputs are usable local examples. Provider choice stays outside the
+product UI. Campaign artwork and its generation prompt are in `public/images/launch-demo/`.
+The white-label section pairs a customization rail with an editable product feature preview.
+Automation uses connected nodes, context/tool inputs, a review branch, and an inspectable result;
+connections follow the responsive node layout. Keep its canvas free of decorative dot grids.
 `LandingNav` and `LandingFooter` are shared by marketing routes without changing the documentation shell.
 The previews use fictional example content and local interactions only: changing
-bots, inspecting their memory and instructions, checking tasks, comparing ideas,
-switching bookshelves, trying everyday tools, and exploring General / Developer views. They never contact
+project creation, working artifact previews, downloads, tasks, and agent choices, editing brand/tools/instructions/context/goals, stepping through
+automation and review, switching bookshelves, and exploring General / Developer views. They never contact
 an agent or touch an account. Mode switching preserves the example app's state.
-The personal secretary example shares one component between the homepage and the
+The personal secretary example shares one component between the app page and the
 use-case directory. Check a priority, open the meeting brief, or switch with arrow keys.
 Use-case prompts start from information the user supplies and tools they connect;
 they do not imply built-in email or calendar integrations.
@@ -120,3 +138,13 @@ selection when changing its presentation.
 Verify public pages, guide and API docs, search, and 404 pages in both themes at
 desktop and phone widths. Workspace options on `/sandboxing/` are a local preview;
 they never create a computer or change an account.
+
+### Positioning
+
+Mindwire is the SDK and runtime for putting supported agents inside an existing product. Lead with
+a concrete task and the integration surface: execution, streaming, sessions, and supported approvals.
+The app is a first-party client; Cloud is optional hosting. Neither is required for an SDK integration.
+General mode remains an approachable app experience alongside Developer mode. Saved bot profiles
+remain an optional runtime capability, not a prerequisite or the primary marketing promise. Avoid
+claims of universal app access, identical provider capabilities, bundled model usage, or unimplemented
+managed orchestration. Keep Cloud prices sourced from the existing catalog.
@@ -0,0 +1,50 @@
+import type { Metadata } from "next";
+import Link from "next/link";
+import { ArrowDown, ArrowUpRight, Folder, Radio, ShieldCheck, Smartphone } from "lucide-react";
+import AppWorkspacePreview from "@/components/landing/AppWorkspacePreview";
+import ModeExplorer from "@/components/landing/ModeExplorer";
+import PersonalSection from "@/components/landing/PersonalSection";
+import ContinuitySection from "@/components/landing/ContinuitySection";
+import FinalInvite from "@/components/landing/FinalInvite";
+import Questions from "@/components/landing/Questions";
+import base from "@/components/landing/landing.module.css";
+import product from "@/components/landing/product.module.css";
+import styles from "@/components/landing/app-showcase.module.css";
+
+export const metadata: Metadata = {
+  title: "Mindwire App — Your work, with you everywhere",
+  description: "A workspace for your agents, files, and ideas. Work from Mac, iPhone, or iPad, follow progress, and review the next step in General or Developer mode.",
+  alternates: { canonical: "/app/" },
+};
+
+export default function AppPage() {
+  return <div className={base.landing}>
+    <section className={styles.hero} aria-labelledby="app-title">
+      <div className={styles.intro}>
+        <span className={styles.label}><Smartphone size={15} />The Mindwire App · Mac, iPhone & iPad</span>
+        <h1 id="app-title">Your work.<br /><em>With you, everywhere.</em></h1>
+        <p>A home for your agents, files, and ideas. Start something at your desk, follow its progress, and pick up the next step from your phone.</p>
+        <div className={styles.actions}><Link href="/download" className={base.primaryButton}>Get the app <ArrowUpRight size={17} /></Link><Link href="#modes" className={base.secondaryButton}>Find your way to work <ArrowDown size={16} /></Link></div>
+      </div>
+      <AppWorkspacePreview />
+    </section>
+    <section className={styles.benefits} aria-label="What the Mindwire app brings together">
+      <div><Radio size={21} /><h2>Know where the work stands.</h2><p>Follow agent progress and tool activity in the same place as the conversation.</p></div>
+      <div><Folder size={21} /><h2>Keep the context close.</h2><p>Your projects, source files, and finished results stay part of the workspace.</p></div>
+      <div><ShieldCheck size={21} /><h2>Stay in the decisions.</h2><p>Review the work and respond to supported questions and approvals across devices.</p></div>
+    </section>
+    <ModeExplorer />
+    <PersonalSection />
+    <ContinuitySection />
+    <section className={`${product.section} ${product.faqSection}`} aria-labelledby="app-questions">
+      <div className={`${product.sectionCopy} ${styles.faqHeading}`}><span className={product.eyebrow}>Make yourself at home</span><h2 id="app-questions">A few things<br /><em>before you start.</em></h2><p>Choose a computer, connect a supported agent, and start with something you need done.</p></div>
+      <Questions items={[
+        { question: "Which mode should I use?", answer: "General mode keeps conversations, files, and finished results up front. Developer mode exposes projects, code changes, Git, and the terminal. Switch views as the work changes." },
+        { question: "Does the work run on my phone?", answer: "The work runs on a connected computer: your Mac, a server, or an optional Cloud Computer. Your phone lets you follow progress and interact with the workspace. The host needs to stay running while tasks execute." },
+        { question: "Can I use my existing agent account?", answer: "Connect an account or API key supported by your selected agent. Available authentication methods, provider terms, limits, and usage charges still apply." },
+        { question: "Where can I get the app?", answer: <>See <Link href="/download">downloads</Link> for current Mac and iOS availability, then follow the <Link href="/get-started">app setup guide</Link> to connect your computer and agent.</> },
+      ]} />
+    </section>
+    <FinalInvite audience="app" />
+  </div>;
+}
@@ -0,0 +1,32 @@
+import type { Metadata } from "next";
+import Link from "next/link";
+import { ArrowUpRight, Cloud, Folder, Laptop, Server } from "lucide-react";
+import Questions from "@/components/landing/Questions";
+import { cloudDashboardUrl } from "@/lib/product";
+import base from "@/components/landing/landing.module.css";
+import product from "@/components/landing/product.module.css";
+import styles from "@/components/landing/platform.module.css";
+
+export const metadata: Metadata = {
+  title: "Mindwire Cloud — A computer for your agent work",
+  description: "Optional monthly Cloud Computers for the Mindwire runtime. Keep files and projects on an online host, with your agent account and model usage separate.",
+  alternates: { canonical: "/cloud/" },
+};
+
+export default function CloudPage() {
+  return <div className={base.landing}>
+    <header className={product.pageHero}><span className={product.eyebrow}>Mindwire Cloud · Optional hosting</span><h1>A computer for<br /><em>the work ahead.</em></h1><p>Give your agent tasks an online workspace with the files and tools they need. Use a monthly Cloud Computer when you want work to run beyond your own laptop.</p><div className={styles.actions} style={{ justifyContent: "center" }}><Link href="/pricing#cloud-plans" className={base.primaryButton}>See Cloud plans <ArrowUpRight size={17} /></Link><a href={cloudDashboardUrl} className={base.secondaryButton}>Open Console <ArrowUpRight size={17} /></a></div></header>
+    <section className={styles.cloudSteps} aria-labelledby="cloud-capabilities"><h2 id="cloud-capabilities">A host for the same runtime.</h2><div className={styles.productGrid}>
+      <article><span className={styles.productIcon}><Server size={25} /></span><h3>Run your workspace.</h3><p>Connect a supported agent account and work with its tools on your Cloud Computer. Agent usage remains separate from hosting.</p></article>
+      <article><span className={styles.productIcon} data-tone="mint"><Folder size={25} /></span><h3>Keep files together.</h3><p>Keep projects and output on the computer that runs the task. Manage your computer and subscription through Console.</p></article>
+      <article><span className={styles.productIcon} data-tone="peach"><Laptop size={25} /></span><h3>Use your preferred client.</h3><p>Connect through the Mindwire app or supported SDK destinations. Your client can disconnect while work continues on the running host.</p></article>
+    </div></section>
+    <section className={styles.hosts} aria-labelledby="cloud-choice"><div><Cloud size={29} /><h2 id="cloud-choice">Cloud is one way to run Mindwire.</h2><p>The SDK and runtime also work locally, on a server you manage, and in supported Docker environments. Choose the host that fits your application.</p></div><div className={styles.hostLinks}><Link href="/docs/guides/destinations">Compare runtime destinations <ArrowUpRight size={16} /></Link><Link href="/pricing">Understand hosting and AI costs <ArrowUpRight size={16} /></Link></div></section>
+    <section className={`${product.section} ${product.faqSection}`} aria-labelledby="cloud-questions"><div className={product.sectionCopy}><span className={product.eyebrow}>Before you choose</span><h2 id="cloud-questions">Hosting, with<br /><em>clear boundaries.</em></h2></div><Questions items={[
+      { question: "Is this a model subscription?", answer: "No. A Cloud plan provides a computer. Use an account or API key supported by your chosen agent; provider limits, terms, and usage charges apply separately." },
+      { question: "What am I paying for?", answer: <>Each computer has its own monthly plan for the listed CPU, memory, and included storage. Check <Link href="/pricing">pricing</Link> and checkout for availability and any separate transfer, storage, or backup terms.</> },
+      { question: "Can I use my own infrastructure instead?", answer: "Yes. Mindwire’s open-source SDK and runtime can run on hardware and infrastructure you manage. A Cloud subscription is optional." },
+      { question: "Does my phone need to stay open?", answer: "No. Execution happens on the computer. Tasks and configured schedules can continue while the client is closed, as long as the host is running and the work is not waiting for input." },
+    ]} /></section>
+  </div>;
+}