Update AI Workspace documentation for July 2026 release - #359
Conversation
Thushani-Jayasekera
commented
Jul 23, 2026
- Updated last_updated dates across multiple files to reflect the new release date of July 23, 2026.
- Revised setup instructions in "Getting Started" and "Setting Up AI Gateways" to point to version 1.0.0-beta for AI Workspace and 1.2.0-beta for AI Gateway.
- Enhanced the "Overview" and "Authentication" sections to clarify the shared configuration file and authentication modes.
- Added details on custom LLM provider templates and updated authentication type options in the LLM providers documentation.
- Included new sections on custom policies and configuration interpolation in the relevant documentation files.
- Updated last_updated dates across multiple files to reflect the new release date of July 23, 2026. - Revised setup instructions in "Getting Started" and "Setting Up AI Gateways" to point to version 1.0.0-beta for AI Workspace and 1.2.0-beta for AI Gateway. - Enhanced the "Overview" and "Authentication" sections to clarify the shared configuration file and authentication modes. - Added details on custom LLM provider templates and updated authentication type options in the LLM providers documentation. - Included new sections on custom policies and configuration interpolation in the relevant documentation files.
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
📝 WalkthroughWalkthroughThe documentation updates align AI Gateway installation instructions with Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Revised setup instructions in "Getting Started" to point to the new version 1.0.0-beta. - Added raw markdown tags in "Overview" for better formatting of configuration interpolation examples.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@en/docs/next/ai-workspace/authentication/asgardeo-setup.md`:
- Line 171: Update the claim-mapping documentation near the referenced sentence
to distinguish Asgardeo token mapper configuration from the two service mapping
tables in config.toml. State that only [ai_workspace.auth.claim_mappings] and
[platform_api.auth.claim_mappings] are defined in config.toml, while the token
mapper output is configured in Asgardeo, and retain consistent claim names
across all three locations.
In `@en/docs/next/ai-workspace/getting-started.md`:
- Line 22: Update the download and directory-change commands in the
getting-started setup flow to replace every 1.0.0-alpha2 artifact reference with
1.0.0-beta, including the additionally affected occurrence, so all commands
consistently target the documented beta release.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: db1ee9be-ae93-4b47-85f6-911541735961
📒 Files selected for processing (10)
en/docs/next/ai-workspace/ai-gateways/setting-up.mden/docs/next/ai-workspace/authentication/asgardeo-setup.mden/docs/next/ai-workspace/authentication/overview.mden/docs/next/ai-workspace/getting-started.mden/docs/next/ai-workspace/llm-providers/configure-provider.mden/docs/next/ai-workspace/llm-providers/manage-provider.mden/docs/next/ai-workspace/llm-providers/overview.mden/docs/next/ai-workspace/llm-proxies/manage-proxy.mden/docs/next/ai-workspace/overview.mden/docs/next/ai-workspace/policies/overview.md
…nt secret interpolation example
…entication images - Changed image paths in "Getting Started," "Asgardeo Setup," and "Overview" sections to point to the updated standalone AI Workspace directory. - Clarified claim mapping consistency in the "Asgardeo Setup" section.