Skip to content

Connector guide reads Saturday Connector; CIMD auth rule matches #1814 - #69

Open
DrAlexHarrison wants to merge 2 commits into
mainfrom
assistantconnector
Open

DrAlexHarrison wants to merge 2 commits into
mainfrom
assistantconnector

Conversation

@DrAlexHarrison

@DrAlexHarrison DrAlexHarrison commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

docs.saturday.fit/guides/coach-connector is the documentation URL in Saturday's Claude directory submission (and later ChatGPT's), and it was titled "Claude Connector". It now reads "Saturday Connector". The URL is unchanged, so links keep working.

Changes

  • Guide title and sidebar: "Claude Connector" to "Saturday Connector". Consent and tool text say "the assistant" where they said "Claude"; Claude stays the one assistant the guide tells you to connect.
  • Link text on 7 other pages and llms.txt: "Claude connector" to "Saturday connector". Behavior statements that hold only for Claude's connection (list_athletes returns the athlete alone, product tools resolve the athlete) say "the Saturday connector in Claude".
  • guides/oauth2.mdx CIMD rule rewritten to the rule fuel-backend #1814 enforces at c025d70c: the listed auth methods must include none; a token_endpoint_auth_method outside the list, or a shared-secret method in either field, is refused. The old text said private_key_jwt clients are unsupported, which stops being true when #1814 deploys. CIMD selection names Claude and ChatGPT, true once #1814 deploys.
  • guides/mcp-integration.mdx: every tool carries openWorldHint (#1814).

No ChatGPT connect instructions yet. ChatGPT can sign in once #1814 deploys, but its tokens map to partner cimd-chatgpt.com, and only partner claude is routed to the athlete's own account (pkg/api isConsumerRequest), so its tools would not read the athlete's data. The ChatGPT line returns once fuel-backend #1831 (that routing, in review) is deployed.

Merge after #1814 is live in prod (the CIMD rule describes #1814's behavior).

Depends-On: SaturdayInc/fuel-backend#1814

Local checks: check-docs-drift.py --backend (against #1814's head) clean, check-app-claims.py clean, check-engine-constants.py clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WLJJumrUazi2upUSsmE9E1

The connector guide was titled and written for Claude alone. It is now
the Saturday Connector, with connect steps for Claude and for ChatGPT
Business, Enterprise and Edu workspaces, and the other pages link it by
that name. The CIMD rule now reads as fuel-backend #1814 enforces it:
the client's listed auth methods must include none.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WLJJumrUazi2upUSsmE9E1

Ci-From: amac
Ci-Session: 37bd0332-516c-4c68-b023-f153d13609b1
… data; CIMD rule matches #1814's final head

ChatGPT can sign in once fuel-backend #1814 deploys, but its tokens map to
partner cimd-chatgpt.com, and only partner "claude" is routed to the
athlete's own account (pkg/api isConsumerRequest). Its tools would read
the partner namespace, so "the assistant can read and write that
athlete's Saturday data" and "never on which assistant connects" are
untrue for ChatGPT. The ChatGPT connect line and mentions come out; the
Saturday Connector naming stays.

- oauth2: a token_endpoint_auth_method outside the listed methods, or a
  shared-secret method in either field, is refused (#1814 at c025d70c).
- mcp-integration: openWorldHint is on every tool since #1814.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WLJJumrUazi2upUSsmE9E1

Ci-From: amac
Ci-Session: 37bd0332-516c-4c68-b023-f153d13609b1
@DrAlexHarrison DrAlexHarrison changed the title Connector guide covers Claude and ChatGPT; CIMD auth rule matches #1814 Connector guide reads Saturday Connector; CIMD auth rule matches #1814 Oct 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant