Carry work across agents · Integrations

Enter through the tools you already use.

Without it, the tool switch becomes another manual step and the record arrives late.

OrgX connects through client setup, hosted OAuth MCP, REST, and webhooks. Each recorded session retains its client and workspace boundary.

Connect your first client Read the connection guide
Start where the work happens

Connect a client, then send the first outcome.

Choose a supported client to see the current setup path and the first bounded prompt.

Paste into Claude Code

Set up OrgX in Claude Code

01npx @useorgx/wizard@latest setup

02The agent pauses when browser authentication needs you.

03Call orgx_bootstrap, report the active workspace, and stop.

What changes in the work

The first session starts bounded.

01

One setup path

The agent handles setup and pauses when browser authentication needs you.

Claude Code and Cursor use the OrgX setup wizard.
02

Workspace authority is explicit

The client reports the active workspace before changing work.

The first bootstrap stops before any creation or mutation.
03

The first prompt starts with an outcome

The record begins with intent, not an unscoped agent session.

Irreversible actions stay behind operator approval.
What OrgX records

The next session receives objects, not a summary.

Client
The tool where the work happened.
Session
The bounded record written by that tool.
Authority
The workspace and scope granted to it.
NextContinue the product storyConsequential judgment reaches you exactly once.
One real initiative

Start with the outcome. Keep the record.

Connect your first client Read the connection guide
Integrations | OrgX