Skip to content

Document OAuth organization hints - #3159

Open
sj26 wants to merge 2 commits into
mainfrom
amp/oauth-organization-hint
Open

Document OAuth organization hints#3159
sj26 wants to merge 2 commits into
mainfrom
amp/oauth-organization-hint

Conversation

@sj26

@sj26 sj26 commented Sep 2, 2026

Copy link
Copy Markdown
Member

Summary

Document how clients can preselect an organization during OAuth authorization:

  • Add organization and organization_uuid to the device authorization API reference.
  • Show bk auth login --device --org my-org for CLI device login.
  • Document organization query hints for the remote MCP server, including an Amp configuration example.
  • Clarify that organization values are preselection hints, not access controls, and users can still choose another available organization.

Related implementation:

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-01a06015-04b9-70ab-aaba-bc0e8736680f
Co-authored-by: Samuel Cochran <sj26@sj26.com>
@sj26
sj26 requested a review from a team as a code owner September 2, 2026 03:58
@github-actions github-actions Bot added the api label Sep 2, 2026
@buildkite-systems

Copy link
Copy Markdown

@buildsworth-bk-app buildsworth-bk-app Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The OAuth hints align with the linked server and CLI implementations. I left one non-blocking comment about where the new MCP guidance sits in the page hierarchy.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 24126, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

About buildsworth

Model: gpt-5.6-sol with xhigh thinking.

How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.

Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):

  • L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
  • L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
  • L3 — High risk (auth, migrations, payments, secrets, perf-critical pipeline paths). Human review always required.

Comment thread pages/apis/mcp_server/remote/configuring_ai_tools.md Outdated
Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-01a06015-04b9-70ab-aaba-bc0e8736680f
Co-authored-by: Samuel Cochran <sj26@sj26.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants