From ccf23c895278b3dadf7e0b27d3d1508b4414070b Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 17 Sep 2026 02:18:19 +0000 Subject: [PATCH] docs: name both Connect-an-Agent doors in three published pages Three published pages still routed readers to "Setup -> Connect an Agent", the one app a non-admin cannot open: SETUP_APP declares requiredPermissions: ['setup.access'], and the ruling that made the page reachable for every signed-in user landed as a second navigationContributions entry into the `account` app's grp_account_developer group (packages/mcp/src/connect-ui.ts), not as an ungating of Setup. - content/docs/api/index.mdx: a direct key-minting instruction -> names both doors, matching the wording already shipped in packages/mcp/README.md and content/docs/ai/connect-mcp.mdx. - content/docs/ai/agents.mdx: descriptive summary that defers step-by-step setup to /docs/ai/connect-mcp -> drops the "Setup -> " prefix only. - content/docs/getting-started/build-with-claude-code.mdx: the sentence's subject was "Admins", which a prefix drop cannot fix -> names both doors. Text only. No behaviour, no gate, no authorization change. Claude-Session: https://claude.ai/code/session_017ef78bLdybu3AffehKkhfk Co-authored-by: Claude --- content/docs/ai/agents.mdx | 2 +- content/docs/api/index.mdx | 6 ++++-- content/docs/getting-started/build-with-claude-code.mdx | 5 +++-- 3 files changed, 8 insertions(+), 5 deletions(-) diff --git a/content/docs/ai/agents.mdx b/content/docs/ai/agents.mdx index 9750c3bb0a9..e8327318a2b 100644 --- a/content/docs/ai/agents.mdx +++ b/content/docs/ai/agents.mdx @@ -52,7 +52,7 @@ architecture. Every deployment serves MCP at `/api/v1/mcp` by default (a core platform capability — set `OS_MCP_SERVER_ENABLED=false` to opt out), with two authentication tracks: The in-product entry point is the -**Setup → Connect an Agent** page: per-client connect snippets, the portable +**Connect an Agent** page: per-client connect snippets, the portable SKILL.md download (`GET /api/v1/mcp/skill`), and API-key minting. - **OAuth 2.1 (interactive clients — recommended).** Each deployment is its diff --git a/content/docs/api/index.mdx b/content/docs/api/index.mdx index 6e2b2369237..3e6f20671e3 100644 --- a/content/docs/api/index.mdx +++ b/content/docs/api/index.mdx @@ -65,8 +65,10 @@ permission model grants anonymous users. Two ways to authenticate: `curl -c cookies.txt` / `-b cookies.txt`. On a fresh dev database the seeded admin is `admin@objectos.ai` / `admin123`. - **API key** (scripts, CI, headless agents): mint one with `POST /api/v1/keys` - (the key is shown once), or from **Setup → Connect an Agent** in the Console. - Send it as `x-api-key: osk_…` or `Authorization: Bearer osk_…`. + (the key is shown once), or from the **Connect an Agent** page in the Console + — **Account → Developer** for any signed-in user, **Setup → Connect an Agent** + for platform admins. Send it as `x-api-key: osk_…` or + `Authorization: Bearer osk_…`. See [Authentication](/docs/permissions/authentication) for the full identity surface (OAuth flows, sessions, providers) and diff --git a/content/docs/getting-started/build-with-claude-code.mdx b/content/docs/getting-started/build-with-claude-code.mdx index ca967711f9f..d69897d52cd 100644 --- a/content/docs/getting-started/build-with-claude-code.mdx +++ b/content/docs/getting-started/build-with-claude-code.mdx @@ -431,8 +431,9 @@ command (one plugin serves every deployment; the URL is the only input): claude plugin marketplace add objectstack-ai/claude-plugin ``` -Admins find every client's copy-paste-ready connect snippet — plus the SKILL.md -download and API-key minting — on the **Setup → Connect an Agent** page. +Every client's copy-paste-ready connect snippet — plus the SKILL.md download and +API-key minting — lives on the **Connect an Agent** page: **Account → Developer** +for any signed-in user, **Setup → Connect an Agent** for platform admins. For headless callers (CI, scripts), mint an API key instead (`POST /api/v1/keys`, shown once) and pass it as a header: