Skip to main content
For ChatGPT and Grok, see the ChatGPT hiring connection and Grok hiring connection. The public OAuth endpoint is enabled for testing; account connection and end-to-end hiring are still being verified.

Local agents

The simplest local setup is to paste set up https://crowdlisten.com/SKILL.md into your agent. To install manually, use the instructions for your client below. Requires Node.js 22+. The standard package includes the native record tools and the authenticated expert, context and video tools; there is no second expert connector to install.
Register CrowdListen through Codex’s MCP CLI:
Complete browser sign-in, then start a new Codex session. If a crowdlisten entry already exists, inspect it before replacing it.

Check from the connected local client

Confirm recall, analyze, and ingest plus the hosted tools expert_offering, expert_result_review, context_task, and video_readiness are available. Read their current schemas, then run:
These reads do not start a model, collect sources, or spend credits. If only the three native tools appear, check the server and client type before trying to repair setup: the legacy remote endpoint does not include expert tools. For the standard local package, inspect the configured version, sign-in, and schema discovery. A new API tool can appear without another package update. Choose an authorized workspace before reading private expertise.

Troubleshooting

  • Old package remains configured: inspect the client entry. The targeted Codex installer preserves an existing managed entry, including its older version and custom settings. Review and update that entry to @crowdlisten/harness@2.4.3, preserving unrelated settings, then restart and verify from the client.
  • Only native tools appear: inspect which server you connected. The legacy remote endpoint exposes only native tools; repeating login there will not add expert tools. For a supported local client, check sign-in, the configured package version, and retry schema discovery. For a hosted assistant, use the read-only browser-approved account connection above.
  • No tools after setup: restart the client, inspect its MCP settings, and confirm Node.js 22+ is on its path.
  • Another account appears: website and agent sessions are separate. Check the identity returned by recall({ mode: "connection" }) and the authorized workspace before opening private work. If this is your own account, run the browser login command again and select it. An outside reviewer should receive an owner-approved share or export instead of switching into the owner’s account.
  • Existing configuration conflict: inspect the entry and preserve unrelated servers. The targeted harness installer, crowdlisten-harness setup --agent codex (or claude-code or cursor), reports conflicts instead of silently replacing custom settings.
  • A method or task is unavailable: verify workspace membership and ownership. Signing in does not grant access to someone else’s private methods.

Save files after connecting

Ask your agent to save an agreed brief or selected Markdown file in your current workspace. You do not need another API key or an expert job. See the copyable Context example. context_items reads saved files; context_save creates and updates them with version checks. Existing sessions may need a tool refresh or a new conversation to discover the updated schemas.