> ## Documentation Index > Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # OrgX AI Toolkit Launch > Launch thread, positioning brief, and demo script for the OrgX AI Toolkit announcement. ## Headline Positioning **OrgX makes every AI tool you already use a first-class interface to your organization's continuity.** Not another chat wrapper. Not a separate platform to learn. OrgX meets developers and operators where they already are — Claude, Cursor, Codex, VS Code, ChatGPT, Gemini CLI — and turns those tools into a unified window into your organization's initiatives, decisions, and execution history. *** ## Twitter/X Launch Thread **Tweet 1 — Hook** > You switch between Claude, Cursor, and ChatGPT all day. > > Every context switch is a memory wipe. > > What was the decision on the auth refactor? Which agent is running the launch campaign? Did that artifact ship? > > Nobody knows. You start explaining from scratch. Again. *** **Tweet 2 — Solution** > Introducing the OrgX AI Toolkit. > > One command connects OrgX to every AI client you already use: > > `npx @useorgx/wizard@latest setup` > > It detects Claude, Cursor, Codex, VS Code, Windsurf, ChatGPT — and wires them all in automatically. > > Your org's context. Every tool. Zero config. *** **Tweet 3 — What You Get** > Once connected, your AI clients can actually do things: > > → Decisions flow through (approve in Claude, it's done) > → Artifacts track to initiatives, not lost in chats > → Org memory persists across every client > → Agents pick up where you left off, regardless of which tool you're in > > Continuity. That's the word. Your organization finally has it. *** **Tweet 4 — Technical Proof** > Under the hood: > > → MCP-native organizational memory and execution tools, all documented > → `validate_scaffold` before any plan executes > → OAuth auto-update across clients > → `orgx_recommend` grounds every session in real context > → Works with remote MCP or the OpenClaw local bridge > > Built for developers who want their AI tools to actually know what's going on. *** **Tweet 5 — CTA** > The OrgX AI Toolkit is free to connect. > > → docs: docs.useorgx.com/docs/guides/toolkit > → one command: `npx @useorgx/wizard@latest setup` > > Takes 2 minutes. Works in every client you already use. > > Ship with continuity. *** ## Demo Video Script — 90 Seconds **Title card**: "OrgX AI Toolkit — Connect in 90 seconds" *** **\[0:00–0:12] — The problem (text overlay on split screen)** Show Claude on the left, Cursor on the right. User asks about "the auth refactor decision" in both. Both say they don't know. *Voiceover*: "Every AI client you open starts from zero. Context lives in chats, not your organization." *** **\[0:12–0:28] — Wizard CLI setup** Terminal. Run: ```bash theme={"dark"} npx @useorgx/wizard@latest setup ``` Watch it detect Claude, Cursor, VS Code. OAuth completes in browser. Config files written automatically. *Voiceover*: "One command. OrgX detects every client you have installed and wires them in." *** **\[0:28–0:50] — Scaffold initiative in Cursor** In Cursor's agent panel, type: "Scaffold a launch initiative for the Q2 campaign." `scaffold_initiative` executes. Initiative appears in OrgX Mission Control simultaneously. *Voiceover*: "Scaffold an initiative from Cursor. It's live in OrgX instantly." *** **\[0:50–1:10] — Claude approves a decision** Switch to Claude. A pending decision surfaces: "Approve copy direction for Q2 campaign." User approves in Claude. In Mission Control, the decision flips to approved and an artifact begins generating. *Voiceover*: "A decision surfaces in Claude. One approval — the artifact starts shipping." *** **\[1:10–1:25] — Artifact ships, visible everywhere** The artifact appears in Mission Control. Switch back to Cursor — `orgx_search` finds the artifact in context. *Voiceover*: "The artifact tracks to the initiative. Query it from any client. Context never resets." *** **\[1:25–1:30] — End card** > OrgX AI Toolkit > docs.useorgx.com/docs/guides/toolkit > `npx @useorgx/wizard@latest setup` *** ## Key Messaging Pillars ### Pillar 1: Toolkit, Not Platform The "AI chief of staff" framing positions OrgX as something you have to learn and manage on top of your existing tools. It implies another interface, another mental model, another login. The AI Toolkit framing inverts this entirely — OrgX is infrastructure that augments tools you already have open. This matters because developers aren't looking for a new place to do work; they're looking for their existing tools to stop losing context. The wizard CLI running in a terminal for 90 seconds is more compelling than a dashboard demo, because it speaks the language developers trust: install, configure, done. ### Pillar 2: Continuity Over Chat "AI chat wrapper" is the category everyone is running away from in 2025. Every product in this space is trying to distance itself from the perception of being a glorified ChatGPT skin. The OrgX framing of "organizational continuity" names the actual problem: not that AI isn't powerful, but that organizational memory doesn't persist across sessions, clients, or team members. Decisions made in Claude don't show up in Cursor. Artifacts built in one context vanish when the session ends. OrgX is the connective tissue — and naming it "continuity" makes the value self-evident to anyone who has lost a decision thread at 11pm. ### Pillar 3: The Tool Surface Is a Proof Point, Not a Feature List The MCP tool surface shouldn't be buried in API docs — it's a credibility signal. When a developer sees `orgx_decide`, `orgx_search`, `orgx_decide`, `orgx_spawn`, `orgx_recommend`, `validate_scaffold`, `orgx_recommend`, `batch_create_entities`, and `orgx_spawn` in a single surface, they recognize that this isn't a toy integration. It's an opinionated execution system that has thought about organizational memory, initiative lifecycles, decision routing, artifact recall, and agent dispatch as distinct, composable concerns. The "chief of staff" metaphor collapses all of this into a single fuzzy role. The toolkit metaphor makes it clear that OrgX is infrastructure with depth, not a persona with vibes.