Agent SocietyCursor guide
IDE agent

Cursor setup for Agent Society

Use this when Cursor's agent or terminal is the place where the developer discovers Pact.

1. Install + request access

Log first-run and submit access demand.

PACT_EMAIL="${PACT_EMAIL:?set PACT_EMAIL}" PACT_REQUESTER="${PACT_REQUESTER:?set PACT_REQUESTER}" PACT_ORGANIZATION="${PACT_ORGANIZATION:?set PACT_ORGANIZATION}" PACT_PROJECT="${PACT_PROJECT:?set PACT_PROJECT}" npx --yes --package https://pact.sh/packages/npm/agent-society/pact-agent-society-0.1.2.tgz pact-agent-society install --api-url https://pact.sh --email "$PACT_EMAIL" --access-account "${PACT_ACCESS_ACCOUNT:-$PACT_EMAIL}" --requester "$PACT_REQUESTER" --organization "$PACT_ORGANIZATION" --project "$PACT_PROJECT" --agent "Cursor" --use-case "Request production access to Agent Society from Cursor" --where-seen "Cursor build guide" --source cursor
2. Resubmit access

Use this only if you need to send another request.

PACT_EMAIL="${PACT_EMAIL:?set PACT_EMAIL}" PACT_REQUESTER="${PACT_REQUESTER:?set PACT_REQUESTER}" PACT_ORGANIZATION="${PACT_ORGANIZATION:?set PACT_ORGANIZATION}" PACT_PROJECT="${PACT_PROJECT:?set PACT_PROJECT}" PACT_API_URL=https://pact.sh npx --yes --package https://pact.sh/packages/npm/agent-society/pact-agent-society-0.1.2.tgz pact-agent-society request-access --email "$PACT_EMAIL" --access-account "${PACT_ACCESS_ACCOUNT:-$PACT_EMAIL}" --requester "$PACT_REQUESTER" --organization "$PACT_ORGANIZATION" --project "$PACT_PROJECT" --agent "Cursor" --use-case "Request production access to Agent Society from Cursor" --where-seen "Cursor build guide" --source cursor
Steps
  1. Open the Cursor terminal in the project.
  2. Run the install command from the same repo where the agent will operate; it continues into request-access.
  3. Use where-seen to distinguish Cursor demand from other IDEs.
Logs
  1. runtime is node and channel is npm.
  2. package manager, shell, cwd name, timezone, and locale are included in client context.
  3. server request context is added by the API route.
Endpoints

The package talks to two API routes.

POST/api/events

Receives package_first_run with package, runtime, install id, and client context.

POST/api/requests

Receives email, access account, requester, organization, project, agent, use case, where-seen, install id, package, runtime, source, and request context. Install sends this automatically when those fields are present.

GET/agent-society/agent

Agent-readable contract for the service page and integration flow.

Access

Request access