The Harness sign-in section on Settings → Agent profiles shows every entry in the credential-bindings document. On the live instance that is two forge bindings, shown as "Not set up". The same document backs the org Credential bindings page ("Service credentials granted to agent identities"). A harness is never given a forge credential (kit.forgeServices), so these rows can't be signed in from the setup terminal and suggest something is missing when nothing is.
Wanted
The harness table lists only bindings for services a configured Kit profile declares in credential@1, or the two uses get separate documents.
Done when
With no Kit profile, the harness section shows no bindings. With the Claude Code Kit, it shows the anthropic service only.
## Problem
The Harness sign-in section on Settings → Agent profiles shows every entry in the `credential-bindings` document. On the live instance that is two forge bindings, shown as "Not set up". The same document backs the org Credential bindings page ("Service credentials granted to agent identities"). A harness is never given a forge credential (`kit.forgeServices`), so these rows can't be signed in from the setup terminal and suggest something is missing when nothing is.
## Wanted
The harness table lists only bindings for services a configured Kit profile declares in `credential@1`, or the two uses get separate documents.
## Done when
With no Kit profile, the harness section shows no bindings. With the Claude Code Kit, it shows the `anthropic` service only.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The Harness sign-in section on Settings → Agent profiles shows every entry in the
credential-bindingsdocument. On the live instance that is two forge bindings, shown as "Not set up". The same document backs the org Credential bindings page ("Service credentials granted to agent identities"). A harness is never given a forge credential (kit.forgeServices), so these rows can't be signed in from the setup terminal and suggest something is missing when nothing is.Wanted
The harness table lists only bindings for services a configured Kit profile declares in
credential@1, or the two uses get separate documents.Done when
With no Kit profile, the harness section shows no bindings. With the Claude Code Kit, it shows the
anthropicservice only.Superseded by #1877: the Harness sign-in section is deleted along with Kit support.
Generated by Claude Code