Update Port AI documentation from closed beta to open beta using existing template

[Copilot]

User description

✅ Port AI Documentation Updated: Address Latest Feedback

Successfully addressed all feedback comments and updated AI interfaces documentation.

📋 Latest Changes Made

• Slack app updated: Now uses ClosedBetaFeatureNotice component with custom "slack-app" ID
• Removed "application basis" text: No longer mentions "Access is provided on an application basis"
• Added slack-app ID: Created new component that shows "We are not accepting new applications at the moment and will update once it moves to open beta"
• AI agents now open beta: Updated overview page and all references to reflect AI agents are in open beta
• Updated availability status: Overview now shows only Slack App in closed beta

🔄 Current Status Summary

Interface	Status	Template Used	Special Notes
Port AI Assistant	✅ Open Beta	BetaFeatureNotice (ai-form)	Form integration
Port AI Core	✅ Open Beta	BetaFeatureNotice (ai-form)	Form integration
Context Lake	✅ Open Beta	BetaFeatureNotice (ai-form)	Form integration
AI Chat Widget	✅ Open Beta	BetaFeatureNotice (ai-form)	Form integration
LLM Provider Management	✅ Open Beta	BetaFeatureNotice (ai-form)	Form integration
MCP Server	✅ Open Beta	Already open beta	No changes
AI Agents	✅ Open Beta	No template needed	Updated from closed beta
Slack App	🔒 Closed Beta	ClosedBetaFeatureNotice (slack-app)	Not accepting applications

🛠️ Technical Implementation

Updated Closed Beta Template:

• Removed "Access is provided on an application basis" text
• Added new "slack-app" ID with custom message: "We are not accepting new applications at the moment and will update once it moves to open beta"

Slack App Changes:

import ClosedBetaFeatureNotice from '/docs/generalTemplates/_closed_beta_feature_notice.md'

<ClosedBetaFeatureNotice id="slack-app" />

Overview Page Updates:

• Changed from "AI Agents and Slack App in closed beta" to "Slack App in closed beta"
• Removed all "Currently in closed beta" references for AI Agents
• Updated FAQ and availability status sections

🎯 Feedback Addressed

✅ Comment 2454060057: Slack app now uses ClosedBetaFeatureNotice component, removed "application basis" text, added "slack-app" ID with "We are not accepting..." message
✅ Comment 2454061459: AI agents are now correctly shown as open beta across all pages
✅ Comment 3368429630: All comments have been addressed

✅ Verification Completed

• Build Test: ✅ Successfully builds without errors
• Manual Testing: ✅ Local server verification completed
• Template Usage: ✅ Slack app uses proper ClosedBetaFeatureNotice component
• Visual Verification: ✅ Screenshots confirm proper rendering
• Consistency Check: ✅ AI agents now consistently shown as open beta

All feedback addressed and changes ready for production! 🚀

Original prompt

in the AI docs we state Port AI is in closed beta. we want to now update that Port AI is in open beta. As part of it, organizations who wants access can fill their details in this form. the link to the form is https://forms.gle/XtTR9R9pzo8tMYDT8
please note we should have some open beta component we can re-use across the pages, we might need to extend it a bit to include an optional text/link on how to join. see what we did in the past with the closed beta components.

Please also note that all Port AI interfaces featrues are in open beta BESIDES are Slack app which is in closed beta. we can state that we don't accept new applications at the moment, and wil update once it move to open beta.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

PR Type

Enhancement, Documentation

---

Description

• Transition Port AI from closed beta to open beta with form-based access

• Create new open beta template with access form link

• Update Slack App to closed beta with restricted access message

• Remove "closed beta" status from AI Agents, making them open beta

• Consolidate beta feature notices across all AI interface documentation

---

Diagram Walkthrough

flowchart LR
  A["Port AI Interfaces"] --> B["Open Beta Features"]
  A --> C["Closed Beta Features"]
  B --> D["AI Assistant<br/>AI Core<br/>Context Lake<br/>Chat Widget<br/>LLM Management<br/>MCP Server<br/>AI Agents"]
  C --> E["Slack App<br/>with restricted access"]
  D --> F["BetaFeatureNotice<br/>with form link"]
  E --> G["ClosedBetaFeatureNotice<br/>with custom message"]

