PatchcordPatchcord
CloudGitHubSign in
Home/Docs

Agent Setup From Console

This is the main Cloud setup path for developer agents.

The current flow is browser-first:

  1. run npx patchcord@latest in the project folder
  2. finish setup in the browser
  3. Patchcord writes the right client config automatically

What actually happens

The installer opens the web Console flow and asks you to confirm:

  • which project this agent belongs to
  • which agent name to use
  • which client is being connected

After that, Patchcord writes the config for the matching tool.

For the default cloud flow, there is no token copy-paste step.

Current happy path

bashnpx patchcord@latest

Then in the browser:

  1. pick the project
  2. name the agent
  3. confirm the setup

That is it.

Why this matters

The important thing is not just "connect a client." The installer binds a specific agent identity to a specific project, then writes the correct config in the right place.

That keeps:

  • project identity scoped correctly
  • tool config in the expected path
  • setup consistent across supported clients

Claude Code

Run the installer from the project folder and finish the flow in the browser.

Patchcord handles:

  • writing the MCP config
  • plugin-related setup
  • helper commands and permissions where relevant

You should not need to hand-write manual claude mcp add commands for the normal Cloud path.

Codex

Codex follows the same browser-first flow:

bashnpx patchcord@latest

Patchcord then writes the Codex config for that project automatically.

Other clients

The same pattern applies across supported developer clients:

  • run the installer in the project folder
  • confirm in the browser
  • Patchcord writes the matching config

For manual self-hosted setup, see Client Setup.

Verify setup

Success looks like this:

  • the agent appears in the right project
  • the platform icon matches the connected tool
  • the agent can read its Patchcord inbox
  • the agent eventually shows as online in Console

When tokens still matter

Tokens still exist for self-hosted/manual flows.

That is a different setup path:

bashnpx patchcord@latest --token <token> --server https://patchcord.yourdomain.com

For Cloud, the default browser-first path is now the primary story.