> ## 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.

# Product quickstart

> Connect one AI tool, confirm its workspace context, and create visible work.

This path is for people who want Claude, Cursor, Codex, ChatGPT, OpenClaw, or
another MCP client to work from shared OrgX context. If you are integrating an
application, use the [API quickstart](https://docs.useorgx.com/docs/api/quickstart.md).

## 1. Choose your path

* **See an example:** [Pick up where you left off](https://docs.useorgx.com/docs/guides/synthetic-data-trial.md) requires no installation.
* **Connect a browser tool:** use the [ChatGPT guide](https://docs.useorgx.com/docs/guides/chatgpt-integration.md) or the [Claude connector instructions](https://docs.useorgx.com/docs/guides/cursor-mcp-setup.md). No Node or local runner is required.
* **Connect a local tool:** review the [Wizard setup and capture choices](https://docs.useorgx.com/docs/guides/wizard-cli-onboarding.md), then run:

```bash theme={"dark"}
npx -y @useorgx/wizard@latest setup
```

The local Wizard requires Node 22 or newer. `@latest` can change: check the
installed version and `setup --help` before unattended setup. Start with one client.

## 2. Ask for your first useful result

Ask your connected client:

> Use OrgX to show my connected workspace and summarize what needs my attention. Include links to the records. Don't change anything.

You should see the workspace name, then the decisions and blocked work waiting
on you, each linked to its record. A new workspace may have nothing waiting
yet; that is still a working connection. If the answer never mentions OrgX,
start a new chat, name OrgX in the prompt, and reconnect from your tool's setup
page if it still cannot find OrgX.

> [accordion] Which OrgX tools answer this prompt
>
> Clients choose tools from what the connection lists. A profile that exposes
> `orgx_bootstrap` uses it to confirm the workspace. The public Claude Code
> plugin uses the status-only `claude-directory` profile and answers with
> `orgx_search` or `get_initiative_pulse` instead. Never require a tool absent
> from discovery.

## 3. Save one bounded draft, if your connection supports writes

Choose one outcome, a first deliverable, an owner, and an acceptance check.
Use [web onboarding](https://useorgx.com/onboarding) to review and save the plan,
or ask a write-capable client to create it using its discovered tools.
A status-only plugin can read the plan; operating access is a separate opt-in
connection. Review scopes and workspace access before granting writes.

A saved draft has not run. A started run has not completed. A receipt records
what happened; accepting an artifact is a separate human action.

## 4. Continue from the result

Open the returned initiative or artifact link in Mission Control. In a new
session, ask your selected client to retrieve that same record and explain the
next action. This tests continuity with an actual result rather than a setup badge.

> [card] [Connect a specific client](https://docs.useorgx.com/docs/guides/toolkit.md)
>
> Choose setup instructions for your client.

> [card] [Understand the work model](https://docs.useorgx.com/docs/concepts.md)
>
> Learn the six core concepts through one concrete workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.