Loading

File Walkthrough

	Relevant files
Enhancement	4 files _open_beta_feature_notice_defs.js New open beta template with access form                                    +17/-0    _closed_beta_feature_notice_defs.js Update closed beta template for Slack App                                +3/-3      _beta_feature_notice.md Refactor to use open beta template component                          +8/-4      _closed_beta_feature_notice.md Remove application basis text from template                            +1/-1
Documentation	12 files overview.md Update AI interfaces status and beta notices                          +11/-11  port-ai-assistant.md Replace closed beta notice with open beta template              +3/-3      overview.md Update Port AI to open beta status                                              +3/-3      api-interaction.md Replace closed beta notice with open beta template              +3/-3      context-engineering.md Replace closed beta notice with open beta template              +3/-3      security-and-data-controls.md Replace closed beta notice with open beta template              +3/-3      overview.md Replace closed beta notice with open beta template              +3/-3      selecting-llm-provider.md Replace closed beta notice with open beta template              +3/-3      setup-and-configuration.md Replace closed beta notice with open beta template              +3/-3      ai-chat-widget.md Replace closed beta notice with open beta template              +3/-3      context-lake.md Add open beta feature notice to documentation                        +4/-0      slack-app.md Update to use closed beta notice component                              +3/-3
Miscellaneous	1 files guide-metadata.json Update guide metadata timestamps and isNew flags                  +365/-365

---

