Skip to content

[codex] correct auth user API example #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
charlesrhoward merged 1 commit into from
May 18, 2026
Merged

[codex] correct auth user API example #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions content/docs/web/api/working-requests.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,19 +53,23 @@ Representative response:
"github_state": "app_installed_with_synced_repos",
"github_installation_count": 2,
"github_covered_repo_count": 8,
"managed_access": {
"allowModels": true,
"allowSandboxes": false
"platform_access": {
"allowPlatformAi": true,
"allowPlatformSandbox": false
},
"vercel": {
"platformState": "ready",
"personalState": "linked",
"linkedProjectState": "repo",
"statusLabel": "Project metadata ready"
"statusLabel": "Platform ready"
}
}
}
```

Current API field names still use `platform_access` and `allowPlatform*`.
Treat those fields as the route's managed account-access flags.

Copy link
Copy Markdown

@mogplex mogplex Bot May 18, 2026

Choose a reason for hiding this comment

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

Suggestion: Prose note could imply upcoming deprecation

The sentence "Current API field names still use platform_access and allowPlatform*." uses "still use" in a way that implies a future rename is planned or in progress. A reader scanning the docs may reasonably conclude these field names are transitional and will change soon, and may write defensive code against that assumption.

If no rename is planned, consider replacing the note with something unambiguous, e.g.:

The managed account-access flags are exposed under platform_access with allowPlatformAi and allowPlatformSandbox sub-fields.

If a rename is planned, a brief note like "(these names will change in a future release)" would make the intent explicit.

Use this call to answer:

- is the caller authenticated?
Expand Down