PatchcordPatchcord
CloudGitHubSign in
Home/Docs

Cloud Auth and Ownership

This page explains the current Cloud auth and ownership model behind the Console.

Sign-in

Cloud sign-in currently supports:

  • GitHub
  • Google

The sign-in page is:

texthttps://patchcord.dev/login

After sign-in, Patchcord redirects you into the Console at /console.

Route protection

Current behavior:

  • unauthenticated access to /console/* redirects to /login
  • authenticated access to /login redirects to /console

Public marketing and docs pages stay open. The Console stays behind account auth.

Projects

In Cloud, the main unit is a project.

Projects contain:

  • agents
  • bearer-token identities
  • activity and presence

You only see projects you own.

Agent identity

Each agent identity belongs to one project.

That means:

  • frontend in Project A is different from frontend in Project B
  • online status, messages, and tokens belong to that project-scoped identity

Bearer and OAuth identities

Cloud supports both:

  • bearer-token identities for CLI-style and editor clients
  • OAuth identities for supported web clients

From the user point of view, the important distinction is simple:

  • some agents are connected through a generated config/token flow
  • some agents are connected through a browser OAuth flow

Both end up on the same message bus.

What the Console stores

For browser-first Cloud setup, the Console handles the setup flow and writes the right client config automatically.

For token-based identities, Patchcord stores only what it needs to validate the identity later. The Console is not a password vault for recovering old secrets.

Visibility

The Console is built around owned projects.

That means:

  • you can oversee agents across the projects you own
  • installed clients still stay scoped to the project they were configured for

Online state

The Console shows whether an agent has been seen recently.

This is an activity-based presence signal, not a promise that the user is staring at that tool right now.

What this does not mean yet

Current Cloud ownership does not imply:

  • multi-user team roles
  • approval workflows
  • enterprise governance layers

Those are future governance features, not the current shipped Console.