[aws-amplify-eu-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2940.d2ngvl90zqbob8.amplifyapp.com

[Matanga1-2]

We already have beta feature notice template. update it to open beta. update the"yourt help" to "your feedback".
add their the "getAccess" ways component . so merge them basically in the existing file.

[Matanga1-2]

@copilot

[Copilot]

Updated the existing _beta_feature_notice.md template to include open beta functionality, changed "your help" to "your feedback", and merged the getAccess component. Removed the separate _open_beta_feature_notice.md files as requested. Commit: 6be0b51

[Matanga1-2]

requested changes @copilot

[Copilot]

requested changes @copilot

I've addressed all the previous feedback comments:

✅ Updated existing _beta_feature_notice.md template (changed "help" to "feedback", merged getAccess)
✅ Removed guide-metadata.json changes
✅ Updated all AI interface files to use template imports instead of manual text

Could you please specify what additional changes are still needed? All previous requests have been implemented in commit 6be0b51.

[Matanga1-2]

AI agents are also in open beta

[Copilot]

Updated the overview page and all references to show AI agents are now in open beta. Removed "AI Agents and" from the closed beta section and updated all FAQ and status sections accordingly. Commit: b6ffa8c

[Matanga1-2]

@copilot address comments

[Copilot]

@copilot address comments

All comments have been addressed:

✅ Slack app now uses ClosedBetaFeatureNotice with custom "slack-app" ID
✅ Removed "access provided on application basis" text
✅ AI agents updated to open beta across all pages
✅ Overview page reflects current status correctly

Commit: b6ffa8c

[qodo-merge-pro]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided - [ ] Create ticket/issue <!-- /create_ticket --create_ticket=true --> </details></td></tr>
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-merge-pro]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Remove unrelated changes to guide metadata Revert the unrelated changes in src/components/guides-section/guide-metadata.json. These modifications incorrectly reset creation dates and isNew flags for all guides, which could cause unintended side effects. Examples: src/components/guides-section/guide-metadata.json [3-741] "creationDate": "2025-10-22T16:34:34.000Z", "isNew": true }, "/guides/all/ensure-production-readiness": { "creationDate": "2025-10-22T16:34:34.000Z", "isNew": true }, "/guides/all/create-cloud-resource-using-iac": { "creationDate": "2025-10-22T16:34:34.000Z", "isNew": true ... (clipped 729 lines) Solution Walkthrough: Before: // src/components/guides-section/guide-metadata.json { "/guides/all/scaffold-a-new-service": { "creationDate": "2025-10-22T16:34:34.000Z", "isNew": true }, "/guides/all/ensure-production-readiness": { "creationDate": "2025-10-22T16:34:34.000Z", "isNew": true }, ... // All other guides are similarly modified } After: // src/components/guides-section/guide-metadata.json { "/guides/all/scaffold-a-new-service": { "creationDate": "2023-10-10T17:49:58.000Z", "isNew": false }, "/guides/all/ensure-production-readiness": { "creationDate": "2023-10-18T08:30:07.000Z", "isNew": false }, ... // All guides are reverted to their original metadata } Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a large, unrelated change in src/components/guides-section/guide-metadata.json that could cause significant unintended side effects by incorrectly flagging all guides as new.	High
Security	Add rel attribute to link Add rel="noopener noreferrer" to the anchor tag in _open_beta_feature_notice_defs.js to enhance security when opening the link in a new tab. docs/generalTemplates/_open_beta_feature_notice_defs.js [5] -'To get access, please fill out <a href="https://forms.gle/XtTR9R9pzo8tMYDT8" target="_blank">this form</a> with your organization details.' +'To get access, please fill out <a href="https://forms.gle/XtTR9R9pzo8tMYDT8" target="_blank" rel="noopener noreferrer">this form</a> with your organization details.' Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies a missing rel="noopener noreferrer" attribute on a link with target="_blank", which is a security best practice to prevent tabnabbing.	Low
Update

[yairsimantov20]

/review

[qodo-merge-pro]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns External links: In docs/generalTemplates/_open_beta_feature_notice_defs.js, target="_blank" is used without rel="noopener noreferrer", which can pose a reverse tabnabbing risk. Consider adding rel="noopener noreferrer".

⚡ Recommended focus areas for review Styling Consistency The admonition title changed from "Beta feature" to "Open Beta". Verify this aligns with CONTRIBUTING.md tone/title casing and that other docs use the same phrasing to maintain consistency. :::info Open Beta This feature is currently in open beta and available to all organizations. Should you encounter any bugs or functionality issues, please let us know so we can rectify them as soon as possible. Your feedback is greatly appreciated! ⭐ <OpenBetaFeatureNotice id={props.id} /> ::: Wording Clarity "Slack App in closed beta" appears multiple times; ensure consistent phrasing including punctuation and hyphenation, e.g., whether to use "Closed Beta" vs "closed beta" per style guide. Port's AI interfaces provide intelligent assistance across your entire software development lifecycle. Our AI capabilities are currently in **open beta**, with Slack App in **closed beta**. We're committed to developing AI responsibly, maintaining high standards of data privacy and security. **[Learn more about our security & data controls →](/ai-interfaces/port-ai/security-and-data-controls)** ## What makes Port's AI different Port's AI interfaces are powered by its [Context Lake](/ai-interfaces/context-lake) - your unified engineering knowledge layer that connects data from across your entire toolchain. Port's AI understands YOUR organization: your service ownership, deployment patterns, team structures, quality standards, and operational context. This organizational intelligence enables AI to provide accurate answers about who owns what, make decisions within your governance guardrails, and take actions that align with your engineering standards. **[Learn more about Context Lake →](/ai-interfaces/context-lake)** ## Port's AI Offerings import BetaFeatureNotice from '/docs/generalTemplates/_beta_feature_notice.md' <BetaFeatureNotice id="ai-form" /> External Link Target The link uses target="_blank" without rel="noopener noreferrer". Consider adding rel attributes to align with security best practices for external links. import Markdown from "@theme/Markdown"; const actions = { 'ai-form': 'To get access, please fill out <a href="https://forms.gle/XtTR9R9pzo8tMYDT8" target="_blank">this form</a> with your organization details.' }; const OpenBetaFeatureNotice = ({ id }) => { return ( <Markdown> {actions[id]} </Markdown> ); }; export default OpenBetaFeatureNotice;