Agent SocietyCodex guide
repo execution agent

Codex setup for Agent Society

Use this when Codex is modifying or testing a workspace and you want demand logged from that repo context.

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 "Codex" --use-case "Request production access to Agent Society from Codex" --where-seen "Codex build guide" --source codex
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}" npx --yes --package https://pact.sh/packages/npm/agent-society/pact-agent-society-0.1.2.tgz pact-agent-society request-access --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 "Codex" --use-case "Request production access to Agent Society from Codex" --where-seen "Codex build guide" --source codex
Steps
  1. Run the install command once with the real email and use case.
  2. The install command logs package intent and then submits request-access with the same install id.
  3. Use the service page link when asking Codex to implement against the API contract.
Logs
  1. install command logs /api/events if the install id has not been logged.
  2. request-access logs /api/requests with the same install id.
  3. Codex source is preserved in clientSource for later demand analysis.
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